Vercel

Jun 16, 15:39 UTC
Resolved - The incident has been resolved.

Jun 16, 15:26 UTC
Monitoring - The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.

Jun 16, 15:16 UTC
Identified - The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.

Jun 16, 14:45 UTC
Update - We are continuing to investigate …

Jun 15, 01:24 UTC
Resolved - This incident has been resolved.

Jun 15, 00:25 UTC
Monitoring - All traffic has been restored to the FRA1 Vercel Region.

Jun 14, 23:15 UTC
Update - The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.

Jun 14, 21:26 UTC
Update - The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

Jun 9, 14:46 UTC
Resolved - This incident has been resolved.

Jun 9, 14:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 9, 14:33 UTC
Identified - The issue has been identified and a fix is being implemented.

Jun 9, 14:09 UTC
Investigating - We are currently investigating this issue.

Jun 8, 20:00 UTC
Resolved - This incident has been resolved.

Jun 8, 19:36 UTC
Update - We are continuing to monitor for any further issues.

Jun 8, 19:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 8, 19:04 UTC
Update - We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.

If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy …

Jun 1, 20:02 UTC
Resolved - This incident has been resolved.

Jun 1, 19:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 1, 19:50 UTC
Identified - The issue has been identified and a fix is being implemented.

Jun 1, 19:21 UTC
Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

May 28, 16:59 UTC
Resolved - This incident has been resolved.

May 28, 16:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

May 28, 16:18 UTC
Identified - The issue has been identified and a fix is being implemented.

May 28, 16:00 UTC
Investigating - We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.

May 27, 05:02 UTC
Resolved - This incident has been resolved.

We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.

May 27, 04:50 UTC
Investigating - We are currently investigating this issue.

May 25, 16:22 UTC
Resolved - This incident has been resolved.

May 25, 16:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

May 25, 15:25 UTC
Identified - The issue has been identified and a fix is being implemented.

May 25, 14:58 UTC
Investigating - We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.

May 23, 18:44 UTC
Resolved - This incident has been resolved.

Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt

May 23, 18:21 UTC
Monitoring - GitHub has implemented a fix, and we are monitoring the results.

May 23, 15:46 UTC
Identified - We have identified the issue and are working closely with GitHub to resolve it.

May 23, 14:30 UTC
Update - We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates …

May 22, 17:11 UTC
Resolved - 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 follow-up deployments should no longer encounter this error.

May 21, 21:31 UTC
Resolved - This incident has been resolved.

May 21, 21:20 UTC
Monitoring - The mitigation was successfully rolled out, and builds are stable.

May 21, 19:55 UTC
Update - The root cause has been identified and we are rolling out a mitigation.

May 21, 15:01 UTC
Identified - 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.

May 21, 06:08 UTC
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.

May 20, 20:07 UTC
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.