Changelog #0313: October 21 security incident

This week's changelog: our response to the October 21 incident and recommended actions.

Changelog

This week, we've been responding to the October 21 security incident, restoring systems, and helping customers secure their credentials. We’re deeply sorry for the disruption and the additional burden this has placed on you.

The incident involved unauthorized access to Railway's internal systems. We've taken steps to contain it and restore affected services, and we're investigating the impact with external incident response experts.

As a precaution, we recommend the following:

- Revoke and replace sensitive credentials stored on Railway before October 21.
- Remove public network access to databases.
- Review GitHub audit logs and installed app access.
- Check container registry audit logs for unexpected activity.

Our preliminary incident report explains what happened, the impact, and our response. The investigation is ongoing, and we'll share a follow-up when it concludes.

Read the incident report: https://blog.railway.com/p/preliminary-report-october-security-incident

If you have questions or need help, contact support@railway.com.

- The Railway team

Unsubscribe: https://railway.com/preferences?token=a2d8789b-5683-419d-a1fd-faec3a03807d

Accession

nse/railway/2026-10-23/4917

From

Railway · hello@news.railway.app

Sent

23 October 2026 · 23:00 UTC