Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google engineer unplugged every fiber they could see and – surprise! – took down a chunk of the G-Cloud

This sounds like a RTFM error at hyperscale

Google engineer unplugged every fiber they could see and – surprise! – took down a chunk of the G-Cloud

Google Cloud experienced a partial outage in its us-central1-b region on September 1, between 07:41 and 11:52 PT. The incident caused "severe network degradation and resource isolation," with traffic flow drop rates reaching 100% for resources hosted in the affected area. Google's service health report revealed that the engineers physically disconnected every fiber-optic cable within the region during a routine hardware maintenance procedure.

This prevented warnings of incorrect action from reaching the engineer before complete disconnection.

The immediate technical trigger for the event was the unplugging of 100% of fiber paths across all devices within a span of 13 minutes. Once Google noticed the situation, it moved traffic away from the disconnected routers and its resilience provisions kicked in, automatically directing traffic to healthy capacity elsewhere in the region.

Technicians identified the disconnected optical links and physically reseated the fibers. After restoring the physical links, traffic flow rates normalized and capacity was redirected back to service.

Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at theregister.com →

More in Tech

Tenant-Aware Error Capture in NestJS: HTTP Filters, Cron Jobs, Queue Workers

An error-tracking setup for a NestJS backend has one hard problem, and it isn't which vendor you sign up with: HTTP exceptions arrive by the thousand, cron jobs and queue workers arrive by the…

  • Implement three-layer error capture system: global HTTP filter, cron job wrapper, queue worker catch
  • Append tenant ID and experiment cohort to error data at each entry point
  • Choose between Sentry, OpenTelemetry, or Infrai for consistent error tagging

개발자 문서 링크 저장을 위한 실용적인 체크리스트

개발자의 링크 보관은 검색보다 맥락에 가깝다. 프레임워크 문서, API 레퍼런스, GitHub 이슈, 변경 기록, 마이그레이션 안내, 패키지 설명, 다른 프로젝트의 예제까지 하루에도 여러 종류의 페이지가 작업 화면을 스친다. 필요한 순간에는 분명 유용했지만, 몇 주 뒤 같은 오류가 다시 나타나면 상황이 달라진다.

More from Friday 4 September →