Elevated errors across multiple services

This incident has been resolved.

We are seeing recovery across all of our products, and Logs have resumed. Historical data in Logs and Speed Insights has been backfilled. Our on-call teams continue to monitor the situation regularly.

Traffic has been rerouted from neighboring regions back to IAD1. Historical runtime Logs data is now being backfilled and will resume normal processing shortly.

We are investigating intermittent errors on the Vercel dashboard.

We have identified the root cause of the Logs and Log Drains issue and we are rolling out a fix.

We are investigating errors affecting runtime Logs and Log Drains.

Edge Config issues are now resolved.

Domain Registrations issues are now resolved.

A fix has been implemented for Edge Config, and we are monitoring the result.

A fix has been implemented for Domain Registrations, and we are monitoring the result.

We have identified Domain Registration failures and are working to restore service.

We have identified degraded performance with Edge Config storage and are working to restore service.

New deployments using Routing Middleware or Vercel Functions in the IAD1 region may fail to deploy.
Traffic is still successfully being rerouted away from IAD1, which may result in increased latency.
We are seeing full recovery of Edge Function and Middleware invocation errors in our IAD1 region.
We are investigating an intermittent elevation of Cron Jobs not being executed.
Historical data for Speed Insights and Web Analytics is currently being backfilled.

New deployments using Routing Middleware or Vercel Functions in the IAD1 region may fail to deploy.
Traffic is still successfully being rerouted away from IAD1, which may result in increased latency.
We are seeing full recovery of Edge Function and Middleware invocation errors in our IAD1 region.
We are investigating an intermittent elevation of Cron Jobs not being executed.
Historical data for Speed Insights and Web Analytics is currently being backfilled.

We are seeing recovery across Edge Functions and Middleware invocation errors in our IAD1 region.
Historical data for Speed Insights and Web Analytics is currently being backfilled.
Deployment creation for customers using Secure Compute or Static IPs are still impacted.
Traffic is still successfully being rerouted away from iad1, which may result in increased latency.

We are investigating an intermittent elevation of Edge Function and Middleware invocation errors in our IAD1 region. Impacted customers may encounter errors with the code INTERNAL_FUNCTION_INVOCATION_FAILED.
Historical data for Speed Insights and Web Analytics is currently being backfilled.
Deployment creation for customers using Secure Compute or Static IPs are still impacted.
Traffic is still successfully being rerouted away from iad1, which may result in increased latency.

Historical data for Speed Insights and Web Analytics is currently being backfilled.
Deployment creation for customers not using Secure Compute or Static IPs has been fully restored.
Traffic is still successfully being rerouted away from IAD1, which may result in increased latency.

We are currently investigating reports of delayed data for Speed Insights and Web Analytics.

We are currently investigating reports of delayed data for Speed Insights and Web Analytics.

We are seeing recovery across deployment creation using Routing Middleware and Functions in IAD1.

CDN traffic in IAD1 continues to be rerouted as we work toward full recovery. During this period, users may experience increased latency.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

New deployments using Routing Middleware, or Vercel Functions with iad1 region may still be failing. We are continuing to investigate this issue.

We are seeing recovery across services and CDN traffic is healthy.

Multiple services are affected. We have re-routed CDN traffic from iad1 to a healthy region and are working on managing impact by component. Builds have also been rerouted.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.