Compare the status, incidents stats and history between Fly.io and Vercel
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 have noticed a spike in packet loss across the FRA region at around 14:44 UTC caused by an upstream issue. This has recovered since 14:47 UTC, and we are currently monitoring the situation along...
We have noticed a temporary blip in our upstream network(s) between 16:38-16:40 UTC that affected our platform. This has been resolving and we are monitoring for any continuing effects.
We were alerted to elevated error rates for machine creates and updates. A deploy caused a validation error which is now being reverted.
We have identified an issue affecting a subset of Vercel Dashboard features related to Teams. We are currently investigating and will provide additional information as this progresses.
We are skipping the domain assignment erroneously for deployments that are intended to be production.
We are aware of an issue affecting the delivery of blobs that contain double slashes (//) in their URLs. These blobs may not be accessible at the moment due to an unexpected change in our URL handl...
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime