On 16:52 UTC, Railway customers reported an outage with a significant amount of our infrastructure affected. We have since fully recovered as of 20:03 UTC and due to the impact are planning to publish the outcome of the investigation.
Railway Status
1,401 posts
Railway Status
@railway_status
All incidents, no matter how small, are posted here
See something? Tag us!
Status 👇
- Investigating: Our edge proxy appears to be partially down. Railway-hosted applications may be inaccessible during this time. We're currently investigating this incident.
- Investigating: We are currently investigating this incident.
- Identified: Our new edge proxy is experiencing a major outage. We have identified the issue and are working on a fix
- Investigating: We are currently investigating this incident. Non-Pro deployments are temporarily paused while we fix the underlying issue.
- Investigating: A small subset of deployments are failing to serve. We're looking into it.
- Investigating: Some users are failing to login. We're looking into it
- Replying to @railway_statusResolved: Our mitigation efforts were successful and services have been restored for all users. We will publish a write-up of this incident shortly.
- Replying to @railway_statusMonitoring: We have successfully rolled out a mitigation and are seeing service recovery for most users. We're continuing to monitor the situation and are working towards restoring services for all users.
- Monitoring: Builds are taking longer than usual as github resumes webhooks after their outage. We are pausing Hobby deployments until the system catches up with the buildup of new deploys
- Replying to @railway_statusIdentified: Our fix is rolling out and we are seeing recovery for some customers.
- Replying to @railway_statusIdentified: We are continuing to work on a fix for this incident.
- Replying to @railway_statusResolved: We've deployed a permanent fix and consider the issue resolved.
- Investigating: We are currently investigating this incident. status.railway.app/clzmru70v12181…
