Railway statusManual checkVerified May 24, 2026Source: status.railway.com
Is Railway down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from status.railway.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Railway status
Railway is a PaaS for services, databases, and ephemeral environments. Most incidents are scoped to a single component (Builds, Deploys, the API) and resolve in under an hour.
Components and surfaces that can break
- Surface 01
Services (web, worker) and Deploys.
- Surface 02
Postgres, Redis, MongoDB, and other Railway data plugins.
- Surface 03
Builds, the public Dashboard, and the GraphQL API.
Recent Railway incidents
Railway maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Railway is actually down
Check if Builds vs Deploys vs Runtime is affected
status.railway.com splits these out. If only Builds is red, your running services are still serving traffic — you just can't ship a new deploy. Don't panic-retry deploys during a Builds outage.
Railway has no native cron — verify your trigger
If you set up Railway 'cron' via a third-party trigger (GitHub Actions, an internal cron container, an external scheduler), the trigger is what's affected when your job stops firing — not Railway itself.
Avoid redeploy-on-error loops
Some CI setups redeploy on health-check failure. During a Railway incident this can amplify the blast radius. Disable the auto-redeploy until the platform is green.
Keep firing through the incident
Schedule your own Railway health check with Crontap
Railway does not ship a native cron primitive. Common patterns are an internal cron container (always-on VM cost), GitHub Actions on a schedule (subject to GitHub drift), or external HTTP cron. Crontap fires your Railway service URL on a cron you control, with retries and a run log.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Railway status: FAQ
- Where is the Railway status page?
- status.railway.com publishes component-level status and a history of incidents. Their Discord and Twitter are usually faster than the status page for very fresh incidents.
- Does Railway have a built-in cron?
- No. Railway expects you to run cron inside one of your services or use an external scheduler. Both approaches work; external is usually cheaper because you don't pay for an idle worker. Full pattern walkthrough in our Railway HTTP cron post.
- How do I monitor a Railway service from outside Railway?
- Set a Crontap schedule against your service URL (or a dedicated /health endpoint) at 1- or 5-minute cadence. You'll get failure alerts independent of Railway's own health checks.