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.

Source: status.railway.com

314incidents recorded
145last 12 months
32last 90 days
3 hourstypical duration

Incidents, newest first

Minor February 25, 2026 Builds and deployments are slow to progress. 2h 59m US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))

Started Feb 25, 2026, 06:16 PM UTC· resolved Feb 25, 2026, 09:15 PM UTC

  1. investigating Feb 25, 2026, 06:16 PM UTC

    We are currently investigating this incident. While we investigate, we have paused builds for Free and Trial users.

  2. identified Feb 25, 2026, 06:31 PM UTC

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

  3. identified Feb 25, 2026, 07:11 PM UTC

    We have released a fix and are currently working through a backlog of queued builds and deployments.

  4. identified Feb 25, 2026, 07:35 PM UTC

    We are continuing to work on a fix for this incident. Hobby builds and deployments are paused to help clear the backlog.

  5. identified Feb 25, 2026, 08:18 PM UTC

    We are continuing to work on a fix for this incident. Hobby builds have been re-enabled.

  6. identified Feb 25, 2026, 08:34 PM UTC

    We are continuing to work on a fix for this incident. Builds and deployments for Free and Trial have been re-enabled, and the backlog is continuing to progress.

  7. monitoring Feb 25, 2026, 08:49 PM UTC

    We implemented a fix and are currently monitoring the result.

  8. resolved Feb 25, 2026, 09:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 21, 2026 A subset of domains are failing with a 503 error page. 1h 21m US East (Virginia, USA) (Networking — Public (US East)), US West (California, USA) (Networking — Public (US West)), EU West (Amsterdam, Netherlands) (Networking — Public (EU West)), Southeast Asia (Singapore) (Networking — Public (Southeast Asia))

Started Feb 21, 2026, 05:34 AM UTC· resolved Feb 21, 2026, 06:55 AM UTC

  1. investigating Feb 21, 2026, 05:34 AM UTC

    We are currently investigating this incident. Some users may see an error page with "Error 503".

  2. identified Feb 21, 2026, 05:56 AM UTC

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

  3. identified Feb 21, 2026, 06:07 AM UTC

    We are continuing to work on a fix for this incident. Some users may see a 429 error as a result.

  4. monitoring Feb 21, 2026, 06:29 AM UTC

    We implemented a fix and are currently monitoring the result.

  5. resolved Feb 21, 2026, 06:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 20, 2026 DNS resolution is failing for some domains. 6h 1m US East (Virginia, USA) (Networking — Public (US East)), US West (California, USA) (Networking — Public (US West)), EU West (Amsterdam, Netherlands) (Networking — Public (EU West)), Southeast Asia (Singapore) (Networking — Public (Southeast Asia))

Started Feb 20, 2026, 06:24 PM UTC· resolved Feb 21, 2026, 12:25 AM UTC

  1. investigating Feb 20, 2026, 06:24 PM UTC

    We are currently investigating this incident.

  2. monitoring Feb 20, 2026, 06:30 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. monitoring Feb 20, 2026, 07:21 PM UTC

    Cloudflare has identified an issue affecting DNS connectivity.

  4. monitoring Feb 20, 2026, 08:17 PM UTC

    We are seeing full recovery for all Railway domains since 18:30 UTC. Cloudflare has indicated there should be no further impact, and we are continuing to monitor.

  5. resolved Feb 21, 2026, 12:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2026 Public networking traffic may time out. 7h 1m US East (Virginia, USA) (Networking — Public (US East)), US West (California, USA) (Networking — Public (US West)), EU West (Amsterdam, Netherlands) (Networking — Public (EU West)), Southeast Asia (Singapore) (Networking — Public (Southeast Asia))

