Compare the status, incidents stats and history between Vercel 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.
We are observing degraded intake of Analytics (Audiences and Web Vitals). We are working closely with the team to resolve the issue as soon as possible.
We're investigating a delay in delivering Vercel Logs to Logdrains for requests to Vercel websites received in the iad1 region. We're currently seeing a delay of 15 minutes. There's no data loss. A...
We are currently investigating degraded performance in our FRA1 (Frankfurt) region.
We're seeing an increased number of errors or timeouts when pushing images to registry.fly.io during deploys.
Our Consul cluster is experiencing an outage. This impacts queries to our API, including creating and modifying apps, as well as incoming network requests for recently deployed apps.
Causing intermittent issues deploying to SIN.
Try it out! How much time you'll save your team, by having the outages information close to them?