Skip to main content
Railway

Clarification: Recent Oct 24 API key revocations are precautionary

Degraded Lasted 16h 30m · started · Railway's page

Level
confirmed
Worst impact
Degraded
Components
Support & Community - station.railway.com
Down Index
23of 100

What to do

  • Check whether you use Railway Support & Community - station.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 16h 30m it lasted.

    Anything that failed between 2026-10-24 13:57 UTC and 2026-10-25 06:26 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 2

  1. triage

    Railway is not currently under attack. Recent API key revocations by AI providers are precautionary actions in response to the October 21 incident, not a new security incident. On October 23, after the attacker’s access had been fully removed on October 22 at 03:32 UTC, AI providers requested another batch of potentially affected keys. We provided that batch to OpenAI and Anthropic, but because we could not filter keys by when they were added, it inadvertently included newer keys. As a result, providers may have revoked replacement keys you created after the incident. These revocations do not indicate that your replacement keys were compromised. You should also receive communications directly from the providers taking action, explaining their response and any steps you need to take. If a provider revoked your key, create a replacement, update the corresponding Railway environment variable, and redeploy the services that use it. If your keys are still working, this notice does not require you to repeat completed rotations. We’re sorry for the confusion and additional disruption.

    provider

  2. resolved

    Dismissed as a notice. No impact.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-4db16bb628

Is Railway still down?

No, this incident was resolved 2026-10-25 06:26 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

16h 30m, from 2026-10-24 13:57 UTC to 2026-10-25 06:26 UTC, by the times Railway posted.

What was affected?

Railway named Support & Community - station.railway.com.

What caused it?

Railway hasn't published a root cause. If it does, it shows here.

Where does this come from?

Railway's official status page, https://status.railway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.