Started Feb 19, 2026, 02:18 PM UTC· resolved Feb 19, 2026, 09:19 PM UTC

  1. investigating Feb 19, 2026, 02:18 PM UTC

    We are currently investigating this incident. A subset of users may experience their application returning a 502 error, timing out, or failing to connect to the TCP proxy.

  2. identified Feb 19, 2026, 02:55 PM UTC

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

  3. monitoring Feb 19, 2026, 03:36 PM UTC

    We are seeing full recovery across all public networking pathways.

  4. identified Feb 19, 2026, 03:37 PM UTC

    We are seeing some network requests time out again. We are continuing to work on a fix for this incident.

  5. monitoring Feb 19, 2026, 04:16 PM UTC

    We are again seeing full recovery across all public networking pathways.

  6. resolved Feb 19, 2026, 04:44 PM UTC

    This incident has been resolved.

  7. investigating Feb 19, 2026, 06:08 PM UTC

    We are seeing some network requests time out again. We are continuing to work on a fix for this incident.

  8. monitoring Feb 19, 2026, 07:21 PM UTC

    We implemented a fix and are currently monitoring the result.

  9. resolved Feb 19, 2026, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 13, 2026 Some users might not be able to log in. 1h 4m Railway (Dashboard — railway.com)

Started Feb 13, 2026, 01:00 AM UTC· resolved Feb 13, 2026, 02:05 AM UTC

  1. investigating Feb 13, 2026, 01:00 AM UTC

    We are currently investigating this incident. All running services are fully operational, only login is affected.

  2. identified Feb 13, 2026, 01:12 AM UTC

    A Redis shard on the Dashboard is timing out. A subset of users may see dashboard timeouts

  3. monitoring Feb 13, 2026, 01:22 AM UTC

    We implemented a fix and are currently monitoring the result. We're seeing recovery on queued deployments as well.

  4. resolved Feb 13, 2026, 02:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026 GitHub is experiencing degraded performance issues 1h 39m External & Third-Party Integrations (GitHub — Auto-Deploys)

Started Feb 09, 2026, 07:08 PM UTC· resolved Feb 09, 2026, 08:48 PM UTC

  1. investigating Feb 09, 2026, 07:08 PM UTC

  2. resolved Feb 09, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 9, 2026 Deploys may fail to go through 44m US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))

Started Feb 09, 2026, 02:28 PM UTC· resolved Feb 09, 2026, 03:13 PM UTC

  1. investigating Feb 09, 2026, 02:28 PM UTC

    We're investigating this incident

  2. identified Feb 09, 2026, 02:32 PM UTC

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

  3. resolved Feb 09, 2026, 03:13 PM UTC

    Our fix is live and customers report deploys working again!

Read the full incident report →

Critical February 4, 2026 Metrics may be unavailable for some users 4h 27m Observability (Metrics)

Started Feb 04, 2026, 05:01 PM UTC· resolved Feb 04, 2026, 09:29 PM UTC

  1. investigating Feb 04, 2026, 05:01 PM UTC

    We are currently investigating this incident.

  2. identified Feb 04, 2026, 07:03 PM UTC

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

  3. monitoring Feb 04, 2026, 08:59 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Feb 04, 2026, 09:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 3, 2026 Metrics may be unavailable for certain users 3h 21m Observability (Metrics)

Started Feb 03, 2026, 10:12 PM UTC· resolved Feb 04, 2026, 01:33 AM UTC

  1. investigating Feb 03, 2026, 10:12 PM UTC

    We are currently investigating this incident.

  2. identified Feb 03, 2026, 10:28 PM UTC

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

  3. monitoring Feb 04, 2026, 01:14 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Feb 04, 2026, 01:33 AM UTC

    We merged a fix and reports point to metrics being healthy.

Read the full incident report →

Minor February 3, 2026 GitHub is reporting degraded performance with GitHub actions 4h 13m External & Third-Party Integrations (GitHub — Auto-Deploys)

Started Feb 03, 2026, 04:43 PM UTC· resolved Feb 03, 2026, 08:56 PM UTC

  1. investigating Feb 03, 2026, 04:43 PM UTC

    is currently investigating this and will provide updates with information as it comes.

  2. resolved Feb 03, 2026, 08:56 PM UTC

    Github reported full system recovery

Read the full incident report →

