Is Vercel down?
Updates every minute
Two independent answers, side by side: what Infra Agent’s own checks observe from multiple regions, and what Vercel reports on its official status page. We never mix the two.
Vercel looks up right now
Infra Agent's checks are succeeding from all 3 of our regions, and Vercel is not reporting any problems on its official status page.
Infra Agent checks
Independent · our own probes
Our checks are reaching Vercel from all 3 regions.
Last checked less than a minute ago
Vercel’s official status
Provider-reported · official feed
Vercel reports "All Systems Operational" on its official status page.
Our regional check results
The latest probe from each of our monitoring regions. A provider only counts as having problems when failures repeat across consecutive checks and more than one region.
| Check region | Main website (vercel.com) | API (api.vercel.com) | Vercel-hosted site (nextjs.org) |
|---|---|---|---|
| Amsterdam, NL | 140 ms | 525 ms | 198 ms |
| Ashburn, US (East) | 130 ms | 228 ms | 83 ms |
| San Jose, US (West) | 53 ms | 42 ms | 92 ms |
What we check
- Main website (vercel.com)https://vercel.com
- API (api.vercel.com)https://api.vercel.com/v2/user
- Vercel-hosted site (nextjs.org)https://nextjs.org
Last 24 hours
Response times and failures from Infra Agent’s own checks of Vercel.
Recent Vercel incidents
As reported by Vercel on its official status page.
- NoticeVercel Community temporarily unavailablestarted 3 days ago · resolved 2 days ago
- NoticeTelemetry data loss for Drainsstarted 4 days ago · resolved 5 days ago
- MajorTimeouts loading charts and observability data in Dashboardstarted 6 days ago · resolved 6 days ago
- CriticalDashboard authentication errorsstarted 6 days ago · resolved 6 days ago
- MinorIncreased invocation failures for Hobby Team functionsstarted 11 days ago · resolved 11 days ago
- MinorGitHub-linked deployments and authentication affectedstarted 12 days ago · resolved 12 days ago
Vercel looks down for you? Work through this
Vercel separates serving existing deployments from building new ones, and most incidents hit one side, not both. Figuring out which side is broken tells you what to do next.
Deployed site down vs. builds failing
If your production site loads but new deployments fail or hang, the incident is in Vercel's build pipeline. Your visitors are fine, and the fix is to wait rather than redeploy repeatedly. If the site itself is unreachable, the edge network is affected.
Compare your custom domain with the .vercel.app URL
Every deployment has a *.vercel.app URL. If that URL works but your custom domain doesn't, the problem is DNS, so check that your domain still points at Vercel (an A record to 76.76.21.21 or a CNAME to cname.vercel-dns.com) rather than assuming a platform outage.
Roll back instantly instead of redeploying
If your site broke right after a deploy during a suspected incident, use Instant Rollback on the project's Deployments page to promote the previous deployment. It doesn't run a new build, so it works even when the build system is degraded.
Check function and middleware errors separately
Serverless Functions and Edge Middleware can be degraded while static pages keep serving from the CDN. If only API routes or middleware-protected pages fail, look for a Functions-scoped incident on Vercel's status page and in your project's runtime logs.
Watch for DNS-scoped incidents
Vercel also operates the DNS for domains bought or managed through it. A DNS incident can make sites unreachable even though the edge network is healthy. The status page lists DNS as its own component.
Check your own website
Provider looks fine but your site is down, or the other way around? Test any URL from our servers right now. No account needed.
About Vercel
Vercel hosts frontend applications and serves them through its global edge network, with builds and serverless functions behind the scenes. An incident can affect new deployments while already-deployed sites keep serving, or the other way around.
Also check: Is Cloudflare down? · Is Fly.io down? · Is DigitalOcean down? · All providers
Infra Agent is an independent monitoring service and is not affiliated with, endorsed by, or sponsored by Vercel. The Vercel name is used for identification only. “Official status” information is republished from Vercel’s public status feed and always links back to the source.
Vercel outage FAQ
My Vercel site is down but Vercel says everything is operational. Why?
Check your own project first: a failed deployment, an exhausted usage limit, a misconfigured custom domain, or an error in your code affects only your site. Compare your custom domain against the deployment's *.vercel.app URL, and check the project's runtime logs. Platform-wide problems usually show on this page's independent checks or Vercel's own feed within minutes.
Does a Vercel outage take down already-deployed sites?
Often not. Vercel's build system and its edge network are separate: many incidents break new builds while existing deployments keep serving from the CDN. Our checks cover both sides (vercel.com and a production site served by Vercel's edge, nextjs.org), so the results table shows which side is affected.
Why does this page show two different answers for Vercel?
The first signal is Infra Agent's own probes of vercel.com, the Vercel API, and a Vercel-hosted production site, run from multiple regions. The second is what Vercel reports on vercel-status.com. Keeping them separate means an unacknowledged problem still shows up, and an incident scoped to products we don't probe still gets surfaced.
How often is this Vercel status page updated?
Infra Agent probes Vercel from every monitoring region roughly every 2 minutes and refreshes the official feed on the same schedule. Timestamps for both are shown above, and the page re-checks automatically while open.