Menu

1 / 3

GCS Write Errors Ran for 12.5 Hours in us-central1. Spool Uploads to Disk, Drain Later

DEV Community: node·Gabriel Anhaia·1 day ago
#3AXUo7i1
#devtonodejs#devto#dev#spool#const
Reading 0:00
15s threshold

Book: System Design Pocket Guide: Fundamentals

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

On October 8, 2026, Google Cloud Storage in us-central1 spent twelve and a half hours returning errors and timeouts on writes. Google's incident report puts the impact from 04:00 to 16:30 US/Pacific, which is 11:00 to 23:30 UTC. Every status update posted during the day carried the same line under Workaround: "None at this time."

Then it came back. The final report adds a second window on October 9, 04:05 to 09:46 Pacific, in the us-central1-b zone, for a total of 18 hours and 11 minutes.

If your service writes user uploads or exports straight to a bucket in that region, that was up to 18 hours in which any write could come back as a 503 or hang until your timeout fired, and the writes that did succeed were slow.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.