Railway Outage History

Railway is up right now

Railway had 26 outages in the last 2 years totaling 30h 32m of downtime, averaging 1.1 incidents per month.

There were 26 Railway outages since March 2, 2026 totaling 30h 32m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: railway.instatus.com

Minor March 25, 2026

Outbound networking to Azure timing out.

Detected by Pingoru
Mar 25, 2026, 08:23 PM UTC
Resolved
Mar 25, 2026, 09:47 PM UTC
Duration
1h 24m
Timeline · 4 updates
  1. investigating Mar 25, 2026, 08:23 PM UTC

    We are currently investigating this incident..

  2. identified Mar 25, 2026, 09:17 PM UTC

    We have traced this back to a change rolled out with static IP egress gateways. We have begun the rollbacks and are already seeing recovery..

  3. monitoring Mar 25, 2026, 09:29 PM UTC

    The rollback has completed, we are seeing recovery, and are currently monitoring the result..

  4. resolved Mar 25, 2026, 09:47 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 25, 2026

Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers.

Detected by Pingoru
Mar 25, 2026, 04:09 PM UTC
Resolved
Mar 25, 2026, 05:54 PM UTC
Duration
1h 45m
Timeline · 4 updates
  1. investigating Mar 25, 2026, 04:09 PM UTC

    Cert discrepancy between Fastly and Railway leading to SAN errors. The network team is actively triaging the issue for affected customers..

  2. identified Mar 25, 2026, 04:11 PM UTC

    For some affected domains, cert provisioning is inoperable, this is due to incorrect domain configuration, please re-add your domains to triage the issue..

  3. identified Mar 25, 2026, 04:38 PM UTC

    Manual workarounds for customers show that access is restored, we are working with our upstream vendor to implement domain forwarding to mitigate customer misconfiguration..

  4. resolved Mar 25, 2026, 05:54 PM UTC

    Network behavior is back to nominal..

Read the full incident report →

Minor March 25, 2026

Railway Dashboard Load Times Impacted

Detected by Pingoru
Mar 25, 2026, 03:55 PM UTC
Resolved
Mar 25, 2026, 04:06 PM UTC
Duration
11m
Timeline · 4 updates
  1. investigating Mar 25, 2026, 03:55 PM UTC

    Railway Dashboard Load Times Impacted.

  2. identified Mar 25, 2026, 04:02 PM UTC

    Performance mitigations have been deployed to Railway.com, for any issues related to application connectivity, please raise a request on station.railway.com.

  3. monitoring Mar 25, 2026, 04:06 PM UTC

    Railway.com load times are now back to normal..

  4. resolved Mar 25, 2026, 04:06 PM UTC

    Railway.com load times are now back to normal..

Read the full incident report →

Major March 24, 2026

Request timeouts and Service Unavailable responses on Edge Network

Detected by Pingoru
Mar 24, 2026, 11:50 PM UTC
Resolved
Mar 25, 2026, 03:45 AM UTC
Duration
3h 55m
Timeline · 4 updates
  1. investigating Mar 24, 2026, 11:50 PM UTC

    We are aware of an issue affecting public traffic routing. Users may experience request timeouts or "Service Unavailable" errors when accessing their services. We are actively investigating and will provide updates as we learn more..

  2. identified Mar 25, 2026, 03:10 AM UTC

    We have identified the root cause and are working on a fix. Users may continue to experience request timeouts or "Service Unavailable" responses when accessing their services. We will provide updates as we make progress..

  3. monitoring Mar 25, 2026, 03:20 AM UTC

    A fix has been deployed, and we are monitoring for recovery. Users should see request timeouts and "Service Unavailable" responses subsiding. We will continue to monitor and provide a final update once we confirm stability..

  4. resolved Mar 25, 2026, 03:45 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 23, 2026

Connectivity issues in EU West (Amsterdam)

Detected by Pingoru
Mar 23, 2026, 11:15 PM UTC
Resolved
Mar 23, 2026, 11:52 PM UTC
Duration
37m
Timeline · 3 updates
  1. investigating Mar 23, 2026, 11:15 PM UTC

    We are aware of issues affecting public networking in the EU West (Amsterdam) region. Users may experience connection failures or intermittent errors when accessing their services in this region. We are actively investigating and will provide updates as we learn more..

  2. monitoring Mar 23, 2026, 11:32 PM UTC

    We have identified the source of the connectivity issues in EU West (Amsterdam) and have applied a fix. We are now monitoring to confirm stability..

  3. resolved Mar 23, 2026, 11:52 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 21, 2026

