Railway Outage Check
Is Railway Down Right Now?
✅ Railway is up and working normally. Checked: 4:06 AM (GMT+8).
Auto-refreshing live data in 60s
Railway's Official Status Page
- App deployments and environments
- Managed database instances
- Background service runners
| Component | Status |
|---|---|
| API Portal | Operational |
| Core Service | Operational |
| OAuth Integrations | Operational |
| Website | Operational |
SLA Grade: A+
Based on 90-day verified uptime
100.000%
Uptime
64m
Mean Resolution Time (MTTR)
6.7
Avg Incidents / Month
40d ago
Last Incident
90 Days AgoToday
Railway API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 53m
Affected: API Requests, API Portal
Railway Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 6m
Affected: Website, DNS Services
Railway Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 52m
Affected: Website, DNS Services
Railway Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 3m
Affected: Website, DNS Services
Railway Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 1h 8m
Affected: Core Service, Website
Are you having problems with Railway?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Railway maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 64 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.