Vercel incident: Missing Build CPU Minutes Usage Data

Affected components

• Builds

1. resolvedJul 16, 2026, 09:27 UTC

   The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.

2. monitoringJul 16, 2026, 06:07 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Vercel's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Tailscale: Admin console and pkgs.tailscale.com are unavailableCritical · Jul 16, 2026, 08:13 UTC
• Supabase: Projects in stuck state in EU-CENTRAL-1 (Frankfurt)Major · Jul 16, 2026, 07:00 UTC
• Plaid: Elevated dashboard.plaid.com error ratesMajor · Jul 16, 2026, 08:48 UTC
• RevenueCat: Some users unable to login via single-sign-on (SSO)Major · Jul 16, 2026, 09:13 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Confluent Cloud: Kafka cluster performance degradation for clusters in AWS region eu-central-1Minor · Jul 15, 2026, 23:33 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• Clerk: Increased latency on our APIsMinor · Jul 16, 2026, 07:56 UTC

How often does Vercel have incidents?

Vercel reported 24 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 59 min. See Vercel's uptime and incident history