DNS Resolution Failures

Detected by Pingoru
Mar 21, 2026, 07:18 PM UTC
Resolved
Mar 21, 2026, 07:55 PM UTC
Duration
37m
Timeline · 3 updates
  1. identified Mar 21, 2026, 07:18 PM UTC

    We are aware of DNS resolution failures affecting Railway services. Users may experience failures when accessing their services via Railway-provided domains..

  2. monitoring Mar 21, 2026, 07:44 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Mar 21, 2026, 07:55 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 20, 2026

Degraded Performance in EU West

Detected by Pingoru
Mar 20, 2026, 02:12 PM UTC
Resolved
Mar 20, 2026, 04:22 PM UTC
Duration
2h 10m
Timeline · 4 updates
  1. investigating Mar 20, 2026, 02:12 PM UTC

    We are investigating reports of degraded performance for services in EU West. Some users may experience slow builds, delayed container creation, or elevated response times. Our team is actively investigating..

  2. identified Mar 20, 2026, 02:49 PM UTC

    We identified the source of degraded performance in EU West and are continuing to work on a fix for this incident..

  3. monitoring Mar 20, 2026, 03:22 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Mar 20, 2026, 04:22 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 19, 2026

Degraded network capacity on a single host

Detected by Pingoru
Mar 19, 2026, 03:30 AM UTC
Resolved
Mar 19, 2026, 05:09 AM UTC
Duration
1h 38m
Timeline · 3 updates
  1. investigating Mar 19, 2026, 03:30 AM UTC

    We are currently investigating this incident..

  2. monitoring Mar 19, 2026, 04:08 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Mar 19, 2026, 05:09 AM UTC

    This incident has been resolved. We found the issue pertaining to a single host in our fleet with elevated connections exhausting access in both the private and public network..

Read the full incident report →

Minor March 17, 2026

Suspected hardware failure affecting a subset of deployments in EU West

Detected by Pingoru
Mar 17, 2026, 10:57 AM UTC
Resolved
Mar 17, 2026, 12:40 PM UTC
Duration
1h 42m
Timeline · 5 updates
  1. investigating Mar 17, 2026, 10:57 AM UTC

    We are aware of an issue affecting a subset of services hosted in EU West. Some users may experience their services being unavailable or deployments failing to start. This is caused by a suspected hardware failure impacting a portion of our compute infrastructure in this region. We are actively working on recovery and services are beginning to come back online. Services with attached storage may take longer to fully recover..

  2. investigating Mar 17, 2026, 11:26 AM UTC

    We are currently investigating this incident. If your service does not have a volume attached, please try re-deploying it.

  3. identified Mar 17, 2026, 12:20 PM UTC

    We have identified the issue as a hardware failure on a single host in EU West. The affected infrastructure is being brought back online and workloads are recovering, some services have already been restored. Services with databases and attached storage may take a bit longer to fully come back. We will continue to provide updates as recovery progresses..

  4. monitoring Mar 17, 2026, 12:34 PM UTC

    All affected infrastructure is progressively recovering. If your service has not automatically recovered, please try redeploying. We are continuing to monitor..

  5. resolved Mar 17, 2026, 12:40 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 16, 2026

Outbound networking issues for a subset of hosts

Detected by Pingoru
Mar 16, 2026, 07:34 AM UTC
Resolved
Mar 16, 2026, 07:39 AM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Mar 16, 2026, 07:34 AM UTC

    We are currently investigating this incident. Egress traffic may be failing on certain hosts from 0620 UTC, primarily concentrated in Asia region..

  2. resolved Mar 16, 2026, 07:39 AM UTC

    This incident has been resolved. We identified a subset of misconfigured hosts primarily in Asia that were failing to route outbound traffic correctly during 0620 UTC \~ 0735 UTC and have applied a fix. We are adding additional monitoring to detect this class of issue earlier. We apologize for any disruption. If you continue to experience issues, please contact support at ..

Read the full incident report →

Minor March 15, 2026

Issues with networking on a subset of hosts

