Railway told customers to change their keys after a breach of its systems
Railway, a hosting service that developers use to run apps, said attackers broke into its internal systems from October 20 to 22 and reached stored customer secrets. Railway told customers who signed up before October 21 to replace their keys.
Checked Nov 17, 2026, 7:00 PM ET
- Affected
- Developers and companies that host apps on Railway. At most about 100,000 workspaces (Railway, Oct 22).
- Official instruction
- Railway recommends that all customers who signed up before Oct 21 rotate the keys they stored on Railway.
- Status
- Railway says the attacker lost access at 3:32 a.m. UTC on Oct 22. Its forensic investigation continues.
What happened
Confirmed2Unconfirmed1- ConfirmedAttackers accessed Railway's internal systems between Oct 20 and Oct 22 and decrypted stored secrets for some customers. Railway says at most about 100,000 workspaces were affected.
- ConfirmedApps already running on Railway stayed online. New builds and deployments were paused during the response.
- UnconfirmedWhether the attackers also accessed customers' source code: Railway says it has not ruled this out.
The cause
Official accountRailway says a targeted attack on its build systems was trying to obtain API keys for AI providers. Railway has not yet published the technical details and says outside forensics experts and the authorities are assisting.
For your household
Most households need no action and no purchase. This affects people and companies that host apps on Railway. If you do, replace the keys you stored there, as Railway recommends.
Share this check
Sources
- RailwayAffected organizationOct 22, 2026Preliminary Report: Oct 21st Security Incident
The full story
What happened
Railway is a hosting service that developers use to run websites and apps. In a report dated October 22, 2026, Railway said attackers had accessed part of its internal systems between October 20 and October 22.
Railway says the attackers pulled customers' stored secrets, such as passwords and API keys, and decrypted a subset of them. It puts the upper limit at about 100,000 workspaces. Railway asked the companies that issued those keys, including GitHub, OpenAI, and Stripe, to cancel them.
Apps already running on Railway stayed online. New builds and deployments were paused while Railway responded. Railway says individual user accounts were not logged into, and that it has not ruled out access to customer source code.
The cause
Railway says this was a sustained, targeted attack on its build systems and that the attackers were looking for API keys for AI providers. Railway has not published the technical details of how the attackers got in. It says it will do so when its investigation ends.
This is the company's own preliminary account. Railway says it has engaged an outside forensics company and the authorities. A final report would settle the open questions, including whether source code was accessed.
What it means for you
If you do not build or host software on Railway, there is nothing to do and nothing to buy. An app you use may run on Railway, but Railway says running apps stayed online.
If you are a Railway customer who signed up before October 21, replace the sensitive keys you stored there. Railway also suggests removing public network access to databases and reviewing your GitHub audit logs.
Updates and corrections
First published Nov 17, 2026, 7:00 PM ET. Sources last checked Nov 17, 2026, 7:00 PM ET. No updates or corrections since then. How we check and correct