Google Cloud has been accused of suspending the account of Platform-as-a-Service provider Railway without prior warning, leading to an eight-hour outage that disrupted millions of services worldwide. The incident, which began at 10:20pm UTC on May 19, 2026, was not fully resolved until 6:14am the following day, according to Railway's detailed post-incident blog post cited by The Register.
Railway, which counts over three million users hosting approximately 10 million services, APIs, and databases, reported that the suspension affected all its workloads across all clouds due to a technical dependency on Google Cloud for its network control plane API. Existing workloads remained operational for only about 15 minutes before caches expired, after which users encountered errors such as 'no healthy upstream', 'unconditional drop overload', login failures, and dashboard inaccessibility.
Account Suspension and Response
According to Railway, the account was suspended as part of a broader automated sweep by Google Cloud targeting suspicious activity, particularly cryptocurrency mining, across many GCP accounts. Google had previously warned affected users of potential lock-outs, but Railway claims it received no such notification before the suspension. The company said it took Google nearly an hour to engage after the incident began, though the account was unsuspended by 10:29pm—just nine minutes after the first issues were reported.
"We are livid and still trying to get all the details," said Angelo Saraceno, Solutions Engineer at Railway, in comments reported by The Register.
Railway spends an eight-figure sum annually with Google Cloud—potentially upwards of $1 million per month—even after moving parts of its infrastructure to colocation services following prior issues in 2024 and 2025. The company acknowledged that the outage was ultimately its own fault due to an exclusive dependency on GCP for its network control plane API.
Timeline of the Outage
| Event | Time (UTC, May 19-20, 2026) |
|---|---|
| Issue identified (account suspended) | 10:20pm |
| Account unsuspended | 10:29pm |
| Full restoration of services | 6:14am (next day) |
| Total outage duration | ~8 hours |
Implications for Cloud-Reliant Businesses
The incident highlights critical risks for companies that depend on a single cloud provider for core infrastructure. Railway's Chandrika Khanduri (Support Engineer) and Cody De Arkland (Agent Experience GM) explained that the company is now removing the network plane API's sole dependency on GCP: "If any of the interconnects go out, there is always a path between the clouds."
For international trade executives and logistics operators who rely on cloud-based platforms for supply chain management, customs filings, or data analytics, this event underscores the need for multi-cloud redundancy. An outage affecting a key SaaS provider like Railway can cascade into disruptions for import/export documentation, port communications, and real-time tracking. Railway's experience shows that even well-funded customers can be caught off-guard by automated suspension policies.
Railway's Commitment to Resiliency
Railway stated it has "invested in resiliency as a result of prior incidents" but acknowledged that the GCP-only dependency was a critical oversight. The company promised to eliminate this single point of failure and ensure that its platform remains reliable. "Your customers don't care whether the failure was Google or Railway; they see your product. Your uptime is our responsibility, and we'll keep delivering on it," the company concluded.
What to watch: Railway's implementation of multi-cloud architecture and any changes to Google Cloud's account suspension notification policies.
Sources:
