Railway incident
Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers.
Update timeline
- resolved Mar 25, 2026, 04:09 PM UTC
Type: Incident Duration: 1 hour and 45 minutes Affected Components: , Edge Network (Legacy) → Mar 25, 16:09:16 GMT+0 - Investigating - Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers. Mar 25, 16:11:10 GMT+0 - Identified - For some affected domains, cert provisioning is inoperable, this is due to incorrect domain configuration, please re-add your domains to triage the issue. Mar 25, 16:38:28 GMT+0 - Identified - Manual workarounds for customers show that access is restored, we are working with our upstream vendor to implement domain forwarding to mitigate customer misconfiguration. Mar 25, 17:54:18 GMT+0 - Resolved - Network behavior is back to nominal.
Looking to track Railway downtime and outages?
Pingoru polls Railway's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Railway reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Railway alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required