On 23 October 2026, Vercel's Logs and Observability data was delayed for 1h 5m. The fault sat inside Vercel's own data pipeline, not in your deployed application.
Started
16:31 UTC
Duration
Lasted 1h 5m
Source
IsDown
Next time
Vercel is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Observability, Logs
What happened?
Vercel's status page logged one incident on this day, titled "Delays in Logs and Observability data". It started at 16:31 UTC and ran for 1h 5m before being marked resolved at 17:32 UTC. Vercel posted two updates in total: an "identified" note at 16:31 saying the cause had been found and a fix was in progress, and a "resolved" note at 17:32 saying the delays had been cleared. Vercel did not publish any detail on what caused the delay, so the root cause is not on the record. Two components were listed as affected: Logs and Observability. No other parts of the Vercel platform, such as deployments or the edge network, appear in the affected components list for this incident. There were no user reports filed in the window covered by this page. Over the past 90 days Vercel has logged 21 incidents with a median duration of 1 hour 19 minutes, so this one resolved faster than the typical incident in that period. Across all time Vercel has recorded 548 incidents, an average of 8.6 per month. A single filing from Vercel is the only account available here, so the detail on what actually broke behind the scenes stays limited to what they chose to publish.
Learning
UptimeRobot's own probes watched Vercel's API from both the EU and North America through this window and recorded 100% uptime over 24 hours, 7 days and 30 days, with no incident registered against this event. That is not a contradiction. This outage lived in the logging and observability pipeline, a layer that sits behind the API your product calls, so a clean response from the API tells you nothing about whether your logs and traces are arriving on time. If your own monitoring only checks that your endpoints respond, an incident like this passes through invisibly, because your application keeps serving requests while its telemetry quietly backs up. This is the general shape of a provider-side partial failure: the part you depend on for debugging goes dark while the part you depend on for serving traffic stays up. Vercel's 90 day history shows this kind of thing is not rare, with 21 incidents and a typical duration over an hour. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.