Compare the status, incidents stats and history between Linode and Fly.io
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.
Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times: - Chicago (...
Our team is investigating an issue affecting connectivity in our US-IAD (Washington) data center. During this time, users may experience intermittent connection timeouts and errors for all services...
Our team is investigating a service issue that affects the Linode Cloud Manager and API. During that time, some users may experience issues when attempting to access these systems. Specifically, we...
We are investigating error 503 when making requests to our GraphQL API, or running flyctl commands.
When deploying with bluegreen strategy some green machines (new app version) won't pass healthchecks. Temporary workaround: unless bluegreen is a must for your app you can temporarily deploy using ...
We are currently investigating inbound network connectivity issues in SJC region. Users routed to SJC may be unable to access apps, or latency may be increased.
14-day free trial · No credit card required · No code required