Historial de interrupciones de Vercel

1. September 4, 2026 at 7:11 PM UTCinvestigating

   Hemos identificado un problema donde algunos clientes pueden experimentar mayor latencia para las solicitudes de API a VCR, Blob y Sandbox. Actualmente estamos investigando esta cuestión. Proporcionaremos actualizaciones adicionales cuando estén disponibles.

2. September 4, 2026 at 7:33 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. September 4, 2026 at 7:33 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. September 4, 2026 at 7:55 PM UTCidentified

   La solución se está poniendo en marcha. Vamos a proporcionar otra actualización una vez que el despliegue esté completo y estamos empezando a ver signos de recuperación.

5. September 4, 2026 at 8:05 PM UTCmonitoring

   La solución ha sido lanzada y estamos viendo signos de recuperación.

6. September 4, 2026 at 8:19 PM UTCmonitoring

   Latencia elevada se ha recuperado para VCR y Sandbox. Continuamos investigando la latencia elevada que afecta a Blob y proporcionaremos otra actualización en breve.

7. September 4, 2026 at 8:27 PM UTCresolved

   Blob se ha recuperado completamente. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 1, 2026 at 7:59 PM UTCinvestigating

   Hemos identificado un problema donde algunas implementaciones que usan las regiones de función IAD1 o Routing Middleware están fallando. Estamos investigando y proporcionaremos más información cuando esté disponible.

2. September 1, 2026 at 8:27 PM UTCinvestigating

   Estamos trabajando activamente para solucionar un problema que provoca que algunos despliegues que usan las regiones de función IAD1 o Routing Middleware fallen. Proporcionaremos actualizaciones adicionales cuando estén disponibles.

3. September 1, 2026 at 8:37 PM UTCidentified

   Hemos identificado el problema y estamos trabajando en una solución. Estamos viendo recuperación a medida que la solución está desplegada. Proporcionaremos actualizaciones adicionales cuando estén disponibles.

4. September 1, 2026 at 8:45 PM UTCmonitoring

   Estamos viendo recuperación en Builds y seguimos monitoreando.

5. September 1, 2026 at 8:49 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

6. September 1, 2026 at 8:58 PM UTCresolved

   Este incidente ha sido resuelto. Los edificios se han recuperado.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 26, 2026 at 3:15 AM UTCinvestigating

   Estamos investigando errores iniciando sesión con Vercel CLI (entrada Vc).

2. August 26, 2026 at 4:28 AM UTCidentified

   El equipo ha identificado la fuente de la cuestión y está probando una solución.

3. August 26, 2026 at 4:28 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 25, 2026 at 7:27 PM UTCinvestigating

   Estamos investigando tiempos elevados de inicialización para algunas construcciones. Proporcionaremos actualizaciones a medida que aprendamos más.

2. August 25, 2026 at 7:37 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. August 25, 2026 at 7:57 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 25, 2026 at 8:05 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 5:46 PM UTCidentified

   Hemos identificado un problema donde las funciones de contenedores recién desplegadas pueden devolver errores 5XX. Los clientes pueden utilizar un despliegue de funciones de contenedores de trabajo previo como mitigación temporal. Estamos trabajando en una solución y proporcionará actualizaciones adicionales a medida que estén disponibles.

2. August 20, 2026 at 6:23 PM UTCmonitoring

   Hemos implementado una solución. Las funciones de contenedores recientemente desplegadas funcionan según lo previsto.

3. August 20, 2026 at 6:34 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 11:14 AM UTCinvestigating

   Estamos investigando un fracaso en la búsqueda de registros de tiempo de ejecución en el Dashboard. Log ingestión y búsqueda de registros de construcción no son afectados.

2. August 20, 2026 at 11:21 AM UTCmonitoring

   Identificamos la fuente del fracaso e implementamos una solución. Los registros de tiempo de ejecución pueden ser consultados de Dashboard de nuevo. Seguimos monitoreando.

