Railway vs. Netlify

Compare the status, incidents stats and history between Railway and Netlify

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

Railway

Railway current official status is Operational

Statistics

1
Incidents in the last 7 days
16
Incidents in the last 30 days
34
Incidents in the last 90 days

Latest incidents

Resolved Single host on Railway Metal (us-west2) is offline

We are currently investigating this incident. A small subset of impacted users on us-west2 region may notice their deployments are unresponsive during this period. You can re-deploy your service to...

Resolved Dashboard Timeouts

Some users may notice dashboard timeouts. We are rolling out a fix for this

Resolved Elevated Latency all Edge proxies

We have identified the issue, implemented a fix, and are already seeing recovery.

Netlify

Netlify current official status is Operational

Statistics

4
Incidents in the last 7 days
6
Incidents in the last 30 days
18
Incidents in the last 90 days

Latest incidents

Resolved Function invocation issue for functions using the ap-southeast-2 region

We have identified an issue starting at 20:38 UTC which is preventing invocations for functions deployed to the ap-southeast-2 region for the High-Performance Edge Network only. We are working on a...

Resolved Domain purchasing currently unavailable

We are currently experiencing issues with the purchasing of new domain names. Domain renewals are unaffected.

Resolved Elevated API Latency and Error Rates Starting at 11:27 UTC

Starting 11:27 UTC our API started to experience high latency and elevated error rates. We are investigating the issue.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required