Detected by Pingoru
Mar 15, 2026, 09:27 AM UTC
Resolved
Mar 15, 2026, 10:04 AM UTC
Duration
36m
Timeline · 5 updates
  1. investigating Mar 15, 2026, 09:27 AM UTC

    We are currently investigating failures to reach the internet for a subset of deployments.

  2. investigating Mar 15, 2026, 09:32 AM UTC

    We were able to confirm impact to be limited to part of the fleet, but to be affecting all networking for affected deployments..

  3. identified Mar 15, 2026, 09:42 AM UTC

    We have identified the root cause and are working on a fix.

  4. monitoring Mar 15, 2026, 09:52 AM UTC

    We implemented a fix and are currently monitoring the result..

  5. resolved Mar 15, 2026, 10:04 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 13, 2026

Logs loading slowly

Detected by Pingoru
Mar 13, 2026, 03:25 PM UTC
Resolved
Mar 13, 2026, 05:31 PM UTC
Duration
2h 5m
Timeline · 5 updates
  1. investigating Mar 13, 2026, 03:25 PM UTC

    We're investigating an issue causing logs not to load..

  2. identified Mar 13, 2026, 03:39 PM UTC

    We've confirmed logs are loading with elevated delay. Our team is aware and working on a fix..

  3. monitoring Mar 13, 2026, 03:59 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. identified Mar 13, 2026, 04:50 PM UTC

    We're seeing continued degradation on logs loading time. We are continuing to work on a fix..

  5. resolved Mar 13, 2026, 05:31 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 12, 2026

Some repos may fail to snapshot code with metal builders

Detected by Pingoru
Mar 12, 2026, 08:29 PM UTC
Resolved
Mar 12, 2026, 08:58 PM UTC
Duration
29m
Timeline · 3 updates
  1. investigating Mar 12, 2026, 08:29 PM UTC

    We are currently investigating this incident. Non metal builders do not encounter this issue. .

  2. monitoring Mar 12, 2026, 08:49 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Mar 12, 2026, 08:58 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 12, 2026

Issues with Dockerfile build configs

Detected by Pingoru
Mar 12, 2026, 08:30 AM UTC
Resolved
Mar 12, 2026, 09:38 AM UTC
Duration
1h 8m
Timeline · 3 updates
  1. investigating Mar 12, 2026, 08:30 AM UTC

    We're investigating an issue causing certain build configurations (primarily for Dockerfile builds) to not resolve properly, causing builds to fail..

  2. identified Mar 12, 2026, 08:42 AM UTC

    We've identified the root cause and are working on a fix..

  3. resolved Mar 12, 2026, 09:38 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 9, 2026

Deployments stuck

Detected by Pingoru
Mar 09, 2026, 10:16 PM UTC
Resolved
Mar 09, 2026, 11:38 PM UTC
Duration
1h 21m
Timeline · 5 updates
  1. investigating Mar 09, 2026, 10:16 PM UTC

    We are aware of an issue where new builds may appear stuck and fail to complete or progress slowly. Existing running services are not affected. We are actively investigating and working on a fix..

  2. investigating Mar 09, 2026, 10:26 PM UTC

    Hobby, free and trial deploys have been temporarily disabled. We are continuing our investigation into the root issue.

  3. identified Mar 09, 2026, 10:56 PM UTC

    We have identified the root cause and are deploying a fix..

  4. monitoring Mar 09, 2026, 11:35 PM UTC

    We implemented a fix and are currently monitoring the result..

  5. resolved Mar 09, 2026, 11:38 PM UTC

    This incident has been resolved. New deployments for free, trial and hobby have been re-enabled..

Read the full incident report →

Minor March 9, 2026

TCP Proxy connectivity issues

Detected by Pingoru
Mar 09, 2026, 04:00 PM UTC
Resolved
Mar 09, 2026, 04:45 PM UTC
Duration
45m
Timeline · 4 updates
  1. investigating Mar 09, 2026, 04:00 PM UTC

    We are working on a fix for TCP proxy connection issues, primarily in the US East and Asia regions.

  2. identified Mar 09, 2026, 04:23 PM UTC

    We are continuing to work on a fix for this incident..

  3. monitoring Mar 09, 2026, 04:25 PM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Mar 09, 2026, 04:45 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 9, 2026

Deployments may fail to go out

