Vercel status: is it down right now?
Our own check of vercel.com from Europe and the US, every 3 minutes, with recent history.
vercel.com responded. The page answered normally in 69 ms.
vercel.com responded.
The page answered normally in 69 ms.
Checked (just now) from Europe and the US, automatic every 3 minutes.
Follow Vercel's public website. Free 10-minute checks, no card. This does not check every feature.
Run a website? Check my website
This checks the response from vercel.com. It does not test playback, login or every Vercel feature.
Vercel status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 5. A problem has to fail two checks in a row before we record it.
Watch your site free
This page is for their outage. Your own site can fail the same way. Free plan: 3 monitors, SSL alerts, no card.
Watch your site freeabout this service
About Vercel
Vercel hosts Next.js and other JAMstack apps on a global edge network, with serverless and edge functions, image optimisation, ISR, and managed DNS. Outages usually fall into one of three buckets: the deploy pipeline (builds queuing or failing even though existing production traffic is fine), the edge network (user-facing latency spikes or 500s from regional POPs), or function runtimes (cold starts failing or exceeding execution limits). Teams shipping continuously notice build-queue issues within minutes because their CI/CD feels stuck.
The official Vercel status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster.
outage patterns
How Vercel outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Vercel is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Vercel.
Common signs Vercel is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Vercel but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Vercel is degraded
When Vercel is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Vercel itself.
monitor 24/7
Monitor Vercel automatically.
Get independent alerts when the public Vercel endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Vercel on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Vercel uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Vercel down right now?
See the latest check of vercel.com and its timestamp at the top of this page. If Vercel is down, you can also check the official status page for extra context.
How do I check if Vercel is having issues?
This page checks the public Vercel endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Vercel goes down?
Set up a free monitor for vercel.com on Visual Sentinel for 10-minute checks with email and push alerts. Paid plans add checks as fast as 60 seconds and more notification channels.
Where can I find Vercel outage context?
The official Vercel status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster. Visual Sentinel checks the public Vercel endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why are my Vercel deployments queuing but existing traffic works?
The Vercel build pipeline and the edge runtime serving production traffic are independent systems. A build-queue incident stalls new deploys while visitors continue to hit the last-good deployment on the edge network.
Does a Vercel edge outage break all regions?
Usually not. Vercel runs multiple edge regions and traffic routes to the nearest healthy one. Single-region incidents cause localised latency spikes. Global edge incidents are rare but do happen and affect every visitor.