v0
AI. Source: v0 status page.
- Incidents, last 90 days
- 6
- Median to mitigation
- 17m
- Median to resolution
- 28m
- p95 to resolution
- 3h 42m
- Naming an upstream provider
- 33%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 3 |
| A provider or third-party service this vendor depends on failed | 3 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
Elevated error rate on the v0 API
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are investigating elevated error rates affecting the v0 API and will provide updates as more information becomes available.
-
resolved
The issue causing elevated error rates on the v0 API has been resolved, and services are operating normally.
Excerpts are shortened. Read the full incident on v0's status page.
Some users are unable to access v0
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some users may be unable to access v0. We’re working to restore access and will share an update once recovery is confirmed.
-
investigating
We're investigating elevated errors and slow load times affecting v0, including the web app, iOS app, and Platform API.
-
resolved
We are confident that the issue has been mitigated.
Excerpts are shortened. Read the full incident on v0's status page.
Some users unable to access v0
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
Some users may be unable to access v0. We’re working to restore access and will share an update once recovery is confirmed.
-
monitoring
The team has applied a fix, and we’re seeing early signs of recovery. We’re continuing to monitor.
-
monitoring
We are confident that the issue has been mitigated.
-
resolved
v0 is operating normally.
Excerpts are shortened. Read the full incident on v0's status page.
Upstream Provider issue causing partial outage in v0
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are seeing some errors due to upstream provider issues.
-
monitoring
The issue has been mitigated; we are continuing to monitor to ensure stability.
-
resolved
We are confident that the issue has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Github service degraded
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
Started during GitHub: Incident with GitHub.com.
-
identified
Features that rely on GitHub (authentication, GitHub repository import, and chatting with GitHub-backed chats) are degraded.
-
monitoring
The upstream degradation has been resolved. We are monitoring to ensure stability.
-
resolved
We conclude that the degraded services are recovered.
Excerpts are shortened. Read the full incident on v0's status page.
GitHub integration degraded
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
identified
GitHub is experiencing issues affecting Pull Requests.
-
monitoring
Upstream provider recovered; we are monitoring to ensure stability.
-
resolved
Upstream provider recovered.
Excerpts are shortened. Read the full incident on v0's status page.
Some chat previews are not loading
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are investigating an issue that causes chat previews to fail to load.
-
investigating
We are investigating an issue that causes chat previews to fail to load.
-
identified
We've identified the issue causing the failing chat preview and are working on a fix.
-
monitoring
We rolled out a fix and are monitoring.
-
resolved
A fix has been implemented, and this incident has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Github service degraded
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
Features that rely on GitHub (authentication, GitHub repository import, and chatting with GitHub-backed chats) are degraded.
-
resolved
Upstream provider recovered.
Excerpts are shortened. Read the full incident on v0's status page.
GitHub integration degraded
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
GitHub is experiencing issues affecting automatic deployments and account connection.
-
identified
Features that rely on GitHub (authentication, GitHub repository import, and chatting with GitHub-backed chats) are degraded.
-
monitoring
The degradation has been resolved. We are monitoring to ensure stability.
-
resolved
The v0 GitHub integration and related features (account linking, importing repositories, and chatting with GitHub-backed chats) were degraded due to an upstream GitHub outage.
Excerpts are shortened. Read the full incident on v0's status page.
v0 is experiencing elevated errors
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are seeing errors in our apps
-
identified
We’ve identified the issue causing elevated errors across several v0 workflows and are actively working on a fix. We’ll continue monitoring closely and share another update as soon as we have more information.
-
resolved
A fix has been implemented, and this incident has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Some code versions can not be restored
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some code versions in the chat history are not able to be restored.
-
identified
We have identified the issue and are working on fix
-
monitoring
A fix has been deployed. New edits can be restored.
-
resolved
The issue has been resolved. Newly created blocks can be restored.
Excerpts are shortened. Read the full incident on v0's status page.
Some users are experiencing degraded previews. We are investigating.
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some users are experiencing degraded previews when viewing chats.
-
monitoring
We have implemented a fix and previews have recovered. We will continue to monitor.
-
resolved
We have implemented a fix and previews have recovered.
Excerpts are shortened. Read the full incident on v0's status page.
Uploads to v0 are degraded
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
File uploads to v0 are currently failing for certain users. We are investigating the issue.
-
resolved
We've identified the source of the issue and have pushed a fix. Upload functionality has been restored.
Excerpts are shortened. Read the full incident on v0's status page.
Some users are experiencing issues deploying
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some users are experiencing issues deploying. We have identified the issue.
-
identified
We have identified the issue and are working on a fix
-
monitoring
We have published a fix and monitoring
-
resolved
The issue has been resolved
Excerpts are shortened. Read the full incident on v0's status page.
v0.app is experiencing degraded functionality
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some users may be unable to access v0.app. A subset of users may be able to load v0.app, but may not be able to switch teams. We are investigating the issue.
-
investigating
Some users may be unable to access [v0.app](http://v0.app "v0.app"). A subset of users may be able to load [v0.app](http://v0.app "v0.app"), but may not be able to switch teams or send messages. We are investigating the issue.
-
investigating
Some users may be unable to access [v0.app](http://v0.app "v0.app"). A subset of users may be able to load [v0.app](http://v0.app "v0.app"), but may not be able to switch teams or send messages. We are investigating the issue.
-
monitoring
We've identified the source of the issue and pushed a fix. We're monitoring the situation.
-
resolved
This issue has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Previews fail to load
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some v0 apps show an error screen instead of the expected preview. We are actively investigating.
-
monitoring
Fix for the issue is rolled out. Continuing to monitor.
-
resolved
The issue is resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Code editor changes are failing to save
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Manual edits made via the Code Editor are not being saved
-
identified
The issue has been identified
-
monitoring
A fix has deployed and we are monitoring.
-
resolved
We've confirmed the fix is live and manual code edits are functioning.
Excerpts are shortened. Read the full incident on v0's status page.
Some users are experiencing degraded preview performance
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some users are experiencing issues loading the preview environment in v0, which my cause agent performance issues. We are investigating the issue.
-
resolved
We've identified the root cause and pushed a fix. We're monitoring the rollout.
Excerpts are shortened. Read the full incident on v0's status page.
v0.app is not loading for some users
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Users may not be able to access v0.app. We're investigating the issue.
-
resolved
The incident has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
v0.app chats on Web and API are unreachable
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
resolved
v0.app chats and API are unreachable
-
resolved
v0.app is fully operational
Excerpts are shortened. Read the full incident on v0's status page.
Issues starting new chats from templates
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are experiencing issues creating new chats from templates.
-
monitoring
A fix has been applied. Chats can now be created from new templates.
-
resolved
The issue has been resolved
Excerpts are shortened. Read the full incident on v0's status page.
GitHub operations are degraded on v0
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
GitHub operations are degraded on v0 due to an upstream issue. We are investigating the issue.
-
investigating
GitHub operations are degraded on v0 due to an upstream issue. We are investigating mitigations.
-
resolved
This issue has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Elevated error rates across v0
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Elevated error rates across v0 due to upstream errors. We are investigating the issue.
-
investigating
Elevated error rates across v0.
-
investigating
We are investigating the root cause of this issue.
-
monitoring
We’re monitoring error rates post recovery.
-
resolved
This issue has been resolved.
Excerpts are shortened. Read the full incident on v0's status page.
GitHub-connected chats are seeing degraded performance
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
Importing GitHub repositories and working on GitHub-connected chats may face degraded performance. We are investigating the issue.
-
investigating
Importing GitHub repositories and working on GitHub-connected chats may face degraded performance.
-
investigating
Importing GitHub repositories and working on GitHub-connected chats may face degraded performance.
-
monitoring
We've addressed the cause of this issue and are monitoring the impact.
-
resolved
This issue is now resolved.
Excerpts are shortened. Read the full incident on v0's status page.
Some messages with images are failing
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some messages with images are failing
-
resolved
We identified the cause of the issue and have pushed a fix.
Excerpts are shortened. Read the full incident on v0's status page.
Environment variables not loading in middleware
Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
In some cases, environment variables are not being correctly read when used in middleware. We are looking into the root cause.
-
identified
We identified the issue in our runtime environment; we are working on a fix.
-
resolved
The issue was fixed, and environment variables are being loaded correctly in middleware/proxy.
Excerpts are shortened. Read the full incident on v0's status page.