3. August 20, 2026 at 11:25 AM UTCresolved

   El sistema funciona normalmente y se recupera completamente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 12:28 AM UTCresolved

   De 10:57pm a 11:43pm UTC, un porcentaje de flujos de trabajo llamadas falló. Los pasos de flujo de trabajo que tenían una llamada de flujo fallido volverían a entrar, y si el paso llegaba a las entradas máximas, el flujo de trabajo falló. Los flujos de trabajo se han recuperado y están funcionando correctamente ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 17, 2026 at 2:30 PM UTCinvestigating

   Estamos investigando una interrupción parcial a la Observabilidad, Web Analytics, Speed Insights, Firewall y Usage en Dashboard. Compartiremos actualizaciones cuando estén disponibles.

2. August 17, 2026 at 3:09 PM UTCinvestigating

   Seguimos investigando esta cuestión. Compartiremos actualizaciones cuando estén disponibles.

3. August 17, 2026 at 4:06 PM UTCinvestigating

   También estamos investigando un problema donde algunos clientes pueden ser incapaces de iniciar sesión en Dashboard con contraseñas de una sola vez basadas en el tiempo (TOTP). Compartiremos actualizaciones cuando estén disponibles.

4. August 17, 2026 at 4:44 PM UTCmonitoring

   Hemos implementado una solución para la interrupción, y los servicios han comenzado a recuperarse. Compartiremos más información a medida que esté disponible.

5. August 17, 2026 at 4:46 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

6. August 17, 2026 at 5:51 PM UTCmonitoring

   Iniciar sesión con TOTP se ha recuperado completamente. Todavía estamos trabajando para ingerir datos de observabilidad desaparecidos durante este período. Compartiremos más información a medida que esté disponible.

7. August 17, 2026 at 8:13 PM UTCmonitoring

   Los servicios se han recuperado. Todavía estamos trabajando para ingerir datos de observabilidad desaparecidos durante este período.

8. August 17, 2026 at 9:25 PM UTCresolved

   Los servicios se han recuperado. Todavía estamos trabajando para ingerir datos de observabilidad desaparecidos durante este período.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 14, 2026 at 1:08 PM UTCresolved

   Este incidente ha sido resuelto. Entre el 12 de agosto de 17:12 UTC y el 13 de agosto de 20:33 UTC, algunas implementaciones de Vercel podrían devolver 404 errores de rutas dinámicas de API. Los despliegues construidos en Vercel durante este período se vieron afectados sólo si cumplieron las tres condiciones: usados Next.js 16.2 o anterior, utilizaron el Router Páginas con internacionalización (i18n configurado en siguiente.config.js), y utilizaron rutas API dinámicas, como páginas/api/[slug].ts o páginas/api/[...path].ts. Los despliegues construidos fuera de Vercel (con despliegue de vercel --preconstruido) no fueron afectados, y los despliegues existentes no reconstruidos durante este período no fueron afectados. Si su proyecto coincide con las condiciones anteriores y se implementó durante la ventana de impacto, vuelva a implementar su proyecto. Los despliegues afectados no se fijan automáticamente; se requiere un nuevo despliegue para restaurar las rutas afectadas.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 6, 2026 at 4:37 PM UTCinvestigating

   Hemos identificado un problema causando retrasos en la entrega de la fuga de troncos. Estamos investigando y proporcionaremos actualizaciones cuando estén disponibles.

2. August 6, 2026 at 4:58 PM UTCinvestigating

   Seguimos investigando esta cuestión y proporcionaremos actualizaciones cuando estén disponibles.

3. August 6, 2026 at 5:06 PM UTCidentified

   Hemos identificado el problema y estamos trabajando en una solución. Proporcionaremos actualizaciones cuando estén disponibles.

4. August 6, 2026 at 5:48 PM UTCidentified

   Estamos empezando a ver la recuperación y seguimos trabajando en el tema. Proporcionaremos actualizaciones cuando estén disponibles.