Major February 2, 2026 GitHub is reporting major outages with GitHub Actions 1h 58m External & Third-Party Integrations (GitHub — Auto-Deploys)

Started Feb 02, 2026, 10:44 PM UTC· resolved Feb 03, 2026, 12:42 AM UTC

  1. investigating Feb 02, 2026, 10:44 PM UTC

  2. resolved Feb 03, 2026, 12:42 AM UTC

    GitHub reports suspected full recovery.

Read the full incident report →

Minor January 29, 2026 NPM is having degraded performance Installing and Viewing Packages 56m External & Third-Party Integrations (Package Registry — npm)

Started Jan 29, 2026, 08:08 PM UTC· resolved Jan 29, 2026, 09:04 PM UTC

  1. investigating Jan 29, 2026, 08:08 PM UTC

    They are currently investigating this issue.

  2. monitoring Jan 29, 2026, 08:25 PM UTC

    NPM Implemented a fix and is monitoring results.

  3. resolved Jan 29, 2026, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026 GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue. 4h 8m External & Third-Party Integrations (GitHub — Auto-Deploys)

Started Jan 29, 2026, 03:06 PM UTC· resolved Jan 29, 2026, 07:15 PM UTC

  1. investigating Jan 29, 2026, 03:06 PM UTC

    GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue.

  2. identified Jan 29, 2026, 03:25 PM UTC

    We have disabled GitHub log in to reduce rate-limit pressure on the system.

  3. identified Jan 29, 2026, 05:38 PM UTC

    We have rolled out additional fixes to improve GitHub callpath resiliency. We are monitoring their effectiveness and will issue an update once we finish monitoring.

  4. monitoring Jan 29, 2026, 06:13 PM UTC

    We have observed no further GitHub rate limiting in the last 60 minutes and we are reanbling GitHub authentication.

  5. resolved Jan 29, 2026, 07:15 PM UTC

    Our monitors have shown that we have good effect on our changes, although we have improvement, we are still monitoring the impact for all customers.

Read the full incident report →

Minor January 28, 2026 Some workloads may have delayed or no logs. We are investigating the cause. 52m Observability (Logs)

Started Jan 28, 2026, 07:13 PM UTC· resolved Jan 28, 2026, 08:05 PM UTC

  1. investigating Jan 28, 2026, 07:13 PM UTC

    Some workloads may have delayed or no logs. We are investigating the cause.

  2. resolved Jan 28, 2026, 08:05 PM UTC

    Logs are working nominally.

Read the full incident report →

Minor January 28, 2026 GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers. 6h 17m External & Third-Party Integrations (GitHub — Auto-Deploys)

Started Jan 28, 2026, 06:02 PM UTC· resolved Jan 29, 2026, 12:20 AM UTC

  1. investigating Jan 28, 2026, 06:02 PM UTC

    GitHub logins or deployments may timeout due to downstream rate limits. We are working on long term resolution for our customers.

  2. identified Jan 28, 2026, 06:41 PM UTC

    We are implementing workarounds to increase GH throughput to prevent GH ratelimiting.

  3. identified Jan 28, 2026, 07:12 PM UTC

    Customers report recovery in most GH operations, waiting to merge long term fixes until resolving the incident.

  4. identified Jan 28, 2026, 09:20 PM UTC

    We have temporarily disabled GitHub logins while we work to reduce load on the GH downstream endpoints to regain quota.

  5. monitoring Jan 29, 2026, 12:06 AM UTC

    We have restored GitHub logins for everyone. We are monitoring the performance and recovery for all customers.

  6. resolved Jan 29, 2026, 12:20 AM UTC

    We have confirmed that GitHub login, and repo access is working for all customers on the platform. We apologize for the impact and we will publish a public retro.

Read the full incident report →

Major January 28, 2026 Applying staged changes might take longer than usual 15m Railway (Dashboard — railway.com)

