Domain provisioning is heavily delayed

What to do

• Check whether you use Railway Dashboard - railway.com. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 45m it lasted.

  Anything that failed between 2026-04-29 10:48 UTC and 2026-04-29 11:33 UTC may need a replay.

• Subscribe to Railway's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Railway 3

1. investigatingApr 29, 2026, 10:48 AM UTC

   Our CDN provider Fastly is experiencing an outage, which is causing TLS provisioning to take longer than expected. As a result, new domains being added to Railway might fail to obtain SSL certificates. Fastly's incident is available here: https://www.fastlystatus.com/incident/378511

   provider

2. monitoringApr 29, 2026, 11:10 AM UTC

   Fastly has implemented a fix and is experiencing recovery. They are currently monitoring this incident. We see active recovery in TLS provisioning globally. Please retry adding your domain. If you have any issues contact us on https://station.railway.com

   provider

3. resolvedApr 29, 2026, 11:33 AM UTC

   We have seen full recovery and are resolving this incident. If you have any questions please reach out at https://station.railway.com.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.