5. August 6, 2026 at 6:19 PM UTCmonitoring

   La entrega de la fuga de registros se ha recuperado. Estamos monitoreando mientras se procesan los partos retrasados restantes.

6. August 6, 2026 at 6:29 PM UTCresolved

   Este incidente ha sido resuelto. La entrega del drenaje de los registros se ha recuperado y se han procesado los partos retrasados restantes.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 10, 2026 at 9:25 PM UTCmonitoring

   We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC. A rollback is in progress to mitigate this issue. We will provide additional updates as they become available. Failed deployments can be retried and should succeed.

2. July 10, 2026 at 11:28 PM UTCresolved

   This incident has been resolved.

1. July 10, 2026 at 7:15 PM UTCinvestigating

   We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.

2. July 10, 2026 at 7:53 PM UTCidentified

   We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result.

3. July 10, 2026 at 8:50 PM UTCidentified

   We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner.

4. July 10, 2026 at 9:32 PM UTCidentified

   We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation. We will provide additional updates as they become available.

5. July 10, 2026 at 10:36 PM UTCresolved

   We have unpaused all impacted deployments. We will continue to monitor the situation.

1. July 10, 2026 at 5:44 PM UTCresolved

   The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs. New builds after the impact period are unaffected.

1. July 8, 2026 at 6:05 PM UTCinvestigating

   We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.

2. July 8, 2026 at 6:40 PM UTCinvestigating

   We are seeing signs of recovery and the affected build queue has started to drain. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available.

3. July 8, 2026 at 7:13 PM UTCmonitoring

   Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available.

4. July 8, 2026 at 9:35 PM UTCmonitoring

   The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis.

5. July 8, 2026 at 10:23 PM UTCresolved

   This incident has been resolved.

1. July 2, 2026 at 4:31 PM UTCinvestigating

   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.

2. July 2, 2026 at 4:33 PM UTCidentified

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

3. July 2, 2026 at 4:39 PM UTCmonitoring

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

4. July 2, 2026 at 4:46 PM UTCresolved

   This incident has been resolved.

1. July 1, 2026 at 4:57 PM UTCidentified

   We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.

2. July 1, 2026 at 5:49 PM UTCidentified

   We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted.

3. July 1, 2026 at 6:30 PM UTCresolved

   The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected. Affected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.

1. June 26, 2026 at 1:08 PM UTCinvestigating

   We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.

2. June 26, 2026 at 1:23 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 26, 2026 at 2:08 PM UTCinvestigating

   We are continuing to investigate this issue and will provide an update as soon as we have more information.

4. June 26, 2026 at 2:11 PM UTCidentified

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

5. June 26, 2026 at 2:29 PM UTCidentified

   Login is recovering for most users. We're monitoring to ensure stability.

6. June 26, 2026 at 3:03 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

7. June 26, 2026 at 3:14 PM UTCresolved

   This incident has been resolved.

1. June 25, 2026 at 7:45 AM UTCinvestigating

   We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.

2. June 25, 2026 at 8:27 AM UTCidentified

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

3. June 25, 2026 at 9:25 AM UTCidentified

   The issue has been identified. We are continuing to work on a fix for this issue.

4. June 25, 2026 at 10:42 AM UTCidentified

   We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs.

5. June 25, 2026 at 12:15 PM UTCidentified

   We are currently rolling a fix for the issue. We are monitoring the results.

6. June 25, 2026 at 1:30 PM UTCmonitoring

   The fix has been fully rolled out and we are monitoring the results.

7. June 25, 2026 at 1:43 PM UTCresolved

   This incident has been resolved.

1. June 23, 2026 at 11:24 PM UTCinvestigating

   We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.

2. June 23, 2026 at 11:26 PM UTCidentified

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

3. June 23, 2026 at 11:28 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. June 23, 2026 at 11:34 PM UTCresolved

   This incident has been resolved.

1. June 19, 2026 at 5:54 PM UTCresolved

   Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.