Space for ads
Checked every 5 minutes · How we measure this
As of 19:00 EST on 12 Nov 2026, vercel.com responded to our check in 335 ms, with 99.65% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to vercel.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Vercel on its own status page. Verify on their status page.
0 problem reports
Build delays and degraded Vercel Dashboard performance
We are seeing recovery after taking corrective action to address latency. We are continuing to process delayed builds. Vercel CI has also been affected. We will provide additional updates as they become available.
Confirmed on the vendor status page
Vercel degraded performance
DownBits detected degraded performance on Vercel between 23 Oct 2026, 22:10 – 23:10 IST, lasting ongoing. Detected across 12 consecutive automated checks of vercel.com.
Detected by DownBits probe
Delays in Logs and Observability data
We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.
Confirmed on the vendor status page
Vercel degraded performance
DownBits detected degraded performance on Vercel between 12 Oct 2026, 19:15 – 01:50 IST, lasting ongoing. Detected across 79 consecutive automated checks of vercel.com.
Detected by DownBits probe
Increased build and deployment failures
The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
Confirmed on the vendor status page
Vercel degraded performance
DownBits detected degraded performance on Vercel between 10 Oct 2026, 05:55 – 07:15 IST, lasting ongoing. Detected across 16 consecutive automated checks of vercel.com.
Detected by DownBits probe
Delays in Drains, Observability, and Workflow in Washington (iad1)
Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available.
Confirmed on the vendor status page
Vercel degraded performance
DownBits detected degraded performance on Vercel between 6 Oct 2026, 21:50 – 22:05 IST, lasting ongoing. Detected across 3 consecutive automated checks of vercel.com.
Detected by DownBits probe
Vercel Auth login failures for pages with Deployment Protection enabled
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Vercel degraded performance
DownBits detected degraded performance on Vercel between 6 Oct 2026, 14:50 – 15:15 IST, lasting ongoing. Detected across 5 consecutive automated checks of vercel.com.
Detected by DownBits probe
Elevated Sandbox error rates in Paris (cdg1)
We are seeing signs of recovery in Sandbox in Paris, France (cdg1). We will share updates as they become available.
Confirmed on the vendor status page
Build failures and 500 errors for functions using Edge runtime
A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.
Confirmed on the vendor status page
Deployment stuck in initializing state
We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.
Confirmed on the vendor status page
Elevated Errors Triggering Deployments
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Elevated error rate on Connect and Passport
The issue has been identified and a fix is being implemented.
Confirmed on the vendor status page
Vercel is responding normally. Our last automated check of vercel.com completed 9 minutes ago and succeeded in 335 ms. Over the past 24 hours the service answered 99.65% of our checks.
Measured from our automated checks, Vercel has been available 99.65% over 24 hours, 99.80% over 7 days, 99.80% over 30 days. We recorded 3 incidents in the last 30 days.
Vercel has averaged 450 ms across our successful checks in the past 24 hours, which is normal for a service of this kind. Response time is measured from our probe to vercel.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for Vercel began on 23 October 2026 at 22:10 IST and lasted 1 hr. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching vercel.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://vercel.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Vercel. On Windows run ping vercel.com and nslookup vercel.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load vercel.com in a private or incognito window. If it works there, clear cookies and site data for vercel.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