Detected by Pingoru
Mar 09, 2026, 03:26 PM UTC
Resolved
Mar 09, 2026, 04:33 PM UTC
Duration
1h 6m
Timeline · 7 updates
  1. investigating Mar 09, 2026, 03:26 PM UTC

    We're investigating an issue causing a large portion of deployments to error, causing slowdowns across deployments and builds..

  2. identified Mar 09, 2026, 03:30 PM UTC

    We have identified the root cause of the issue and are working on a fix..

  3. identified Mar 09, 2026, 03:47 PM UTC

    We are continuing to work on a fix for this incident. New deploys for the hobby, free and trial plans have been paused until a fix is deployed..

  4. identified Mar 09, 2026, 04:04 PM UTC

    A fix has been pushed and is pending rollout. We're seeing issues with TCP proxy connections, related to this incident..

  5. monitoring Mar 09, 2026, 04:24 PM UTC

    We are seeing recovery for deployments. We are continuing to work on a fix for the TCP Proxy: .

  6. monitoring Mar 09, 2026, 04:26 PM UTC

    We are seeing recovery, and have re-enabled Free, Trial and Hobby deploys..

  7. resolved Mar 09, 2026, 04:33 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 6, 2026

[Retroactive] HTTP 503 Errors on railway.com and Railway-Hosted Services

Detected by Pingoru
Mar 06, 2026, 02:43 PM UTC
Resolved
Mar 06, 2026, 02:43 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Mar 06, 2026, 02:43 PM UTC

    Between 14:43 UTC and 14:50 UTC, users experienced HTTP 503 errors when accessing [railway.com](http://railway.com) and Railway-hosted services. We identified the root cause as our CDN provider (Fastly) reaching maximum connection limits to our edge network, which resulted in 503 errors for end users. The issue has been resolved and all services are operating normally. We are working with our CDN provider to implement safeguards to prevent this from recurring. We apologize for the disruption. If you continue to experience issues, please contact support at ..

Read the full incident report →

Minor March 5, 2026

Dashboard may fail to load for some people

Detected by Pingoru
Mar 05, 2026, 04:41 PM UTC
Resolved
Mar 05, 2026, 04:57 PM UTC
Duration
16m
Timeline · 3 updates
  1. identified Mar 05, 2026, 04:41 PM UTC

    We are continuing to work on a fix for this incident..

  2. monitoring Mar 05, 2026, 04:49 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Mar 05, 2026, 04:57 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 5, 2026

Degraded performance on public networking

Detected by Pingoru
Mar 05, 2026, 09:36 AM UTC
Resolved
Mar 05, 2026, 09:52 AM UTC
Duration
15m
Timeline · 3 updates
  1. identified Mar 05, 2026, 09:36 AM UTC

    We are working on a fix for network degradation on the railway edge..

  2. monitoring Mar 05, 2026, 09:50 AM UTC

    We've applied a fix and are seeing recovery across all regions..

  3. resolved Mar 05, 2026, 09:52 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor March 3, 2026

Issue with deployments

Detected by Pingoru
Mar 03, 2026, 11:05 PM UTC
Resolved
Mar 04, 2026, 12:23 AM UTC
Duration
1h 18m
Timeline · 8 updates
  1. investigating Mar 03, 2026, 11:05 PM UTC

    We're investigating an issue causing slowdowns in builds..

  2. investigating Mar 03, 2026, 11:27 PM UTC

    We've paused free, trial and hobby plan deploys as we continue investigating the issue..

  3. identified Mar 03, 2026, 11:32 PM UTC

    We've identified the root cause of the issue and are working on a fix. Free, Trial and Hobby provisions remain disabled at this time..

  4. identified Mar 03, 2026, 11:51 PM UTC

    We are continuing to work on a fix for this incident..

  5. identified Mar 03, 2026, 11:52 PM UTC

    We are continuing to work on a fix for this incident..

  6. monitoring Mar 03, 2026, 11:59 PM UTC

    We implemented a fix and are currently monitoring the result. Non-pro deploys remain disabled until we catch up with the deploy queue..

  7. monitoring Mar 04, 2026, 12:16 AM UTC

    Hobby, free and trial deployments have been re-enabled. We are still monitoring, but have seen full recovery on our deploy systems..

  8. resolved Mar 04, 2026, 12:23 AM UTC

    This incident has been resolved..

Read the full incident report →