2 months ago
Cdn Erroneously Enabled for DomainsOperational
US East (Metal / Virginia, USA)US West (Metal / California, USA)TCP Proxy (Metal)EU West (Metal / Amsterdam, Netherlands)Southeast Asia (Metal / Singapore)
Resolved
This incident has been resolved. A postmortem is available at https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.
March 30, 17:37 UTC
Monitoring
We are seeing reports that even content without cache-control set was erroneously cached. We are still determining impact.
March 30, 12:27 UTC
Monitoring
This is a retroactive incident that was resolved at 11:30 UTC. We are still determining impact.
March 30, 12:21 UTC
Investigating
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.
4 Replies
2 months ago
The CDN incident you referenced has already been resolved, and your service's latest deployment shows a SUCCESS status with no error logs. If you're still unable to access your page, try a hard refresh or clear your browser cache, as stale cached content from the incident window may still be served by your browser.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
The CDN incident you referenced has already been resolved, and your service's latest deployment shows a SUCCESS status with no error logs. If you're still unable to access your page, try a hard refresh or clear your browser cache, as stale cached content from the incident window may still be served by your browser.
2 months ago
how do you do hard refresh?
Status changed to Awaiting Railway Response Railway • about 2 months ago
gelson12
how do you do hard refresh?
2 months ago
i tried different browser it still dont work
Attachments
Status changed to Open Railway • about 2 months ago
2 months ago
Hello gelson12,
the cdn incident is already resolved since 11:30 utc today, so thats not your issue anymore. since you already tried different browsers, the problem is on your app side not the cdn. go to your railway dashboard, open your service, click on the latest deployment and check the runtime logs (not just the build logs) and share what you see there, that will tell exactly whats wrong