Started Jan 28, 2026, 04:48 PM UTC· resolved Jan 28, 2026, 05:04 PM UTC

  1. investigating Jan 28, 2026, 04:48 PM UTC

    Applying staged changes might take longer than usual

  2. monitoring Jan 28, 2026, 04:54 PM UTC

    The staged changes queue appears recovered, we are monitoring the recovery.

  3. resolved Jan 28, 2026, 05:04 PM UTC

    Staged changes are applying for all customers on the platform.

Read the full incident report →

Minor January 26, 2026 Node Yarn PKG mirror is unavailible causing failed builds. 2h 20m External & Third-Party Integrations (Package Registry — npm)

Started Jan 26, 2026, 08:58 PM UTC· resolved Jan 26, 2026, 11:18 PM UTC

  1. investigating Jan 26, 2026, 08:58 PM UTC

    Node Yarn PKG mirror is unavailible causing failed builds.

  2. monitoring Jan 26, 2026, 11:18 PM UTC

    The yarn mirror is operational.

  3. resolved Jan 26, 2026, 11:18 PM UTC

    The yarn mirror is operational.

Read the full incident report →

Major January 21, 2026 Log delivery delay across all regions 37m Observability (Logs)

Started Jan 21, 2026, 08:30 PM UTC· resolved Jan 21, 2026, 09:08 PM UTC

  1. investigating Jan 21, 2026, 08:30 PM UTC

    We are aware of delays in log delivery across all regions. Deploy logs may appear with significant delay on the dashboard. Our team is actively investigating and working to restore real-time log delivery. We will provide updates as we learn more.

  2. identified Jan 21, 2026, 08:37 PM UTC

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

  3. monitoring Jan 21, 2026, 08:57 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jan 21, 2026, 09:08 PM UTC

    This incident has been resolved. Some build and deploy logs may have been dropped during this incident window. We apologize for any inconvenience caused. Please reach out to us at if you are still experiencing issues with build or deploy logs.

Read the full incident report →

Minor January 4, 2026 Deployment Degredation 30m US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))

Started Jan 04, 2026, 09:15 PM UTC· resolved Jan 04, 2026, 09:45 PM UTC

  1. investigating Jan 04, 2026, 09:15 PM UTC

    We are currently investigating this incident.

  2. identified Jan 04, 2026, 09:25 PM UTC

    We've disabled deployments for Trial, Free, and Hobby plans.

  3. monitoring Jan 04, 2026, 09:38 PM UTC

    We've reenabled deployments on all plans.

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

    This incident has been resolved.

Read the full incident report →

Minor December 20, 2025 Canvas updates are slow 1h 32m Railway (Dashboard — railway.com)

Started Dec 20, 2025, 08:08 AM UTC· resolved Dec 20, 2025, 09:40 AM UTC

  1. investigating Dec 20, 2025, 08:08 AM UTC

    The Canvas is currently experiencing degraded performance. Updates to projects may take longer than usual to persist, which can result in increased loading times.

  2. identified Dec 20, 2025, 08:41 AM UTC

    We’ve identified a potential root cause and are currently evaluating a fix.

  3. monitoring Dec 20, 2025, 09:08 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Dec 20, 2025, 09:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 16, 2025 We are investigating issues with elevated network latency and slow deploys 1d 11h US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))

Started Dec 16, 2025, 07:10 AM UTC· resolved Dec 17, 2025, 07:04 PM UTC

  1. investigating Dec 16, 2025, 07:10 AM UTC

    We are currently investigating this incident.

  2. identified Dec 16, 2025, 07:37 AM UTC

    We continue to see degradation across all regions, and are working on a fix. We have paused new deploys as we investigate.

  3. monitoring Dec 16, 2025, 08:06 AM UTC

    We are rolling out a fix and are seeing recovery in all regions. Deploys have been re-enabled

  4. monitoring Dec 16, 2025, 08:30 AM UTC

    We have seen recovery in all regions. We are continuing to monitor this incident.

  5. monitoring Dec 16, 2025, 09:08 AM UTC

    We are seeing further degradation, particularly in EU regions. We are continuing to work on a permanent fix.

  6. monitoring Dec 16, 2025, 10:30 AM UTC

    We are still monitoring this incident.

  7. monitoring Dec 16, 2025, 11:00 AM UTC

    We have seen widespread recovery and are continuing to monitor this incident.

  8. resolved Dec 16, 2025, 11:20 AM UTC

    This incident has been resolved.

  9. investigating Dec 17, 2025, 07:04 PM UTC

    A post-mortem of this incident has been published at .

