Railway Outage History
Railway degraded · 1 active incident View live status →Pingoru has recorded 314 incidents for Railway: 145 in the last 12 months and 32 in the last 90 days.
Incidents, newest first
Minor August 14, 2026 Logs and Metrics Delays 17m Observability (Logs), Observability (Metrics)
Started Aug 14, 2026, 04:05 PM UTC· resolved Aug 14, 2026, 04:22 PM UTC
- investigating Aug 14, 2026, 04:05 PM UTC
We are aware of an issue affecting logs and metrics. Users may experience delays or gaps in log and metric delivery. We are actively investigating and will provide updates as we learn more.
- identified Aug 14, 2026, 04:08 PM UTC
We have identified the issue and are working on a fix.
- monitoring Aug 14, 2026, 04:16 PM UTC
We have implemented a fix and have seen full recovery. We are monitoring the results
- resolved Aug 14, 2026, 04:22 PM UTC
We have seen consistent full recovery. This incident is now resolved
Minor August 11, 2026 Railpack builds may be delayed 1h 22m US East (Virginia, USA) (Builds (US East)), US West (California, USA) (Builds (US West)), EU West (Amsterdam, Netherlands) (Builds (EU West)), Southeast Asia (Singapore) (Builds (Southeast Asia))
Started Aug 11, 2026, 06:52 PM UTC· resolved Aug 11, 2026, 08:14 PM UTC
- investigating Aug 11, 2026, 06:52 PM UTC
We are aware that some select services built using Railpack might have extended build times or fail. We are investigating this incident
- identified Aug 11, 2026, 06:55 PM UTC
We have identified this issue as isolated to users deploying via railway up with railpack. We are working on a fix for this incident.
- identified Aug 11, 2026, 07:24 PM UTC
We are continuing to work on a fix for this incident.
- monitoring Aug 11, 2026, 07:47 PM UTC
We have rolled out a fix and are seeing recovery.
- resolved Aug 11, 2026, 08:14 PM UTC
We have seen full recovery and have marked this incident as resolved. If you encounter any issues, please open a thread at https://station.railway.com
Major August 10, 2026 Connectivity issues in US West 2h 7m US West (California, USA) (Deployments (US West)), US West (California, USA) (Networking — Public (US West))
Started Aug 10, 2026, 03:39 AM UTC· resolved Aug 10, 2026, 05:47 AM UTC
- investigating Aug 10, 2026, 03:39 AM UTC
We are aware of issues affecting services in our US West (California) region. Users may experience intermittent connectivity to deployed services and delays with new deployments in this region. We are actively investigating and we will provide updates as we learn more.
- investigating Aug 10, 2026, 04:21 AM UTC
We are continuing to work on the issues affecting services in US West (California). Some services in the region remain affected: databases may be unreachable, and new deployments may fail or stall We will provide another update as we have more.
- identified Aug 10, 2026, 04:27 AM UTC
We have identified the cause. Elevated traffic into our US West (California) region saturated network capacity, which caused services in the region to become slow or unreachable. Network capacity has recovered and we are seeing affected services return to normal. Some services in the region may still be recovering. We will provide another update shortly.
- monitoring Aug 10, 2026, 04:37 AM UTC
Services in US West (California) are recovering We are monitoring the region to confirm it remains stable. If you are still seeing issues with a service in this region, please reach out at https://station.railway.com.
- resolved Aug 10, 2026, 05:47 AM UTC
This incident has been resolved. Services in US West (California) have returned to normal operation. A small number of services may need a redeploy to fully recover. If yours is still not behaving as expected, please reach out at https://station.railway.com and we will take a look. We apologize for the disruption.
Minor July 31, 2026 Dashboard slowness 30m Railway (Dashboard — railway.com), Railway (API — backboard.railway.com)
Started Jul 31, 2026, 11:08 AM UTC· resolved Jul 31, 2026, 11:39 AM UTC
- investigating Jul 31, 2026, 11:08 AM UTC
We're investigating reports of slowness with the railway.com dashboard
- investigating Jul 31, 2026, 11:09 AM UTC
Triage escalated to incident
- identified Jul 31, 2026, 11:26 AM UTC
We have identified the issue and are rolling out a fix.
- monitoring Jul 31, 2026, 11:34 AM UTC
We have rolled out a fix and are seeing recovery. We are continuing to monitor this incident.
- resolved Jul 31, 2026, 11:39 AM UTC
This incident has been resolved.
Minor July 30, 2026 Builds and deployments are delayed 1h 27m US East (Virginia, USA) (Builds (US East)), US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Builds (US West)), US West (California, USA) (Deployments (US West)) and 4 more
Started Jul 30, 2026, 04:32 PM UTC· resolved Jul 30, 2026, 05:59 PM UTC
- investigating Jul 30, 2026, 04:32 PM UTC
We are aware of an issue causing builds and deployments to be delayed. Hobby and Pro projects are affected. Deployments may take longer to queue and start than usual. We are actively investigating and working to restore normal processing times. We will provide updates as we learn more.
- identified Jul 30, 2026, 05:10 PM UTC
We have identified the root cause of the build and deployment delays. We are working to resolve this as soon as possible. In the meantime, we have paused new deployments for Hobby and Trial plans to reduce load while we continue to investigate and implement a fix. Pro projects remain active but may continue to experience delays. We will provide another update shortly.
- identified Jul 30, 2026, 05:43 PM UTC
We are seeing improvement in build and deployment processing. Hobby plan deployments are no longer queued; Pro plan deployments are still working through a backlog but are trending in the right direction. We are continuing to monitor the situation and will provide another update shortly.
- monitoring Jul 30, 2026, 05:47 PM UTC
Build and deployment processing has fully resumed. Non-Pro plan deployments have been re-enabled and the Pro plan backlog has cleared. We are monitoring the situation to ensure processing remains stable and will provide another update shortly.
- resolved Jul 30, 2026, 05:59 PM UTC
Build and deployment processing has been restored across all regions. All plan tiers are processing normally and the backlog has cleared. We apologize for any inconvenience this caused. If you continue to experience issues, please contact support at https://station.railway.com.
Minor July 28, 2026 Builds are delayed 45m US East (Virginia, USA) (Builds (US East)), US West (California, USA) (Builds (US West)), EU West (Amsterdam, Netherlands) (Builds (EU West)), Southeast Asia (Singapore) (Builds (Southeast Asia))
Started Jul 28, 2026, 04:19 PM UTC· resolved Jul 28, 2026, 05:04 PM UTC
- investigating Jul 28, 2026, 04:19 PM UTC
We are aware of an issue causing builds to be delayed. Users may experience builds taking longer than usual to start or progress. Builds on the trial plan have been disabled; hobby and pro plans builds will be slow to progress. We are actively investigating and working to restore normal build times. We will provide updates as we learn more.
- identified Jul 28, 2026, 04:32 PM UTC
We have identified the root cause of the build delays and are actively working to clear the build queue. Hobby plan builds have recovered. Trial plan builds remain paused, and Pro plan builds are still slow to progress as the queue continues to drain. We will provide further updates as we learn more.
- identified Jul 28, 2026, 04:38 PM UTC
Pro plan builds have recovered and the build queue has fully drained. Trial plan builds remain paused while we continue monitoring. We will provide a further update shortly.
- monitoring Jul 28, 2026, 04:50 PM UTC
Trial plan builds have been re-enabled. Pro and Hobby plan builds are operating normally. We are continuing to monitor the situation.
- resolved Jul 28, 2026, 05:04 PM UTC
All build plans have returned to normal operation. Trial plan builds have been re-enabled, and Pro and Hobby plan builds are operating normally. This incident has been resolved. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Major July 18, 2026 Intermittent connectivity issues affecting Outbound Static IPs in US East 1h 22m US East (Virginia, USA) (Networking — Outbound Static IPs (US East))
Started Jul 18, 2026, 06:03 PM UTC· resolved Jul 18, 2026, 07:26 PM UTC
- investigating Jul 18, 2026, 06:03 PM UTC
We are aware of an issue affecting Outbound Static IPs in US East. Some users relying on static egress IPs may experience intermittent connectivity issues. We are actively investigating and working to mitigate the impact. We will provide updates as we learn more.
- identified Jul 18, 2026, 06:38 PM UTC
We are aware of an issue affecting Outbound Static IPs in US East. Some users relying on static egress IPs may experience intermittent connectivity issues. We are mitigating the impact. We will provide updates as we learn more.
- monitoring Jul 18, 2026, 06:51 PM UTC
We have mitigated outbound Static IPs in US East. We will provide updates as we learn more.
- resolved Jul 18, 2026, 07:26 PM UTC
This incident is resolved.
Major July 16, 2026 Storage Bucket creation is unavailable 51m US East (Virginia, USA) (Storage Buckets (US East)), US West (California, USA) (Storage Buckets (US West)), EU West (Amsterdam, Netherlands) (Storage Buckets (EU West)), Southeast Asia (Singapore) (Storage Buckets (Southeast Asia))
Started Jul 16, 2026, 09:22 AM UTC· resolved Jul 16, 2026, 10:14 AM UTC
- investigating Jul 16, 2026, 09:22 AM UTC
We are aware of an issue preventing the creation of new Storage Buckets. Users attempting to create a Storage Bucket may see failures. We are actively investigating and will provide updates as we learn more.
- identified Jul 16, 2026, 09:31 AM UTC
We identified the issue related to an upstream provider and are currently rolling out a mitigation.
- resolved Jul 16, 2026, 10:14 AM UTC
The fix has rolled out and is working as intended.
Minor July 8, 2026 Deployments failing in US West 57m US West (California, USA) (Deployments (US West))
Started Jul 08, 2026, 08:50 PM UTC· resolved Jul 08, 2026, 09:47 PM UTC
- investigating Jul 08, 2026, 09:36 PM UTC
We are aware of an issue causing deployments to fail in US West. Users attempting to deploy may see their deployment fail immediately after a successful build.
- resolved Jul 08, 2026, 09:47 PM UTC
Deployments are functioning normally. We apologize for the disruption.
Minor July 8, 2026 Builds taking longer than usual in US West 22m US West (California, USA) (Builds (US West))
Started Jul 08, 2026, 02:10 PM UTC· resolved Jul 08, 2026, 02:32 PM UTC
- investigating Jul 08, 2026, 02:10 PM UTC
We are aware of an issue causing builds to take longer than usual to complete in US West (California, USA). Users in this region may experience increased build times. We are actively investigating and will provide updates as we learn more.
- monitoring Jul 08, 2026, 02:17 PM UTC
Build times in US West (California, USA) appear to have returned to normal. We are monitoring to confirm stability before resolving this incident. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
- resolved Jul 08, 2026, 02:32 PM UTC
Build times in US West (California, USA) have returned to normal and this incident is now resolved. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Critical July 2, 2026 Elevated latency and packet loss on Edge Network in US regions 4h 16m US East (Virginia, USA) (Networking — Public (US East)), US West (California, USA) (Networking — Public (US West))
Started Jul 02, 2026, 07:44 AM UTC· resolved Jul 02, 2026, 12:01 PM UTC
- investigating Jul 02, 2026, 07:44 AM UTC
We are aware of elevated latency and packet loss affecting users in US regions. Users may experience increased response times or intermittent connectivity issues. We are actively investigating and will provide updates as we learn more.
- identified Jul 02, 2026, 07:50 AM UTC
We have traced the elevated latency and packet loss affecting US regions to an issue with an upstream fiber provider. We are pulling the affected provider from our network path to route traffic around the disruption. While this reroute is in progress, users in US regions may continue to experience increased response times or intermittent connectivity, and private networking between regions may also be affected.
- identified Jul 02, 2026, 08:34 AM UTC
Traffic continues to route around the affected upstream fiber provider following our earlier reroute. We are seeing conditions in US regions improve, but latency and packet loss have not fully returned to baseline, and cross-region private networking may still be intermittent. We are continuing to work toward full recovery and are monitoring closely.
- identified Jul 02, 2026, 08:52 AM UTC
The issue affecting US regions has worsened and is now causing widespread disruption. Many users may experience failed connections, significantly elevated latency, and packet loss, and private networking between regions is heavily degraded. This impacts all traffic into and out of our US East region. Our earlier reroute has not fully mitigated the impact. We are working on adjusting our network path to restore service as quickly as possible. We will provide the next update within 30 minutes.
- identified Jul 02, 2026, 09:04 AM UTC
We are beginning to see recovery across US regions as our network path adjustments take effect. Connectivity is improving and latency and packet loss are trending back toward normal, though some users may still experience intermittent issues, including with private networking between regions. We are continuing to work toward full service restoration.
- identified Jul 02, 2026, 09:49 AM UTC
Recovery across US regions is continuing as our network path adjustments hold, and latency and packet loss are trending back toward normal. Some users may still experience intermittent connectivity, including with private networking between regions. Services with attached volumes in US East may experience slower read and write performance as storage recovers. We are continuing to work toward full restoration and will provide the next update within 30 minutes.
- identified Jul 02, 2026, 10:29 AM UTC
We are continuing to work toward full restoration across US regions. Conditions remain improved from earlier, but the incident is not yet fully resolved, and some users may still see intermittent connectivity, including with private networking between regions, and slower volume performance in US East.
- monitoring Jul 02, 2026, 11:49 AM UTC
Full connectivity has been restored across US regions. Our network path adjustments are holding, latency and packet loss have returned to normal, and private networking between regions and volume performance in US East have recovered. We are monitoring closely to confirm everything remains stable before marking this incident resolved.
- resolved Jul 02, 2026, 12:01 PM UTC
This incident has been resolved. A post-mortem of this incident will be published once ready. We apologize for the disruption. If you continue to experience any issues, please reach out at https://station.railway.com.
Major July 1, 2026 Elevated latency on Edge Network 1h 8m US East (Virginia, USA) (Networking — Public (US East)), US West (California, USA) (Networking — Public (US West))
Started Jul 01, 2026, 10:29 PM UTC· resolved Jul 01, 2026, 11:37 PM UTC
- investigating Jul 01, 2026, 10:29 PM UTC
We are aware of elevated latency affecting some users. We are actively investigating and will provide updates as we learn more.
- monitoring Jul 01, 2026, 11:07 PM UTC
We have identified packet loss affecting several edge network points of presence in North America. We have seen recovery and are monitoring the situation.
- resolved Jul 01, 2026, 11:37 PM UTC
We have observed healthy response times and are resolving this incident.
Minor June 22, 2026 Logs and metrics may be slow to load 6h 27m Observability (Logs), Observability (Metrics)
Started Jun 22, 2026, 01:26 PM UTC· resolved Jun 22, 2026, 07:53 PM UTC
- investigating Jun 22, 2026, 01:26 PM UTC
Users may experience elevated load times for logs and metrics. We are currently investigating this incident.
- identified Jun 22, 2026, 01:54 PM UTC
We have identified elevated query load on our logging infrastructure as the likely cause of slow log and metric load times. We are actively working to implement additional rate limiting to reduce the impact and restore normal performance. Some users may continue to experience slow load times for logs and metrics while we work on a fix. We will provide further updates as we make progress.
- identified Jun 22, 2026, 02:58 PM UTC
We are continuing to see signs of recovery and are observing more standard request times.
- resolved Jun 22, 2026, 07:53 PM UTC
The issue affecting log and metric load times has been resolved. We applied additional rate limiting and expanded our logging infrastructure capacity, which has restored normal performance. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Minor June 15, 2026 Logs are slow to load 1h 26m Observability (Logs)
Started Jun 15, 2026, 01:30 PM UTC· resolved Jun 15, 2026, 02:56 PM UTC
- investigating Jun 15, 2026, 01:30 PM UTC
We are aware of an issue causing logs to load slowly. Users may experience delays when viewing logs in the dashboard. We are actively investigating and working to restore normal performance. We will provide updates as we learn more.
- monitoring Jun 15, 2026, 01:54 PM UTC
We have implemented additional controls to limit the impact of high-volume log queries on our logging system. Wait times have stabilized and we are monitoring to confirm the fix is holding. Users may still experience some delays when loading logs. We will continue to provide updates as we monitor the situation.
- resolved Jun 15, 2026, 02:41 PM UTC
The issue causing logs to load slowly has been resolved. We have deployed additional controls to limit the impact of high-volume log queries on our logging system, and wait times have returned to normal. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Major June 11, 2026 AWS cloud workloads in US West and US East regions may experience failures to respond 6h 27m US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), US West (California, USA) (Networking — Public (US West))
Started Jun 11, 2026, 10:21 AM UTC· resolved Jun 11, 2026, 04:48 PM UTC
- investigating Jun 11, 2026, 10:21 AM UTC
We are aware of issues affecting our compute infrastructure across multiple regions. Users in US West and Singapore may experience failures or degraded performance with deployments and running services. We are actively investigating the scope and root cause and will provide updates as we learn more.
- investigating Jun 11, 2026, 11:27 AM UTC
We are continuing to investigate issues affecting our compute infrastructure in US West and Singapore regions. We have identified a potential contributing factor and are actively working to restore affected services. Some users in these regions may continue to experience failures or degraded performance with running services and deployments. We will provide further updates as we learn more.
- resolved Jun 11, 2026, 04:48 PM UTC
The issue affecting our AWS compute infrastructure in US West and US East regions has been resolved. Services in these regions are now operating normally. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com/.
Major June 10, 2026 GitHub is reporting authentication issues with their API 1h 12m External & Third-Party Integrations (GitHub — Auto-Deploys)
Started Jun 10, 2026, 03:29 PM UTC· resolved Jun 10, 2026, 04:42 PM UTC
- investigating Jun 10, 2026, 03:29 PM UTC
Users may see failures surrounding GitHub operations. GitHub's statuspage will have the most accurate up to date information https://www.githubstatus.com/incidents/fcj3088jg1wx
- monitoring Jun 10, 2026, 03:51 PM UTC
GitHub has observed recovery and is monitoring the results. https://www.githubstatus.com/incidents/fcj3088jg1wx
- resolved Jun 10, 2026, 04:42 PM UTC
GitHub has reported full recovery and has resolved this incident. https://www.githubstatus.com/incidents/fcj3088jg1wx
Minor June 8, 2026 Metrics and logs may be delayed or unavailable 3h 36m Observability (Logs), Observability (Metrics)
Started Jun 08, 2026, 01:13 PM UTC· resolved Jun 08, 2026, 04:49 PM UTC
- investigating Jun 08, 2026, 01:13 PM UTC
We are aware of an issue affecting metrics and log visibility in the dashboard. Users may experience metrics not loading or appearing delayed. We are actively investigating and will provide updates as we learn more.
- identified Jun 08, 2026, 02:18 PM UTC
We are continuing to investigate the issue affecting metrics visibility in the dashboard. We have identified high query load on our logging and metrics system as the contributing factor and have implemented interim mitigations to reduce pressure. We are in the process of rolling out a fix and will provide updates as progress continues.
- monitoring Jun 08, 2026, 04:33 PM UTC
We are continuing to investigate the issue affecting metrics and log visibility in the dashboard. Users may still experience metrics not loading or appearing delayed. We have identified high read load on our logging and metrics system as the root cause. Log queries in particular were generating significant pressure on the system, and we have deployed additional rate limiting to reduce this load. Metrics and logs are currently loading, though we are continuing to monitor closely before resolving the incident. We will provide a further update shortly.
- resolved Jun 08, 2026, 04:49 PM UTC
Metrics and logs have returned healthy for an extended period now. We are marking this incident as resolved. If you have any questions, https://station.railway.com
Major June 5, 2026 Private Networking Degraded in Southeast Asia (Singapore) 1h 33m Southeast Asia (Singapore) (Deployments (Southeast Asia))
Started Jun 05, 2026, 04:17 PM UTC· resolved Jun 05, 2026, 05:51 PM UTC
- investigating Jun 05, 2026, 04:17 PM UTC
We are investigating an issue with private networking in our Southeast Asia (Singapore) region. Some workloads in this region may experience intermittent request timeouts when reaching their services. We are actively investigating the root cause and will provide updates as we learn more.
- identified Jun 05, 2026, 04:38 PM UTC
We have identified that the issue involves degraded transit connectivity between our Southeast Asia (Singapore) region and our US East infrastructure. Some workloads experiencing cross-region connectivity may see intermittent request timeouts as a result. We are actively investigating the affected transit paths and working to restore normal connectivity. We will provide further updates as we make progress.
- monitoring Jun 05, 2026, 05:30 PM UTC
We have identified a degraded transit path between our Southeast Asia (Singapore) region and our US East infrastructure as the root cause of the connectivity issues. We removed the affected transit provider and observed significant recovery in our network metrics. We are continuing to monitor the situation and investigating any remaining connectivity issues. We will provide a further update shortly.
- resolved Jun 05, 2026, 05:51 PM UTC
The connectivity issues affecting private networking between our Southeast Asia (Singapore) region and US East infrastructure have been resolved. We identified a degraded transit path as the root cause and removed the affected transit provider, which restored normal connectivity. We apologize for any inconvenience caused. If you continue to experience issues, please contact support at https://station.railway.com.
Major June 5, 2026 API errors elevated 3h 34m Railway (Dashboard — railway.com)
Started Jun 05, 2026, 10:04 AM UTC· resolved Jun 05, 2026, 01:38 PM UTC
- investigating Jun 05, 2026, 10:04 AM UTC
We are aware of an issue causing elevated API errors. Some users may experience failed requests or unexpected errors when using the Railway dashboard or API. We are actively investigating the root cause and will provide updates as we learn more.
- identified Jun 05, 2026, 10:18 AM UTC
We have identified that the elevated API errors are isolated to metrics and usage data queries. Other API functionality is operating normally. We are actively working to clear the backlog of queued metrics queries and will provide further updates as we make progress.
- investigating Jun 05, 2026, 11:34 AM UTC
We continue to investigate elevated wait times for metrics and usage data queries. Our team has been actively working to clear the query backlog, but the issue is persisting as we investigate the underlying cause. Other API functionality remains unaffected. We will provide further updates as we make progress.
- monitoring Jun 05, 2026, 11:39 AM UTC
We have identified that corrupt state in our query queue was preventing metrics and usage data queries from being processed. We have cleared the corrupt state and metrics are now loading normally. We are monitoring to confirm full recovery. Other API functionality was not affected throughout this incident. We will provide a final update shortly.
- resolved Jun 05, 2026, 01:38 PM UTC
The issue affecting metrics and usage data queries has been resolved. Corrupt state in our query queue was preventing queries from being processed. We cleared the corrupt state and metrics are now loading normally. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Minor June 5, 2026 Degraded Storage Performance in Southeast Asia 7h 35m Southeast Asia (Singapore) (Deployments (Southeast Asia))
Started Jun 05, 2026, 08:44 AM UTC· resolved Jun 05, 2026, 04:20 PM UTC
- investigating Jun 05, 2026, 08:44 AM UTC
We are aware of an issue affecting storage performance in our Singapore region. Users may experience slower than normal read/write operations for services with volumes. We are actively investigating the root cause and will provide updates as we learn more.
- monitoring Jun 05, 2026, 03:57 PM UTC
We have applied a fix for the storage performance issues affecting services with volumes in our Singapore region. Read/write operations have recovered to normal levels.
- resolved Jun 05, 2026, 04:20 PM UTC
This incident has been resolved.
Major June 4, 2026 Metrics unavailable 1h 12m Observability (Metrics)
Started Jun 04, 2026, 12:52 PM UTC· resolved Jun 04, 2026, 02:05 PM UTC
- investigating Jun 04, 2026, 12:52 PM UTC
We are aware of an issue preventing metrics from loading. Users may be unable to view service metrics in the dashboard. We are actively investigating and will provide updates as we learn more.
- resolved Jun 04, 2026, 02:05 PM UTC
The issue preventing metrics from loading has been resolved. An internal background job was consuming excessive capacity in our metrics system, crowding out user-facing metrics queries. We deployed a fix to stop the background job and adjusted system settings to restore normal query processing. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Minor June 3, 2026 Elevated latency for some services routing through US West 1h 22m US West (California, USA) (Networking — Public (US West))
Started Jun 03, 2026, 11:17 PM UTC· resolved Jun 04, 2026, 12:39 AM UTC
- investigating Jun 03, 2026, 11:17 PM UTC
We are aware of elevated latency affecting HTTP requests routed through our US West (Los Angeles) edge. Apps and services whose traffic enters through this region may see slow responses or timeouts. We are actively investigating the root cause and will provide updates as we learn more.
- monitoring Jun 04, 2026, 12:08 AM UTC
We have implemented a mitigation and are monitoring this incident. Due to DNS caching and connection closing, some users may take a few minutes to see improvement.
- resolved Jun 04, 2026, 12:39 AM UTC
The issue affecting elevated latency for services routing through our US West (Los Angeles) edge has been resolved. We identified the cause as an issue with our edge location in Los Angeles and implemented a mitigation. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Minor June 2, 2026 Dashboard Logs Loading Slowly 3h 35m Railway (Dashboard — railway.com)
Started Jun 02, 2026, 04:15 PM UTC· resolved Jun 02, 2026, 07:51 PM UTC
- investigating Jun 02, 2026, 04:15 PM UTC
We are investigating reports of logs loading slowly or failing to load in the Railway dashboard. We are actively looking into the issue and will provide updates as we learn more.
- monitoring Jun 02, 2026, 04:33 PM UTC
We have identified the cause of the slow log loading. Query latency has since recovered and we are continuing to monitor the situation. We will provide another update shortly.
- resolved Jun 02, 2026, 07:51 PM UTC
We continue to monitor but logging is back to normal
Minor May 29, 2026 Builds and deployments are slow to progress 38m US West (California, USA) (Deployments (US West))
Started May 29, 2026, 11:11 PM UTC· resolved May 29, 2026, 11:50 PM UTC
- investigating May 29, 2026, 11:11 PM UTC
We are aware of slower than normal build and deployment times. New builds and deployments may take longer than usual to complete, and some deployments may appear stuck while in progress. Existing running services are not affected. We are actively investigating the root cause and we will provide updates as we learn more.
- investigating May 29, 2026, 11:21 PM UTC
We have narrowed the scope of this issue to part of our US-West region. Builds and deployments originating in US-West may be experiencing slower than normal progress due to elevated image pull times in that region. Builds and deployments in other regions are not affected. Existing running services remain unaffected. We are continuing to investigate and will provide further updates as we learn more.
- monitoring May 29, 2026, 11:35 PM UTC
We believe the issue affecting builds and deployments in our US-West region has been resolved. Image pull times have returned to normal levels and builds and deployments are progressing as expected. We are monitoring to confirm stability and will provide a further update shortly.
- resolved May 29, 2026, 11:50 PM UTC
We have confirmed that the issue affecting builds and deployments in our US-West region has been resolved. Image pull times have returned to normal and builds and deployments are progressing as expected. We apologize for any disruption this caused.
Major May 27, 2026 Build Log Delivery Delays 4h 22m Observability (Logs)
Started May 27, 2026, 05:19 PM UTC· resolved May 27, 2026, 09:41 PM UTC
- investigating May 27, 2026, 05:19 PM UTC
We are investigating an issue affecting build log delivery. Some build logs may be missing or incomplete for deployments since approximately 14:46 UTC. Your running applications are not affected, and historical logs from before this window remain available. We are actively investigating and will provide updates as we learn more.
- monitoring May 27, 2026, 06:03 PM UTC
We have deployed a fix for the build log delivery issue and are now monitoring to confirm full recovery. Some build logs from the affected window (approximately 14:46–17:53 UTC) will be permanently missing. We will provide a further update once we have confirmed stability.
- investigating May 27, 2026, 06:22 PM UTC
While monitoring, we continued to see periods where build logs may be missing or incomplete. The earlier fix addressed part of the underlying issue, but the problem has not been fully resolved. We are actively investigating. Your running applications are not affected. We will provide a further update as we learn more.
- investigating May 27, 2026, 07:16 PM UTC
We are continuing to investigate the build log delivery issue. We are still seeing periods where build logs may be missing or incomplete, and have not yet reached a full resolution. Your running applications are not affected. We will provide a further update as we learn more.
- identified May 27, 2026, 08:35 PM UTC
We have identified the cause of the build log delivery issue. We have deployed a fix to address this and are in the process of rolling it out across our build infrastructure. We are monitoring for recovery and will provide a further update once we have confirmed stability. Your running applications are not affected. Build logs from the affected window may be permanently missing.
- monitoring May 27, 2026, 09:19 PM UTC
We have identified and resolved the underlying cause of the build log delivery issue. A fix has been deployed and we are now monitoring to confirm full recovery. Your running applications are not affected. Build logs from the affected window may be permanently missing. We will provide a further update once we have confirmed stability.
- resolved May 27, 2026, 09:41 PM UTC
We have confirmed that the build log delivery issue has been resolved. Build logs are now being delivered successfully and metrics have returned to normal levels. We apologize for the disruption. Build logs from the affected window may be permanently missing. Your running applications were not affected at any point during this incident.