v0 (Vercel) · 137d ago
Missing Build CPU Minutes Usage Data
ResolvedYes — v0 had a problem on May 20, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window.”
Timeline
Started: 5/20/2026, 8:07:17 PM
Last update: 5/29/2026, 5:05:14 PM
Resolved: 5/21/2026, 6:08:03 AM
Affected: 7ckq6xr6nsbv
Updates
resolved
This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window.
5/21/2026, 6:08:03 AM
monitoring
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.
5/20/2026, 8:07:17 PM
More v0 (Vercel) incidents
- Increased build and deployment failures — resolved, 1d ago
- Delays in Drains, Observability, and Workflow in Washington (iad1) — resolved, 4d ago
- Vercel Auth login failures for pages with Deployment Protection enabled — resolved, 7d ago
- Elevated Sandbox error rates in Paris (cdg1) — resolved, 7d ago
- Build failures and 500 errors for functions using Edge runtime — resolved, 15d ago
- Deployment stuck in initializing state — resolved, 25d ago