# Unauthenticated pages erroneously cached

- Provider: [Railway](https://down.guide/railway)
- Level: confirmed
- Impact: Degraded
- lasted 5h 16m
- started 2026-03-30 12:20 UTC
- US East (Virginia, USA), US West (California, USA), TCP Proxy (Metal) +2
- apac, eu, us
- id: DWN-b6b9f3547b
- Official page: https://status.railway.com/incident/X0Q39H56

## Updates from Railway
### 2026-03-30 12:20 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.

### 2026-03-30 12:21 UTC: monitoring
This is a retroactive incident that was resolved at 11:30 UTC. We are still determining impact.

### 2026-03-30 12:27 UTC: monitoring
We are seeing reports that even content without cache-control set was erroneously cached. We are still determining impact.

### 2026-03-30 17:37 UTC: resolved
This incident has been resolved. A postmortem is available at https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).