Minor impactResolvedCloud

Vercel incident: Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)

Vercel reported this minor-impact incident on its official status page on Jul 2, 2026, 16:31 UTC. It was resolved after 15 min.

Right now Vercel is operational. Live Vercel status →

🔔 Get alerted when Vercel has issuesFree · email alerts · no credit card
Jul 2, 2026, 16:31 UTC
started
Jul 2, 2026, 16:46 UTC
resolved
15 min
duration
Minor
impact

Affected components

  • CLE1 - Cleveland, East US
  • Dashboard
  • Functions
  • IAD1 - Washington DC, USA

Timeline

updates from Vercel's status page ↗
  1. resolvedJul 2, 2026, 16:46 UTC

    This incident has been resolved.

  2. monitoringJul 2, 2026, 16:39 UTC

    A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.

  3. identifiedJul 2, 2026, 16:33 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingJul 2, 2026, 16:31 UTC

    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.

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.

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

← Previous: Increase in Workflow runs stuck in pending, failed (Jul 1, 2026)Next: Delays Processing Builds (Jul 8, 2026) →
Vercel incident on Jul 2, 2026: Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1) · APIStatus.watch