Railway incident

Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers.

Resolved after 1 hour 45 minutes, on March 25, 2026.

identified Mar 25, 2026, 04:38 PM UTC

Manual workarounds for customers show that access is restored, we are working with our upstream vendor to implement domain forwarding to mitigate customer misconfiguration..

Started
Mar 25, 2026, 04:09 PM UTC
Resolved
Mar 25, 2026, 05:54 PM UTC
Duration
1h 45m
Detected by Pingoru
Mar 25, 2026, 04:09 PM UTC

Update timeline

  1. investigating Mar 25, 2026, 04:09 PM UTC

    Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers..

  2. identified Mar 25, 2026, 04:11 PM UTC

    For some affected domains, cert provisioning is inoperable, this is due to incorrect domain configuration, please re-add your domains to triage the issue..

  3. identified Mar 25, 2026, 04:38 PM UTC

    Manual workarounds for customers show that access is restored, we are working with our upstream vendor to implement domain forwarding to mitigate customer misconfiguration..

  4. resolved Mar 25, 2026, 05:54 PM UTC

    Network behavior is back to nominal..

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.

Add your stack →