Incident Related to Railway.com
Resolved
Oct 22, 2026 at 1:22pm UTC
Thank you for your patience whilst we resolved these issues.
We have just released a new CLI, v5.10.0 to address urgent security issues due to this incident and we strongly recommend updating immediately.
Affected services
Updated
Oct 22, 2026 at 1:07pm UTC
All systems are green and we're back to capacity.
An incident report will be released later today.
Affected services
Updated
Oct 22, 2026 at 12:50pm UTC
Jobs are running smoothly with minor issues on the API and console. We expect to be all normal over the next hour or so.
We're also preparing a post-mortem to be published later today.
Affected services
Updated
Oct 22, 2026 at 11:58am UTC
The Console and API are recovering and should be back to normal shortly. Tests are beginning to flow again.
Affected services
Updated
Oct 22, 2026 at 10:30am UTC
cpu1 is recovering and we're starting to see throughput again. We'll update as soon as we have more.
Affected services
Updated
Oct 22, 2026 at 9:35am UTC
As part of the incident, our hosting provider (Railway) has advised us to rotate our env keys. As a result, systems may take longer to recover as we work through our stack.
Affected services
Updated
Oct 22, 2026 at 8:32am UTC
Services are beginning to recover.
Affected services
Updated
Oct 22, 2026 at 7:28am UTC
This incident is now causing downtime.
Affected services
Created
Oct 22, 2026 at 6:28am UTC
One of our upstream providers (railway.com) has declared an incident. We're investigating.
Affected services