Independent monitoring
Vercel status
OperationalMerlonix has monitored Vercel around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations and any incidents Vercel reported.
Snapshot as observed by Merlonix at Sep 6, 2026, 01:58 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.
30-day observation timeline
Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects Vercel’s own published component-level status and may mean a single component was affected while the overall service was fine.
Observations recorded
16
distinct status changes over 21 days we have data for
Most recent change
Sep 4, 2026
last time the observed status changed
Days by observed status
- Degraded21d
What Merlonix monitors for Vercel
Merlonix polls Vercel's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of Vercel.
Recent incidents Vercel reported
No incidents recorded from Vercel’s status source in the current observation window.
Get alerted the moment Vercel has a bad day.
Merlonix watches Vercel and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.
Other vendors we monitor