Resolved after 5 hours 16 minutes, affecting US East (Virginia, USA) (Networking — Public (US East)) and US West (California, USA) (Networking — Public (US West)) and 1 more, on March 30, 2026.
This incident has been resolved. A postmortem is available at https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.
Affected components
Update timeline
- investigating Mar 30, 2026, 12:20 PM UTC
While updating our edge CDN to allow us to identify cached assets on a per-domain basis, we enabled a feature called “Surrogate Keys”. Unknowingly to us, this bypassed our “if CDN is disabled for this domain, pass directly to origin” behavior, which meant that we accidentally enabled CDN caching capabilities for domains that didn’t previously have it enabled. Because of that, the following assets may have been cached during this 30 minute period even with domains with the CDN feature disabled: Any content with public Cache-Control headers Images, videos and other known-static assets No HTML would’ve been cached; this is always considered dynamic At 11:30 UTC, once realizing the mistake, we immediately pushed an update which reverted this behavior and purged the cache of all assets globally.
- monitoring Mar 30, 2026, 12:21 PM UTC
This is a retroactive incident that was resolved at 11:30 UTC. We are still determining impact.
- monitoring Mar 30, 2026, 12:27 PM UTC
We are seeing reports that even content without cache-control set was erroneously cached. We are still determining impact.
- resolved Mar 30, 2026, 05:37 PM UTC
This incident has been resolved. A postmortem is available at https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.
Your product runs on more than Railway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services