Incident Report: September 30, 2026: Domain Routing Disruption
Blog post from Railway
Railway experienced a roughly five-minute global routing incident on September 30, 2026, from about 07:35 to 07:40 UTC, during which new connections to hosted custom domains and railway.app subdomains returned HTTP 404 errors. The outage occurred when a newly deployed distributed routing control-plane service reached production before its required database schema migration had completed, causing route lookups to fail across all regions; origin proxies then interpreted those failures as nonexistent domains rather than using previously known routes. Existing connections and running workloads remained unaffected, no data was lost, but public access and some private network DNS lookups between services failed temporarily. Service recovered automatically once the migration completed and route lookup retries succeeded, with full recovery confirmed by 07:47 UTC. Railway identified the parallel deployment pipelines and altered fallback behavior as contributing factors, and plans to prevent recurrence through enforced migration ordering, schema validation before service rollout, unified deployment checks, and shard-based regional deployments.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.