Read the full incident report →

Minor December 11, 2025 Metal Registry issues in Europe 1h EU West (Amsterdam, Netherlands) (Deployments (EU West))

Started Dec 11, 2025, 11:45 AM UTC· resolved Dec 11, 2025, 12:45 PM UTC

  1. investigating Dec 11, 2025, 11:45 AM UTC

    We're currently investigating issues with our EU image registry. Deploys may get stuck or retry until we push out a fix.

  2. resolved Dec 11, 2025, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 8, 2025 Our backend is experiencing connectivity issues. 6h 42m Railway (Dashboard — railway.com), Authentication (Login — GitHub), Authentication (Login — Google)

Started Dec 08, 2025, 03:18 PM UTC· resolved Dec 08, 2025, 10:00 PM UTC

  1. investigating Dec 08, 2025, 03:18 PM UTC

    We are currently investigating this incident.

  2. resolved Dec 08, 2025, 03:26 PM UTC

    This incident has been resolved.

  3. investigating Dec 08, 2025, 10:00 PM UTC

    A post-mortem of this incident has been published at

Read the full incident report →

Minor December 6, 2025 Elevated latency and error rates for edge network in US East 22m US East (Virginia, USA) (Networking — Public (US East))

Started Dec 06, 2025, 10:46 AM UTC· resolved Dec 06, 2025, 11:09 AM UTC

  1. investigating Dec 06, 2025, 10:46 AM UTC

    We are currently investigating this incident.

  2. monitoring Dec 06, 2025, 10:56 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Dec 06, 2025, 11:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 25, 2025 Deploys and configuration changes delayed 20h 53m Railway (Dashboard — railway.com), US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)) and 1 more

Started Nov 25, 2025, 10:56 PM UTC· resolved Nov 26, 2025, 07:49 PM UTC

  1. investigating Nov 25, 2025, 10:56 PM UTC

    We are currently investigating this incident.

  2. investigating Nov 25, 2025, 11:04 PM UTC

    We are pausing deploys for Free, Trial, and Hobby. Pro deploys will continue, albeit slowly.

  3. identified Nov 25, 2025, 11:19 PM UTC

    We are continuing to work on a fix for this incident. Free, Trial, and Hobby deployments remain paused.

  4. identified Nov 26, 2025, 12:21 AM UTC

    We are continuing to work on a fix for this incident. Free, Trial, and Hobby deployments remain paused, and Pro deploys are delayed.

  5. identified Nov 26, 2025, 12:35 AM UTC

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

  6. identified Nov 26, 2025, 12:39 AM UTC

    The dashboard is now fully operational. We are continuning to work on a fix for significant delay in deployments.

  7. identified Nov 26, 2025, 12:57 AM UTC

    Our task queue is experiencing an outage. The following operations may fail or be significantly delayed: * Builds and deployments (may appear stuck on "Initializing") * Service setting changes (e.g., updating environment variables) * Environment creation and deployment removals We're actively working on a fix and will provide updates shortly.

  8. monitoring Nov 26, 2025, 12:59 AM UTC

    Recovery is underway. Pro and Hobby deploys have been restored. Free and Trial deploys will be re-enabled shortly.

  9. monitoring Nov 26, 2025, 01:08 AM UTC

    Free and Trial deployments have been re-enabled.

  10. resolved Nov 26, 2025, 01:22 AM UTC

    This incident has been resolved. We apologize for the service disruption. A post-mortem of this incident will be published shortly.

  11. investigating Nov 26, 2025, 07:49 PM UTC

    A post-mortem of this incident has been published at

Read the full incident report →