Is it down for me?
Testing vercel.com from your device…
Most checked
Not listed? Type its address, like example.com, to check it now.
Our last check from one location (UtiBox server · Newark, US) found it answering normally in 287 ms.
Testing vercel.com from your device…
Vercel is up. Total time to the final page on our latest check.
Thanks, you said it works
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
No answers in the last 24 hours
Only our server so far. The regional checks run when the page opens.
No posts yet. Be the first to say how Vercel is working for you.
Our latest check, step by step. Tap a step to open its full record.
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether vercel.com is blocked or broken there.
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
Rules out extensions and stored cookies.
Move from Wi-Fi to mobile data, or the other way round.
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
They can block or reroute requests.
A wrong clock breaks secure connections.
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for Vercel. | ||||
What people say about Vercel, in their own words, kept apart from our own checks.
Live counts · real numbers, refreshed with the page
Posts are public after a quick review. Don’t share personal details or links.
No posts yet.
Be the first to say how Vercel is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
One answer per person, counted for 24 hours.
Having one of these? Tap it to start a report.
What Vercel status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Read from the official feed · the provider last updated it .
What Vercel status reports about Vercel. A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Vercel. It may not reflect regional or account-specific problems.
None reported for Vercel in the last report we read.
No maintenance is planned for Vercel in the last report we read.
Our first successful read in this window was on 9 Nov 2026.
51 resolved updates since May 2026 · 17 major · last one 10 Nov 2026
“On November 10, 2026, between 19:16 and 19:34 UTC, some Sandbox and Blob API requests in iad1 region experienced elevated latency and errors. A fix was applied, restoring service at 19:34 UTC and preventing this issue from recurring. This incident lasted 18 minutes and is being reported retroactively. We apologize for the disruption.”
“We've identified an issue where some customers may experience delayed builds, slow page loads, and failed actions in the Vercel Dashboard. We are investigating the cause. We will provide additional updates as they become available.”
“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.”
“We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.”
“We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.”
“We are investigating an issue causing Vercel Auth login failures for pages with Deployment Protection enabled. We will provide an update as more information becomes available.”
“We've identified an issue where some customers may experience elevated error rates with Sandbox in Paris, France (cdg1). We are currently investigating this issue. We will share updates as they become available.”
“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.”
“We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.”
“We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.”
“Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.”
“Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.”
“Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.”
“Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.”
“We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.”
“We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.”
“We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.”
“We are investigating errors logging in with Vercel CLI (vc login).”
“We're investigating elevated initialization times for some builds. We will provide updates as we learn more.”
“We've identified an issue where newly deployed container functions may return 5XX errors. Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.”
“We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.”
“From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.”
“We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.”
“This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts. Deployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this…”
“We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.”
“The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.”
“Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.”
“We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.”
“We are investigating an issue causing the dashboard to be inaccessible for some users.”
“There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.”
“We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.”
“We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.”
“We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.”
“We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.”
“We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available. Failed deployments can be retried and should succeed.”
“We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.”
“The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.”
“We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.”
“We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.”
“We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.”
“We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.”
“We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.”
“We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.”
“Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the…”
“We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.”
“We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.”
“We are currently investigating this issue.”
“The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.”
“We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.”
“We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.”
“We are currently investigating this issue.”
No updates of this kind.
From Vercel status’s public status history. UtiBox keeps the official updates it reads for 180 days.
At our last check from UtiBox server · Newark, US, Vercel was up and answering normally. The page refreshes the check automatically.
The official status page (www.vercel-status.com) reports “Operational” for Vercel. We read it every few minutes. It’s separate from our own check of the vercel.com website above, so the two can differ.
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
Our server requests vercel.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.
UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.
Keep forms secure (ubsid) and remember that you’ve seen this notice (ub_consent). Things you ask us to remember, like light or dark mode and closed banners, are part of this.
UtiBox is free because of ads. Google AdSense and its partners use cookies to show, limit and measure ads. To change how Google personalises the ads you see, use Google’s My Ad Center. To opt out of personalised ads from many companies, visit aboutads.info or youronlinechoices.eu.
Google Analytics counts visits and shows us which pages and tools people use, so we can improve them. It sets _ga cookies. In the EEA, the UK and Switzerland it stores nothing unless you agree. To opt out on any site, use Google’s opt-out browser add-on. Ahrefs Web Analytics counts visits without cookies: it stores nothing on your device and never keeps your IP address; block analytics.ahrefs.com to opt out. Microsoft Clarity records clicks and scrolling for heatmaps and replays, with the tool area and what you type blanked out; block clarity.ms to opt out.