Compare the status, incidents stats and history between Vercel and AWS
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.
9:57 AM PDT Between 8:25 AM and 9:16 AM PDT, we experienced elevated packet loss and latency to a small set of internet destinations in the US-WEST-2 Region. Connectivity within the US-WEST-2 Regi...
7:34 PM PST We are investigating increased STS API error rates in the US-GOV-WEST-1 Region. We are actively working toward resolution. 8:08 PM PST We have identified the cause of the increased...
7:06 PM PST We are investigating increased error rates that block the listing of exportable AMIs for the AWS Snowball Management Console blocking Edge Compute orders in the US-GOV-EAST-1 Region. ...
Try it out! How much time you'll save your team, by having the outages information close to them?