Is v0 down right now?
HTTP endpoint monitoring - checked every 5 minutes · How we classify outages
v0 is currently operational - 209ms HTTP response. Last checked . 90-day uptime: 99.8%.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live v0 status on your site, README, or docs.
90-day uptime
99.8%
20 incidents (90d)
Response now
209ms
HTTP p50 (7d)
242ms
median ping response
HTTP p95 (7d)
930ms
tail ping response
Response time (7 days)
p50 242ms·p95 930msⓘ HTTP response times from Tickerr's monitoring server to v0's status or homepage endpoint - not API inference latency or time-to-first-token (TTFT). For API benchmark data, see third-party sources like Artificial Analysis.
90-day uptime comparison
Independent monitoring catches issues faster - official pages sometimes lag by hours before acknowledging problems.
Service components
via www.vercel-status.com ↗Incident history
We are currently investigating this issue.
We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
We are currently investigating this issue.
Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and…
We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.
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're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.
We are investigating an issue where support cannot be submitted through the dashboard.
Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.
Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is…
Between 18:36 and 19:04 UTC, issuing SSL certificates was delayed for new domains. These certificates have now been issued. Certificate renewals were not affected.
We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they …
Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.
We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes available.
We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue and are implementing a fix.
We've identified an issue where various services in the Vercel dashboard, API, and CLI are failing to load data. These services include Observability, Speed Insights, Alerts, Usage, Web Analytics, Fir…
Between 21:45–21:52 UTC, some users may have experienced request failures in ICN1. The issue has been identified, a fix has been applied, and the issue has been resolved.
Between May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content…
We are currently investigating this issue.
We are currently investigating this issue.
Related pages
About v0 status
v0 is Vercel's AI-powered UI generation tool that creates React components from prompts. When v0 is down, component generation and the chat interface are unavailable. v0 runs on Vercel infrastructure and uses Anthropic and OpenAI models.