Historial de interrupciones de Anaplan

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

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. September 7, 2026 at 1:33 PM UTCinvestigating

   Hemos identificado la causa probable del problema, y ahora estamos enfocados en restaurar el servicio lo antes posible. Actualmente, todavía no tenemos tiempo para resolver. Proporcionaremos nuevas actualizaciones en 30 minutos o en resolución.

3. September 7, 2026 at 1:35 PM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

4. September 7, 2026 at 1:46 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

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

1. September 3, 2026 at 2:56 PM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. September 3, 2026 at 3:12 PM UTCidentified

   Hemos identificado la causa probable del problema, y ahora estamos enfocados en restaurar el servicio lo antes posible. Actualmente, todavía no tenemos tiempo para resolver. Proporcionaremos nuevas actualizaciones en 30 minutos o en resolución.

3. September 3, 2026 at 3:16 PM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

4. September 3, 2026 at 6:04 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

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

1. September 1, 2026 at 9:49 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para ejecutar integraciones de Cloudworks. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. September 1, 2026 at 10:25 AM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

3. September 1, 2026 at 11:06 AM UTCinvestigating

   Gracias por su paciencia continua mientras investigamos este asunto. Hemos confirmado un problema que afecta a las integraciones de CloudWorks en varias regiones. Esta sigue siendo una prioridad máxima, y todavía no tenemos un tiempo estimado para resolver. Continuaremos compartiendo actualizaciones cada 30 minutos mientras trabajamos para resolver esto lo más rápido posible.

4. September 1, 2026 at 11:45 AM UTCidentified

   Gracias por su paciencia continua mientras investigamos este asunto. Hemos observado que las integraciones de CloudWorks comienzan y completan con éxito en todas las regiones; sin embargo, seguimos monitoreando la situación de cerca. Compartiremos nuevas actualizaciones cada 30 minutos mientras trabajamos para resolver esto lo más rápido posible.

5. September 1, 2026 at 12:19 PM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

6. September 1, 2026 at 12:42 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

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

1. September 1, 2026 at 9:10 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para ejecutar integraciones de Cloudworks. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. September 1, 2026 at 9:28 AM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

3. September 1, 2026 at 9:47 AM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

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

1. August 27, 2026 at 10:22 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan en Canadá. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. August 27, 2026 at 10:52 AM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

3. August 27, 2026 at 10:57 AM UTCidentified

   Hemos identificado la causa probable del problema, y ahora estamos enfocados en restaurar el servicio lo antes posible. Actualmente, proporcionaremos más actualizaciones en 30 minutos o en resolución.

4. August 27, 2026 at 10:58 AM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

5. August 27, 2026 at 11:08 AM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

6. September 3, 2026 at 3:52 PM UTCpostmortem

   El 27 de agosto de 2026, a las 10:22 UTC, algunos clientes de nuestro ca1: Cloud - Canadá región experimentaron problemas intermitentes accediendo a la plataforma. Durante este tiempo, los usuarios pueden haber encontrado errores al intentar iniciar sesión. El impacto variaba dependiendo de qué componente manejaba cada solicitud; algunas solicitudes tuvieron éxito mientras que otras no tuvieron éxito. *Causa de raíz* Following a standard system update, a single traffic-routing component in the Canada region entered an inconsistent state after a settings reload and failed to reconstruction its routing instructions properly. El componente empezó a rechazar intermitentemente las solicitudes de clientes o a dirigirlas erróneamente. Los controles de salud del componente verificaron su disponibilidad, pero no capturaron la corrección de su configuración de enrutamiento. Como resultado de ello, seguía siendo activa y continuaba sirviendo de tráfico. Esto dio lugar a que algunas solicitudes tuvieran éxito, mientras que otras no tuvieron éxito, dependiendo de qué componente manejaba la conexión. *Recuperación* Nuestro equipo de ingeniería identificó el problema y tomó medidas inmediatas. El equipo aisló la cuestión a un solo componente de tráfico y la reinicia. Esto redistribuyó todo el tráfico entrante a través de los componentes sanos restantes. Para las 11:08 UTC, la cuestión se resolvió completamente. ** Acciones correctivas y preventivas** Estamos implementando las siguientes acciones para prevenir la recurrencia: * Estamos endureciendo los controles de salud de nuestros componentes de tráfico para aislar inmediatamente y reiniciar automáticamente cualquier componente que no valide correctamente después de una actualización de configuración. Esto impide que un componente degradado siga sirviendo al tráfico y causando fallos de acceso intermitente para los clientes. * Estamos refinando nuestro monitoreo para proporcionar más visibilidad granular en componentes de servicio individuales. Esto permite una detección más rápida de problemas localizados antes de afectar a más clientes. Nos disculpamos por el impacto que este problema ha tenido en sus operaciones. Estamos comprometidos con las mejoras descritas anteriormente para evitar interrupciones similares. Si tiene preguntas o preocupaciones, póngase en contacto con nuestro equipo [Apoyo] (https://support.anaplan.com/).

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

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

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para ejecutar integraciones de Cloudworks. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. August 15, 2026 at 4:02 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan, que también está impactando las integraciones de CloudWorks Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

3. August 15, 2026 at 4:31 AM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

4. August 15, 2026 at 5:03 AM UTCidentified

   Hemos identificado la causa probable del problema, y ahora estamos enfocados en restaurar el servicio lo antes posible. Actualmente, todavía no tenemos tiempo para resolver. Proporcionaremos nuevas actualizaciones en 30 minutos o en resolución.

5. August 15, 2026 at 5:33 AM UTCidentified

   Hemos intensificado esta cuestión con el proveedor de terceros para mitigar la cuestión. Actualmente, todavía no tenemos tiempo para resolver. Proporcionaremos nuevas actualizaciones en 30 minutos o en resolución.

6. August 15, 2026 at 6:13 AM UTCidentified

   Continuamos colaborando estrechamente con nuestro proveedor para resolver la cuestión del acceso que afecta a la región de la UE2, que sigue siendo nuestra máxima prioridad. A través de nuestra investigación, hemos identificado cuestiones de conectividad a la región UE-CENTRAL-1 como la causa subyacente. A partir de las 7:33 PM PDT el 14 de agosto, nuestro proveedor comenzó a experimentar una mayor pérdida de paquetes que impactó la conectividad para los clientes en la región UE-CENTRAL-1. La ubicación afectada se ha identificado como Equinix, Frankfurt. Si bien se han hecho progresos, las conexiones con este lugar siguen siendo deficientes. Seguimos priorizando pasos de resolución con nuestro proveedor. Sin embargo, se espera que la recuperación completa esté a varias horas de distancia. Proporcionaremos una actualización cada 60 minutos a medida que trabajemos para restaurar el servicio lo más rápido posible, o antes si se dispone de información adicional.

7. August 15, 2026 at 7:12 AM UTCidentified

   Seguimos trabajando con nuestro proveedor para resolver la cuestión del acceso que afecta a la región eu2 como nuestra máxima prioridad. También estamos explorando múltiples caminos para restaurar el servicio lo más rápido posible. La colaboración con nuestro proveedor está en curso; sin embargo, se espera que la recuperación completa esté a varias horas de distancia. Proporcionaremos una actualización cada 60 minutos a medida que trabajemos para restaurar el servicio lo más rápido posible, o antes si se dispone de información adicional

8. August 15, 2026 at 8:11 AM UTCidentified

   Hemos completado la red de tráfico fuera de la zona afectada y ahora estamos en fase de monitoreo. Se proporcionará otra actualización en 30 minutos, o antes si se dispone de información adicional.

9. August 15, 2026 at 8:37 AM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

10. August 25, 2026 at 4:00 PM UTCpostmortem

    El 15 de agosto de 2026, de 03:16 UTC a 08:23 UTC, clientes en nuestro eu2: Data Center - Alemania región experimentó una interrupción del servicio que impidió el acceso a la plataforma Anaplan. Durante este tiempo, un fallo de infraestructura local afectó la capacidad de la región de conectarse a servicios externos, lo que dio lugar a una pérdida de disponibilidad de plataformas. *Causa de raíz* La perturbación fue causada por un fracaso ambiental en la instalación de terceros de nuestro proveedor en Frankfurt, Alemania. Una fuga en el sistema de refrigeración de la instalación llevó a sobrecalentamiento localizado, lo que provocó cierres automáticos de seguridad de equipos de red críticos. El agua de escape también dañó sistemas de distribución de energía localizada dentro de la instalación, desactivando dispositivos de red. Este fallo combinado de potencia y enfriamiento impidió que el sistema resolviera direcciones externas y completara solicitudes de salida en esta región. *Recuperación* Debido a que las condiciones ambientales de la instalación hicieron que la zona fuera insegura para entrar, nuestro proveedor se retrasó en evaluar y reparar el equipo afectado. Como resultado, nuestro equipo de ingeniería desplegó un cambio de emergencia para redirigir el tráfico a través de una vía de red regional alternativa, superando las instalaciones y regiones con deficiencias. Esta conectividad externa completa restaurada con éxito y resolución de nombres, y el acceso a la plataforma fue totalmente restaurado por 08:23 UTC. El operador de la instalación y nuestro proveedor continuaron los trabajos de recuperación en los días siguientes, con la restauración completa confirmada antes del 18 de agosto. Mantuvimos nuestro viaje de emergencia durante todo ese período para mantener el servicio estable mientras el vendedor completó las reparaciones. ** Acciones correctivas y preventivas** Estamos aplicando las siguientes medidas para fortalecer la resiliencia y reducir el riesgo de una perturbación similar: * Estamos añadiendo una capa que redirige automáticamente el tráfico a ubicaciones geográficas alternadas durante una salida localizada, sin necesidad de intervención manual. * Estamos permitiendo que los registros cachés continúen sirviendo al tráfico cuando el camino a los soluciones externos no está disponible, por lo que una pérdida de conectividad a los servicios externos ya no impide el acceso a la plataforma cuando se produce un evento regional. * Trabajamos con nuestros proveedores de instalaciones y redes de terceros para revisar sus estándares para sistemas críticos de potencia y refrigeración y asegurar que existan salvaguardias preventivas más fuertes. Nos disculpamos por el impacto que este problema ha tenido en sus operaciones. Estamos comprometidos con las mejoras descritas anteriormente para evitar perturbaciones similares. Si tiene preguntas o preocupaciones, póngase en contacto con nuestro equipo de soporte.

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

1. July 29, 2026 at 11:06 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. July 29, 2026 at 11:36 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan. Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

3. July 29, 2026 at 11:41 AM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

4. July 29, 2026 at 12:51 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

5. August 7, 2026 at 6:56 PM UTCpostmortem

   On July 29, 2026, between 10:57 UTC and 11:53 UTC, customers in our us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan regions experienced degraded performance. This resulted in delayed model and workspace access, slow page load times, and slower logins across the platform, as well as delayed execution of CloudWorks™ integrations. All other regions were unaffected during this time.  **Root Cause**  The incident was triggered by an automated security software update deployed across our platform servers. This simultaneous update caused an unexpected, short-lived spike in storage activity that temporarily exceeded the storage systems' processing capacity. The resulting latency disrupted communication between internal metadata services and core system servers, causing the service connection pools to become unresponsive and preventing them from automatically recovering.  **Recovery**  Our engineering team identified the issue and took immediate action. We performed rolling restarts of the affected metadata services to clear the unresponsive connection pools and stabilize the systems. By 11:30 UTC, affected systems had recovered. Following this, the CloudWorks™ scheduler was restarted to process and clear the backlog of integration tasks. The issue was fully resolved by 11:53 UTC.  **Corrective & Preventative Actions**  We are implementing the following actions to prevent recurrence:  * We are implementing enhanced storage performance tiers and traffic-prioritization controls to isolate key platform workloads from other background system activities.  * We are updating our internal service connection frameworks to automatically detect and gracefully recover from unexpected system connection interruptions.  * We are refining our security software deployment processes to stagger rollouts and limit simultaneous resource utilization.  * We are enhancing our synthetic monitoring dashboards to improve visibility of regional service performance deviations.  * We are conducting rigorous connection-recovery and system testing in our lower environments to validate application resilience under loaded states.  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.

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

1. July 24, 2026 at 8:35 PM UTCinvestigating

   Actualmente estamos investigando un problema que resulta en que algunos clientes no pueden cargar modelos. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. July 24, 2026 at 11:01 PM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

3. July 24, 2026 at 11:33 PM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Nuestros equipos de apoyo siguen investigando esta cuestión, pero todavía no tenemos tiempo para resolverla. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

4. July 25, 2026 at 12:07 AM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Esta cuestión se ha intensificado en nuestros equipos de ingeniería y liderazgo, que están investigando activamente la situación y evaluando todos los próximos pasos necesarios para restaurar las operaciones completas. Si bien no disponemos de detalles técnicos específicos para compartir en este momento, por favor recuperemos que resolver este incidente es nuestra máxima prioridad. Sinceramente nos disculpamos por la perturbación y apreciamos su paciencia. Seguiremos proporcionando actualizaciones cada 30 minutos, o antes si surgen nuevos detalles, ya que trabajamos para resolver este problema lo antes posible.

5. July 25, 2026 at 12:39 AM UTCinvestigating

   Hemos identificado posibles vías de rehabilitación y actualmente estamos progresando en actividades de mitigación activas para restaurar la estabilidad de los servicios. Si bien no tenemos un tiempo estimado firme para la recuperación (ETA) para compartir en esta etapa, por favor tenga la seguridad de que nuestro enfoque principal sigue siendo la solución segura y rápida de esta cuestión. Estamos monitoreando de cerca el impacto de nuestros actuales pasos de mitigación. Nos disculpamos por las molestias en curso. Nuestra próxima actualización será publicada en 30 minutos, o antes como hitos clave se consiguen.

6. July 25, 2026 at 1:08 AM UTCinvestigating

   Entendemos que la perturbación que esto ha causado y queremos asegurarle que resolver esto lo más rápido posible sigue siendo nuestra máxima prioridad. Nuestro equipo está activamente comprometido con la rehabilitación, y las medidas adoptadas están mostrando avances significativos hacia la plena restauración del servicio. Reconocemos su paciencia durante todo este proceso y no lo damos por sentado. Estamos monitoreando nuestros sistemas de cerca y proporcionaremos una actualización adicional dentro de 30 minutos, o antes de que haya un desarrollo significativo que compartir.

7. July 25, 2026 at 1:42 AM UTCinvestigating

   Continuamos ejecutando y validando nuestros planes de rehabilitación. Estamos viendo progresos sostenidos a medida que los esfuerzos de recuperación avanzan sistemáticamente. Para asegurar una recuperación segura y completa, estamos progresando cuidadosamente y todavía no estamos en condiciones de compartir hitos técnicos específicos. Asegúrese de que todo nuestro equipo de respuesta sigue plenamente dedicado a resolver este incidente. Gracias por su paciencia continua. Nuestra próxima actualización será publicada en 30 minutos, o antes tan pronto como tengamos más progresos para informar.

8. July 25, 2026 at 2:18 AM UTCinvestigating

   Actualmente estamos realizando mantenimientos de emergencia en la región del Canadá. El acceso a la plataforma se ha restringido temporalmente mientras nuestro equipo trabaja para completar la rehabilitación y validar la restauración completa de los servicios. Estamos monitoreando activamente el medio ambiente y progresando. Apreciamos su paciencia y entendemos el impacto que esto tiene en su trabajo. Se proporcionarán más actualizaciones cada 30 minutos, o antes si hay un desarrollo significativo que compartir. Nos disculpamos por la inconveniencia y seguimos comprometidos a restaurar el servicio lo antes posible.

9. July 25, 2026 at 3:09 AM UTCinvestigating

   Nuestro equipo sigue participando activamente en los esfuerzos de rehabilitación. El trabajo está progresando a través de múltiples flujos de trabajo y seguimos avanzando hacia la restauración del servicio completo. Proporcionaremos una actualización adicional dentro de 30 minutos, o antes si hay un desarrollo significativo que compartir. Apreciamos su paciencia continua.

10. July 25, 2026 at 3:47 AM UTCinvestigating

    Actualmente realizamos mantenimiento de emergencia en la región del Canadá. Nuestro equipo participa activamente en los esfuerzos de rehabilitación en coordinación con nuestro proveedor, y la cuestión ha sido contenida. El acceso de los clientes al entorno del Canadá sigue estando temporalmente restringido mientras completamos los esfuerzos de validación y restauración. Apreciamos su paciencia y proporcionaremos una actualización adicional dentro de 1 hora, o antes si hay un desarrollo significativo que compartir.

11. July 25, 2026 at 4:47 AM UTCinvestigating

    Nuestro equipo sigue trabajando mediante el mantenimiento de emergencia en la región del Canadá en estrecha coordinación con nuestro proveedor. La cuestión se ha contenido y se están realizando activamente esfuerzos de restauración. El acceso al entorno del Canadá sigue restringido temporalmente al completar las medidas de validación necesarias antes de la restauración del servicio. Reconocemos el impacto que esto tiene en su trabajo y apreciamos su paciencia continua. Nuestra próxima actualización se proporcionará dentro de 1 hora, o antes debe ocurrir un desarrollo significativo.

12. July 25, 2026 at 6:05 AM UTCidentified

    Nuestro equipo sigue trabajando mediante el mantenimiento de emergencia en la región del Canadá en estrecha coordinación con nuestro proveedor. Sin embargo, la cuestión se ha contenido debido a la complejidad y el alcance del proceso de recuperación, esperamos que la restauración sea un esfuerzo prolongado que llevará varias horas completarse. El acceso al entorno del Canadá seguirá estando restringido durante la recuperación. Reconocemos el impacto significativo que esto tiene en su trabajo y apreciamos sinceramente su paciencia. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

13. July 25, 2026 at 7:06 AM UTCidentified

    Nuestros socios de equipo y proveedores siguen progresando en el complejo proceso de recuperación de la región del Canadá durante este mantenimiento de emergencia. Estamos ejecutando sistemáticamente nuestros protocolos de recuperación y validando la integridad del sistema en cada etapa. Como se señaló anteriormente, debido al alcance de este esfuerzo, esto sigue siendo un proceso de recuperación ampliado, y el acceso al entorno del Canadá seguirá estando restringido a medida que trabajemos para una restauración de servicios segura y completa. Seguimos plenamente conscientes del impacto que esta interrupción del servicio tiene en sus operaciones y estamos haciendo todo lo posible para acelerar estos pasos. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

14. July 25, 2026 at 8:07 AM UTCidentified

    Nuestros equipos de ingeniería y proveedores siguen ejecutando activamente las medidas de recuperación de la región del Canadá bajo mantenimiento de emergencia. No hay nuevos detalles técnicos o cambios que compartir en este momento, ya que nuestro enfoque sigue siendo enteramente la restauración sistemática y segura de los servicios. El acceso al entorno del Canadá sigue estando restringido mientras se están llevando a cabo esas actividades de recuperación. Apreciamos su paciencia y asociación continuas mientras trabajamos a través de este esfuerzo prolongado. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

15. July 25, 2026 at 9:06 AM UTCidentified

    Nuestros equipos de ingeniería y socios proveedores siguen progresando a través de las medidas de recuperación para la región del Canadá bajo mantenimiento de emergencia. Estamos haciendo avances positivos y estamos acercándonos a reacondicionar la región para la mayoría de los espacios de trabajo. El acceso al entorno del Canadá sigue estando temporalmente restringido mientras ejecutamos y completamos estas cruciales medidas de validación final para garantizar la estabilidad de los servicios. Apreciamos sinceramente su paciencia y asociación al entrar en estas etapas finales del proceso de recuperación. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

16. July 25, 2026 at 10:07 AM UTCinvestigating

    Seguimos aplicando sistemáticamente nuestras medidas de recuperación para la región del Canadá bajo mantenimiento de emergencia. Nuestros equipos de ingeniería y socios proveedores siguen centrados en las fases de validación final, y seguimos acercándonos para permitir a la región para la mayoría de los clientes. El acceso al entorno del Canadá sigue siendo restringido por el momento para garantizar que mantengamos la estabilidad del sistema durante estas etapas finales críticas. Estamos inmensamente agradecidos por su paciencia y asociación continuas. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

17. July 25, 2026 at 11:14 AM UTCidentified

    Nuestros equipos de ingeniería y socios proveedores siguen progresando sistemáticamente a través de las etapas finales de validación para la región del Canadá bajo mantenimiento de emergencia. Seguimos enfocados en la verificación de la estabilidad del sistema, que nos mantiene en un camino constante hacia la habilitación de la región para la mayoría de los clientes. El acceso al entorno del Canadá sigue estando restringido por el momento para garantizar que se completen plenamente esos controles críticos de seguridad y estabilidad. Estamos increíblemente agradecidos por su paciencia y asociación continua mientras completamos este esfuerzo prolongado. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

18. July 25, 2026 at 12:37 PM UTCidentified

    Nuestros equipos de ingeniería y proveedores están entrando en las fases finales de preparación de nuestro plan de recuperación para la región del Canadá bajo mantenimiento de emergencia. A medida que nos preparamos para restaurar el acceso, nuestro plan es habilitar todos los servicios en la región con la excepción de traer su propia clave (BYOK) configuraciones. Además, un pequeño número de espacios de trabajo permanecerá desactivado inicialmente cuando se restablezca el servicio general. Para estos espacios de trabajo específicos restantes, ejecutaremos un plan de restauración altamente controlado y sistemático para recuperar cada entorno individualmente para garantizar la estabilidad completa e integridad de los datos. El acceso al medio ambiente del Canadá sigue siendo restringido en este momento, mientras que completamos estos pasos finales de validación previa a la disponibilidad. Reconocemos el impacto que esto tiene en sus operaciones y apreciamos sinceramente su paciencia continua. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

19. July 25, 2026 at 1:51 PM UTCidentified

    Actualmente estamos restaurando la plataforma. Nuestros equipos de ingeniería y proveedores están trabajando activamente para restaurar los servicios lo antes posible. Como parte de nuestro plan de recuperación, vamos a restaurar todos los servicios en la región con la excepción de traer su propia clave (BYOK) configuraciones. Además, un pequeño número de espacios de trabajo permanecerá temporalmente discapacitado cuando se restablezca el servicio inicial. Para estos espacios de trabajo específicos, vamos a ejecutar un proceso de restauración altamente controlado y sistemático para recuperar cada entorno individualmente y garantizar la completa estabilidad e integridad de los datos. El acceso al entorno del Canadá sigue estando restringido en este momento Reconocemos el impacto significativo que esto tiene en sus operaciones y apreciamos sinceramente su paciencia continua. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

20. July 25, 2026 at 4:22 PM UTCidentified

    Nuestro equipo de ingeniería está trabajando activamente para restaurar la estabilidad de las plataformas en toda la región del Canadá (CA1) mediante una recuperación cuidadosamente gradual. Inicialmente restauraremos los servicios generales, con la excepción de Traer su propia clave (BYOK) configuraciones. Para garantizar un entorno estable y seguro, un pequeño número de espacios de trabajo pueden permanecer temporalmente discapacitados mientras realizamos restauraciones controladas. El acceso general al entorno del Canadá sigue estando restringido en este momento a medida que completamos estas medidas críticas de restauración. Reconocemos profundamente el impacto significativo que esta situación tiene en sus operaciones y agradecemos sinceramente su paciencia continua mientras trabajamos a través de estas medidas de seguridad. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

21. July 25, 2026 at 5:24 PM UTCidentified

    Hemos permitido el acceso general de los clientes a la región de Canadá. Todos los servicios dentro de la región están siendo puestos en línea, con la excepción de traer su propia clave (BYOK) configuraciones. Además, un pequeño número específico de espacios de trabajo del cliente permanecerá temporalmente deshabilitado. Para estos espacios de trabajo restantes, nuestros equipos de ingeniería están ejecutando un plan de restauración altamente controlado y sistemático para recuperar de forma segura cada entorno individualmente para garantizar la integridad completa de los datos. Apreciamos sinceramente su paciencia y asociación en curso mientras ejecutamos estos pasos finales y precisos de recuperación. Nuestra próxima actualización se proporcionará dentro de una hora, o antes debe ocurrir un desarrollo significativo.

22. July 25, 2026 at 11:28 PM UTCidentified

    Sinceramente nos disculpamos por la perturbación que esto ha causado y apreciamos profundamente su paciencia. El acceso general de los clientes a la región de Canadá ha sido restaurado, y los servicios están volviendo en línea. Traiga sus propias configuraciones Key y un pequeño número de espacios de trabajo permanecen temporalmente fuera de línea mientras completamos una cuidadosa restauración individualizada para garantizar la integridad total de datos. Proporcionaremos una actualización adicional dentro de una hora, o antes si hay un desarrollo significativo que compartir.

23. July 25, 2026 at 11:52 PM UTCidentified

    Se ha restaurado el acceso general de los clientes a la región de Canadá. Workspaces using Bring Your Own Key (BYOK) encryption permanecerá temporalmente fuera de línea mientras completamos la restauración individualizada para cada espacio de trabajo afectado. Proporcionaremos una nueva actualización sobre el estado de restauración de BYOK a las 09:00 UTC el 26 de julio de 2026. Nos disculpamos por la interrupción y gracias por su paciencia.

24. July 26, 2026 at 8:59 AM UTCinvestigating

    Estamos escribiendo para proporcionar una actualización de alto nivel sobre la interrupción de los servicios que afectan al Canadá (CA1) acceso a la región que comenzó el viernes 24 de julio a las 20:35 UTC. A través de la coordinación dedicada de nuestros equipos de ingeniería y socios proveedores, el acceso general a la región del Canadá se volvió a habilitar el sábado 25 de julio a las 17:24 UTC. La gran mayoría de nuestros clientes ahora pueden acceder a sus espacios de trabajo y modelos normalmente. Estado actual y próximos pasos Mientras que el acceso a la región general se ha restaurado completamente, los espacios de trabajo que utilizan Bring Your Own Key (BYOK) encriptación permanecen temporalmente fuera de línea. Nuestro objetivo principal es reproducir con éxito la perturbación técnica dentro de un entorno controlado. Las ideas obtenidas de esta fase de reproducción son críticas, ya que influirán directamente y determinarán el camino de recuperación más seguro y eficaz para los espacios de trabajo de BYOK restantes. Proceder con esta investigación sistemática nos asegura mantener los más altos estándares de estabilidad del sistema e integridad de los datos. Esperamos proporcionar nuestra próxima actualización específica sobre la restauración del espacio de trabajo de BYOK a las 11:00 UTC. Sinceramente nos disculpamos por la perturbación y el impacto que esto ha tenido en sus operaciones. Nuestros equipos de soporte siguen estando plenamente disponibles para ayudarle con cualquier pregunta o necesidades inmediatas.

25. July 26, 2026 at 11:16 AM UTCinvestigating

    Estamos escribiendo para proporcionar una actualización de alto nivel sobre la interrupción de los servicios que afectan al Canadá (CA1) acceso a la región que comenzó el viernes 24 de julio a las 20:35 UTC. A través de la coordinación dedicada de nuestros equipos de ingeniería y socios proveedores, el acceso general a la región del Canadá se volvió a habilitar el sábado 25 de julio a las 17:24 UTC. La gran mayoría de nuestros clientes ahora pueden acceder a sus espacios de trabajo y modelos normalmente. Estado actual y próximos pasos Mientras que el acceso a la región general se ha restaurado completamente, los espacios de trabajo que utilizan Bring Your Own Key (BYOK) encriptación permanecen temporalmente fuera de línea. Nuestro objetivo principal es reproducir con éxito la perturbación técnica dentro de un entorno controlado. Las ideas obtenidas de esta fase de reproducción son críticas, ya que influirán directamente y determinarán el camino de recuperación más seguro y eficaz para los espacios de trabajo de BYOK restantes. Proceder con esta investigación sistemática nos asegura mantener los más altos estándares de estabilidad del sistema e integridad de los datos. Esperamos proporcionar nuestra próxima actualización específica sobre la restauración del espacio de trabajo de BYOK a las 13:00 UTC. Sinceramente nos disculpamos por la perturbación y el impacto que esto ha tenido en sus operaciones. Nuestros equipos de soporte siguen estando plenamente disponibles para ayudarle con cualquier pregunta o necesidades inmediatas.

26. July 26, 2026 at 1:06 PM UTCinvestigating

    Aunque el acceso general a la región del Canadá (CA1) ha sido totalmente restaurado a partir del sábado 25 de julio a las 17:24 UTC, los espacios de trabajo que utilizan Bring Your Own Key (BYOK) encriptación permanecen temporalmente fuera de línea. Nuestro enfoque primario para reproducir la perturbación dentro de un ambiente controlado sigue siendo continuo con nuestro proveedor. Esta es una fase crítica, ya que influirá directamente y determinará el camino de recuperación más seguro y eficaz para los espacios de trabajo restantes de BYOK, garantizando la estabilidad del sistema y la integridad de los datos. Esperamos proporcionar nuestra próxima actualización específica sobre la restauración del espacio de trabajo de BYOK a las 15:00 UTC. Sinceramente nos disculpamos por la perturbación y el impacto que esto ha tenido en sus operaciones. Nuestros equipos de soporte siguen estando plenamente disponibles para ayudarle con cualquier pregunta o necesidades inmediatas.

27. July 26, 2026 at 3:20 PM UTCinvestigating

    El acceso general a la región CA1 sigue siendo totalmente restaurado para la mayoría de los clientes. Los espacios de trabajo que utilizan Bring Your Own Key (BYOK) encriptación permanecen temporalmente fuera de línea mientras finalizamos recuperación segura, validación y análisis de causas raíz. Estamos colaborando activamente con nuestro socio de cifrado de terceros para comprender la causa y la solución potencial.

28. July 26, 2026 at 5:53 PM UTCidentified

    El acceso general a la región CA1 sigue siendo totalmente restaurado para la mayoría de los clientes. Los espacios de trabajo que utilizan Bring Your Own Key (BYOK) encriptación permanecen temporalmente fuera de línea mientras finalizamos recuperación segura, validación y análisis de causas raíz. Estamos colaborando activamente con nuestro socio de cifrado de terceros para comprender la causa y la solución potencial.

29. July 26, 2026 at 6:49 PM UTCidentified

    El acceso general a la región del Canadá (CA1) sigue siendo plenamente restaurado. Sin embargo, los espacios de trabajo que utilizan Bring Your Own Key (BYOK) cifrado permanecerá temporalmente fuera de línea. Proporcionaremos una nueva actualización del estado de restauración de BYOK a las 10:00 UTC el 27 de julio de 2026. Nos disculpamos por esta perturbación y gracias por su paciencia continua.

30. July 27, 2026 at 10:03 AM UTCinvestigating

    Estamos escribiendo para proporcionar una actualización de estado sobre los esfuerzos de recuperación en curso para traer su propio espacio de trabajo Key (BYOK) dentro de la región Canadá (CA1). Los servicios generales de la región siguen siendo totalmente restaurados y funcionan normalmente. Situación actual de la investigación Nuestros equipos de ingeniería y proveedores continúan su profunda investigación sobre la causa raíz de la reciente interrupción del servicio. Actualmente estamos centrando nuestros esfuerzos en reproducir la cuestión dentro de un entorno dedicado a la no producción. Esta replicación controlada es un paso crítico, ya que los resultados técnicos nos permitirán identificar y validar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK. Al asegurarnos de entender a fondo el comportamiento del sistema bajo estas condiciones específicas en la no producción primero, podemos garantizar la absoluta seguridad, estabilidad e integridad de sus datos durante la fase final de restauración. Apreciamos sinceramente su paciencia y asociación mientras ejecutamos estos pasos meticulosos de validación. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes debe alcanzarse un hito significativo.

31. July 27, 2026 at 12:30 PM UTCinvestigating

    Continuamos nuestra planificación activa de investigación y recuperación para traer su propia llave clave (BYOK) espacios de trabajo dentro de la región Canadá (CA1). Los servicios generales de la región siguen siendo plenamente restaurados y siguen funcionando normalmente. Nuestros equipos de ingeniería y socios proveedores siguen centrando sus esfuerzos en replicar la perturbación dentro de un entorno controlado y no productivo. Replicar el escenario en estas condiciones seguras sigue siendo nuestra máxima prioridad, ya que es el paso crítico que nos permitirá identificar y confirmar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK. Estamos procediendo metódicamente para asegurar que el proceso de restauración, una vez iniciado, preserve la estabilidad del sistema y la integridad de los datos. Apreciamos su paciencia y asociación constantes mientras esta profunda validación técnica continúa. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos tener nuevos progresos para compartir.

32. July 27, 2026 at 2:04 PM UTCinvestigating

    Continuamos nuestros esfuerzos activos para restaurar traer su propio espacio de trabajo Key (BYOK) en la región de Canadá (CA1). Los servicios generales de toda la región siguen siendo totalmente restaurados y funcionan normalmente. Para agilizar la resolución, nuestros equipos de ingeniería y socios proveedores persiguen simultáneamente múltiples líneas de investigación. Este enfoque multifacético es fundamental para garantizar que nuestro plan de restauración sea plenamente validado y preserve la integridad de su entorno. Apreciamos sinceramente su paciencia y asociación mientras ejecutamos estos esfuerzos simultáneos. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos lograr un avance significativo.

33. July 27, 2026 at 3:54 PM UTCidentified

    Continuamos nuestros esfuerzos activos para restaurar traer su propio espacio de trabajo Key (BYOK) en la región de Canadá (CA1). Los servicios generales de toda la región siguen siendo totalmente restaurados y funcionan normalmente. Nuestros equipos de ingeniería y socios proveedores persiguen simultáneamente múltiples líneas de investigación. Este enfoque paralelo se está ejecutando deliberadamente para validar y finalizar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK, asegurando que restablezcamos los servicios con seguridad y con el mayor nivel de estabilidad. Apreciamos su paciencia continua mientras nuestros equipos trabajan a través de estos pasos necesarios. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos lograr un avance significativo.

34. July 27, 2026 at 5:37 PM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente, continuamos prestando especial atención a la recuperación de los espacios de trabajo de Bring Your Own Key (BYOK). Nuestros equipos están avanzando sistemáticamente con múltiples flujos de trabajo paralelos. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados, asegurando validar e implementar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK, asegurando que restauramos los servicios con seguridad y con el más alto nivel de estabilidad. Apreciamos su asociación y paciencia en curso mientras ejecutamos estos pasos críticos de recuperación. Proporcionaremos una nueva actualización del estado de restauración de BYOK a las 09:00 UTC (10:00 BST) el 28 de julio de 2026.

35. July 28, 2026 at 9:02 AM UTCidentified

    Los servicios generales en la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente. Para el resto Traiga su propio espacio de trabajo Key (BYOK), nuestros equipos continúan ejecutando múltiples flujos de trabajo paralelos. Este enfoque concurrente se está llevando a cabo deliberadamente para validar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK, garantizando al mismo tiempo la estabilidad absoluta del sistema. Apreciamos su paciencia continua. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

36. July 28, 2026 at 11:01 AM UTCidentified

    Los servicios generales de la región del Canadá (CA1) siguen funcionando normalmente y siguen siendo plenamente estables. Nuestros equipos de ingeniería y proveedores continúan progresando a través de múltiples flujos de trabajo simultáneos para abordar el resto Traiga su propio espacio de trabajo Key (BYOK). Este enfoque paralelo sigue siendo nuestro enfoque activo, lo que nos permite validar y aplicar sistemáticamente el camino de recuperación más eficaz para los espacios de trabajo de BYOK restantes con el más alto nivel de seguridad. Apreciamos su paciencia y apoyo continuos. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

37. July 28, 2026 at 1:11 PM UTCidentified

    Los servicios generales de la región del Canadá (CA1) siguen siendo plenamente restaurados, estables y siguen funcionando normalmente. Nuestros equipos de ingeniería y socios proveedores continúan avanzando con múltiples flujos de trabajo simultáneos para abordar el resto Traiga su propio espacio de trabajo (BYOK). Esta estrategia paralela sigue siendo nuestro enfoque activo, permitiéndonos validar y aplicar sistemáticamente el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK. Apreciamos sinceramente su paciencia continua mientras trabajamos a través de estos pasos deliberados. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

38. July 28, 2026 at 4:02 PM UTCidentified

    Los servicios generales de la región del Canadá (CA1) siguen siendo plenamente restaurados, estables y siguen funcionando normalmente. Nuestros equipos de ingeniería y socios de proveedores están manteniendo activamente su enfoque en los espacios de trabajo restantes Bring Your Own Key (BYOK) a través de múltiples flujos de trabajo paralelos. Apreciamos su paciencia y asociación continuas mientras completamos estas fases de validación crítica. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

39. July 28, 2026 at 7:51 PM UTCidentified

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente, continuamos prestando especial atención a la recuperación de los espacios de trabajo de Bring Your Own Key (BYOK). Nuestros equipos están avanzando sistemáticamente con múltiples flujos de trabajo paralelos. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados, asegurando validar e implementar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK, asegurando que restauramos los servicios con seguridad y con el más alto nivel de estabilidad. Apreciamos su asociación y paciencia en curso mientras ejecutamos estos pasos críticos de recuperación. Proporcionaremos una nueva actualización del estado de restauración de BYOK a las 09:00 UTC (10:00 BST) el 29 de julio de 2026.

40. July 29, 2026 at 9:04 AM UTCidentified

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente, continuamos prestando especial atención a la recuperación de los espacios de trabajo de Bring Your Own Key (BYOK). Nuestros equipos siguen progresando sistemáticamente a través de múltiples corrientes de trabajo paralelas. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados técnicos, asegurando validar e implementar el camino de recuperación más seguro y estable para los espacios de trabajo restantes de BYOK. Apreciamos su asociación y paciencia en curso mientras ejecutamos estos pasos críticos de recuperación. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

41. July 29, 2026 at 1:23 PM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente, continuamos prestando especial atención a la recuperación de los espacios de trabajo de Bring Your Own Key (BYOK). Nuestros equipos siguen progresando sistemáticamente a través de múltiples corrientes de trabajo paralelas. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados técnicos, asegurando validar e implementar el camino de recuperación más seguro y estable para los espacios de trabajo restantes de BYOK. Apreciamos su asociación y paciencia en curso mientras ejecutamos estos pasos críticos de recuperación. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

42. July 29, 2026 at 3:21 PM UTCinvestigating

    Los servicios generales en toda la región del Canadá (CA1) siguen siendo plenamente restaurados y siguen funcionando normalmente. Nuestros equipos de ingeniería y operaciones están manteniendo su enfoque dedicado y concentrado en la recuperación de los espacios de trabajo restantes Bring Your Own Key (BYOK). Para asegurar la restauración más segura posible, estamos avanzando activamente en múltiples flujos de trabajo paralelos de recuperación. Ejecutar estos esfuerzos simultáneamente nos permite analizar rigurosamente los resultados técnicos en tiempo real, asegurando validar e implementar el camino más estable y seguro hacia adelante para los espacios de trabajo restantes de BYOK. Apreciamos sinceramente su paciencia y asociación continuas mientras ejecutamos sistemáticamente estos pasos críticos de recuperación. Nuestra próxima actualización se proporcionará dentro de dos horas, o antes deberíamos alcanzar un hito significativo.

43. July 29, 2026 at 5:17 PM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen siendo totalmente restaurados y funcionando normalmente, continuamos prestando especial atención a la recuperación de los espacios de trabajo de Bring Your Own Key (BYOK). Nuestros equipos están avanzando sistemáticamente con múltiples flujos de trabajo paralelos. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados, asegurando validar e implementar el camino de recuperación más eficaz para los espacios de trabajo restantes de BYOK, asegurando que restauramos los servicios con seguridad y con el más alto nivel de estabilidad. Apreciamos su asociación y paciencia en curso mientras ejecutamos estos pasos críticos de recuperación. Proporcionaremos una nueva actualización del estado de restauración de BYOK a las 09:00 UTC (10:00 BST) el 30 de julio de 2026.

44. July 30, 2026 at 8:59 AM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen funcionando normalmente con plena estabilidad, nuestros equipos técnicos mantienen su especial atención en la recuperación de los espacios de trabajo restantes Bring Your Own Key (BYOK). Seguimos avanzando en múltiples flujos de trabajo paralelos para validar y ejecutar el camino de restauración más seguro posible. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados técnicos, asegurando que restauramos los servicios con el más alto nivel de seguridad y estabilidad para todos los espacios de trabajo destacados de BYOK. Apreciamos su paciencia y asociación continuas mientras trabajamos sistemáticamente a través de estos pasos críticos de recuperación. Proporcionaremos una nueva actualización del progreso de restauración de BYOK en dos horas.

45. July 30, 2026 at 11:07 AM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen funcionando normalmente con plena estabilidad, nuestros equipos técnicos mantienen su especial atención en la recuperación de los espacios de trabajo restantes Bring Your Own Key (BYOK). Seguimos avanzando en múltiples flujos de trabajo paralelos para validar y ejecutar el camino de restauración más seguro posible. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados técnicos, asegurando que restauramos los servicios con el más alto nivel de seguridad y estabilidad para todos los espacios de trabajo destacados de BYOK. Apreciamos su paciencia y asociación continuas mientras trabajamos sistemáticamente a través de estos pasos críticos de recuperación. Proporcionaremos una nueva actualización sobre el estado de restauración de BYOK a las 09:00 UTC (10:00 BST) el 31 de julio de 2026, o antes deberíamos alcanzar un hito significativo.

46. July 31, 2026 at 9:04 AM UTCinvestigating

    Si bien los servicios generales en toda la región del Canadá (CA1) siguen funcionando normalmente con plena estabilidad, nuestros equipos técnicos mantienen su especial atención en la recuperación de los espacios de trabajo restantes Bring Your Own Key (BYOK). Seguimos avanzando en múltiples flujos de trabajo paralelos para validar y ejecutar el camino de restauración más seguro posible. Ejecutar estos esfuerzos simultáneamente nos permite analizar a fondo todos los resultados técnicos, asegurando que restauramos los servicios con el más alto nivel de seguridad y estabilidad para todos los espacios de trabajo destacados de BYOK. Apreciamos su paciencia y asociación continuas mientras trabajamos sistemáticamente a través de estos pasos críticos de recuperación. Proporcionaremos una nueva actualización sobre el estado de restauración de BYOK a las 09:00 UTC (10:00 BST) el 3 de agosto de 2026, o antes deberíamos alcanzar un hito significativo.

47. July 31, 2026 at 1:47 PM UTCresolved

    Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

48. August 11, 2026 at 4:03 PM UTCpostmortem

    **Summary**  On July 24, 2026, at 20:22 UTC, our engineering team began investigating an issue affecting customers in our ca1: Cloud — Canada region. Customers with affected workspaces were unable to open their models. As a precaution, while we validated the scope of the issue, we restricted access to the region behind a maintenance page at 02:18 UTC on July 25. General access to CA1 was restored at 17:24 UTC on July 25. Bring Your Own Key \(BYOK\) workspaces remained offline for additional safeguards, and were re-enabled progressively as those safeguards were validated. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Root cause**  The disruption was caused by a defect in a third-party component used within our BYOK service. The defect only surfaced under a very specific combination of events occurring in a particular order on the same host. When a BYOK workspace was unloaded, the component failed tofully clear one of its local resources, leaving behind a stale reference. When a BYOK workspace was subsequently loaded onto the same host, the component attempted to clean up that stale reference before proceeding. During this step, it incorrectly executed a removal that extended beyond the stale reference and deleted files that were still in active use.   The affected files were captured in our regular backups. Once our engineering team identified the source of the activity, isolated it, and applied protective controls to stop any further impact, restoration became a controlled process of returning each affected file to its most recent backup.  **Recovery**  Our engineering team identified the issue and isolated it at its source, then worked systematically to restore the affected files. This allowed us to bring non-BYOK workspaces back online in a controlled sequence, and general access to CA1 was restored at 17:24 UTC on July 25.  We deliberately kept BYOK workspaces offline while our team worked with the third-party vendor to reproduce the trigger in a controlled, non-production environment. This reproduction gave us the diagnostic evidence the vendor needed to build a fix and to confirm the exact cause. It also allowed us to develop and validate our own temporary safeguards — targeted changes to how BYOK workspaces are scheduled — that eliminated the specific combination of conditions required to trigger the defect. These safeguards act as compensating controls to bring BYOK workspaces back online while the third party completes the permanent fix to the underlying component. We re-enabled BYOK workspaces once those safeguards were validated, ensuring the trigger conditions couldn't recur. The incident was fully resolved on July 31, 2026, at 13:47 UTC.  **Corrective and preventative actions**  Our corrective actions follow two complementary tracks. The first removes the specific combination of conditions required to trigger the defect, using controls we have developed and deployed ourselves as compensating safeguards. The second is the permanent fix to the underlying component itself, which the third party is delivering. Together, these tracks address both the trigger and the defect, so that neither can produce another incident of this kind. We are implementing the following actions to prevent recurrence:  * We have deployed changes that prevent the specific combination of conditions required to trigger the defect. This is a temporary but effective control that removes the trigger today, ahead of the permanent fix.  * We are working with the third party to deploy their validated fix. This removes the defect at its source and closes the underlying cause of this incident.  * We are strengthening how we validate BYOK third-party components in non-production before they reach production, including reproducing a wider range of workspace lifecycle scenarios and event sequences. This gives us stronger assurance to surface these types of issues in non-production and are addressed before they can affect customers.  * We have deployed dedicated alerting on the specific event pattern that triggered this incident and are actively reviewing additional file-level alerting. These alerts provide an additional safety net and earlier warning, enabling faster preventative action before customers are affected.  **Closing**  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.   If you have further questions or concerns, please visit our [Support](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

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

1. July 21, 2026 at 2:30 PM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para ejecutar integraciones de Cloudworks. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. July 21, 2026 at 2:44 PM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

3. July 21, 2026 at 2:54 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

4. July 30, 2026 at 10:22 PM UTCpostmortem

   El 21 de julio de 2026, entre las 14:15 UTC y las 14:50 UTC, el us5: Cloud - región del este de Estados Unidos experimentó una perturbación a las integraciones programadas CloudWorksTM. Durante esta ventana, no se podían activar flujos de trabajo automatizados, y los usuarios podrían haber experimentado dificultades para acceder a los servicios de integración. *Causa de raíz* La cuestión fue desencadenada por una breve interrupción en los sistemas de almacenamiento subyacentes después de un sistema de lanzamiento de rollos. Esto condujo a la pérdida de conectividad dentro del sistema de cronogramas de integración, lo que impidió que las tareas programadas fueran con éxito apagadas o disparadas. *Recuperación* Nuestro equipo de ingeniería identificó el problema y tomó medidas inmediatas. Verificamos la conectividad del sistema a medida que los servicios subyacentes se recuperaron automáticamente, y ejecutamos integraciones de pruebas para validar los flujos de trabajo programados. Estos controles de validación confirmaron que todos los mecanismos de programación habían reanudado con seguridad las operaciones normales sin necesidad de reiniciar el sistema. Para las 14:50 UTC, la cuestión se resolvió completamente. ** Acciones correctivas y preventivas** * Estamos llevando a cabo una investigación profunda sobre el rendimiento del sistema durante las operaciones de reversión para garantizar la estabilidad en condiciones de alta carga. * Estamos implementando cheques de salud mejorados para el cronogramador de integración para asegurar que llegue a un estado "listo" antes de que el tráfico se enrute durante los contratiempos. * Estamos actualizando nuestros procesos de implementación para incluir validación automatizada de la profundidad de la cola de tareas inmediatamente después de cualquier actualización regional o retroceso. * Estamos actualizando nuestra documentación sobre el tamaño de los recursos para este servicio con los valores recomendados de solicitud/limitación para garantizar la capacidad suficiente para operaciones de despliegue y reversión. Nos disculpamos por cualquier impacto que este problema haya tenido en sus operaciones comerciales. Estamos fortaleciendo nuestros sistemas y procedimientos para evitar interrupciones en su negocio y usuarios. If you have further questions or concerns, please visit our [Support](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F) website. Apreciamos su paciencia durante este incidente y valoramos la confianza que deposita en Anaplan.

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

1. July 14, 2026 at 8:04 PM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para ejecutar integraciones de Cloudworks. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. July 14, 2026 at 9:00 PM UTCmonitoring

   Hemos visto que algo ha ido mal. Actualmente estamos investigando el problema, y proporcionaremos una actualización pronto.

3. July 14, 2026 at 9:04 PM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

4. July 14, 2026 at 9:12 PM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

5. July 22, 2026 at 6:15 PM UTCpostmortem

   El 14 de julio de 2026, a las 19:55 UTC, los clientes de nuestro us7: Cloud - región de EE.UU. Oeste experimentaron retrasos y fracasos en el procesamiento de trabajo de integración CloudWorksTM. Los puestos de trabajo de integración que se habían programado para ejecutar en esta región no se completaron como se esperaba, lo que dio lugar a un atraso de procesamiento que se despejó una vez que se restableció el servicio. Causa raíz Un componente de back-end que apoya el servicio CloudWorksTM agotó temporalmente su memoria disponible, lo que llevó a una breve interrupción de la conectividad. Aunque la base de datos se recuperó inmediatamente, los componentes de procesamiento CloudWorksTM retuvieron conexiones inactivas y no pudieron reconectarse automáticamente. Esto impidió que los puestos de trabajo de integración terminaran y causó que se acumularan las tareas programadas. Recuperación Nuestro equipo de ingeniería identificó el problema y tomó medidas inmediatas. El equipo reanudó los componentes de procesamiento CloudWorksTM para limpiar todas las conexiones fijas e inactivas. Para aclarar rápidamente el atraso de los trabajos de integración pendientes, aumentamos temporalmente la capacidad de procesamiento de los componentes. Después de verificar que los trabajos de integración se completaron normalmente y el atraso se había procesado completamente, devolvimos el sistema a su capacidad original. Para 21:14 UTC, la cuestión se resolvió completamente. Medidas correctivas y preventivas Estamos aplicando las siguientes medidas para prevenir la recurrencia: * ** Aumento de la asignación de fondos:** Estamos aumentando la asignación de memoria para el componente de back-end en nosotros7. Esto reduce la probabilidad de que un evento similar de presión de memoria ocurra en el futuro. * ** Optimización de proceso de fondo:** Hemos desactivado ciertos procesos de recogida de métricas de fondo que estaban aportando carga innecesaria al componente back-end. Esto reduce aún más el riesgo de construcción de presión de memoria con el tiempo. * ** Pruebas de resiliencia* Nuestros equipos de ingeniería están realizando pruebas controladas en entornos no productivos para comprender mejor cómo se comporta el servicio CloudWorksTM durante breves interrupciones de conectividad. Este trabajo nos ayudará a mejorar la capacidad del servicio para recuperarse automáticamente —sin requerir intervención manual— si se produce un evento similar en el futuro. Nos disculpamos por el impacto que este problema ha tenido en sus operaciones. Estamos comprometidos con las mejoras descritas anteriormente para evitar perturbaciones similares. Si tiene preguntas o preocupaciones, sírvase ponerse en contacto con [Apoyo](https://support.anaplan.com/).

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

1. July 2, 2026 at 12:00 AM UTCinvestigating

   Actualmente estamos investigando un problema que impacta la capacidad de los clientes para acceder a la Plataforma Anaplan. Estamos trabajando para resolver este problema lo antes posible y proporcionaremos actualizaciones cada 30 minutos o una resolución.

2. July 2, 2026 at 12:30 AM UTCinvestigating

   Gracias por su paciencia mientras seguimos investigando este asunto. Actualmente estamos experimentando una perturbación crítica de los servicios causando plena falta de disponibilidad en las regiones afectadas. Los usuarios que intentan acceder a los servicios en estas regiones encontrarán tiempo de conexión y falta de carga de recursos. Actualmente, todavía no tenemos tiempo para resolver. Seguiremos proporcionando actualizaciones cada 30 minutos a medida que trabajemos para resolver este problema lo antes posible.

3. July 2, 2026 at 12:59 AM UTCinvestigating

   Estamos investigando un problema que afecta el acceso a los usuarios y plataformas en nuestras regiones ME1 y EU5. La investigación inicial apunta a una perturbación del camino de autenticación para esas regiones. Resolver esto es nuestra máxima prioridad, y nuestros equipos de ingeniería están trabajando activamente para restaurar las operaciones normales. Aún no tenemos un ETA. Proporcionaremos otra actualización dentro de 30 minutos, o antes si tenemos información nueva significativa.

4. July 2, 2026 at 1:29 AM UTCinvestigating

   Nuestra investigación sobre la cuestión de acceso a la plataforma y la entrada que afecta a las regiones ME1 y EU5 está en curso. Hemos contratado a nuestro proveedor para apoyo adicional mientras trabajamos para identificar y resolver la causa raíz. Resolver esto sigue siendo nuestra máxima prioridad. Todavía no hay ETA. Proporcionaremos nuestra próxima actualización dentro de 30 minutos, o antes si tenemos información nueva significativa.

5. July 2, 2026 at 1:58 AM UTCinvestigating

   Nuestra investigación sobre la cuestión de acceso a la plataforma y la entrada que afecta a las regiones ME1 y EU5 está en curso. Nuestros equipos de ingeniería han reducido la investigación y están buscando activamente varias líneas de investigación, en colaboración con nuestro socio de infraestructura. El servicio de restauración sigue siendo nuestra máxima prioridad. Todavía no hay ETA. Proporcionaremos nuestra próxima actualización dentro de 30 minutos, o antes si tenemos información nueva significativa.

6. July 2, 2026 at 2:27 AM UTCinvestigating

   Estamos investigando un problema que afecta el acceso a los usuarios y plataformas en nuestras regiones ME1 y EU5. La cuestión comenzó aproximadamente a las 23:52 UTC el 1 de julio de 2026. En coordinación con nuestro socio de infraestructura, hemos reducido con éxito las posibles causas y estamos centrando nuestros esfuerzos de ingeniería en aislar la cuestión para iniciar la mitigación dirigida. Nuestro equipo sigue plenamente dedicado a resolver este problema lo antes posible. Proporcionaremos nuestra próxima actualización dentro de 30 minutos, o antes si tenemos información nueva significativa.

7. July 2, 2026 at 2:55 AM UTCinvestigating

   Seguimos investigando la cuestión que afecta el acceso a los usuarios y plataformas en nuestras regiones ME1 y EU5. Hemos identificado la causa potencial y estamos progresando activamente en las medidas de mitigación para abordar la cuestión y restaurar el pleno servicio. Seguiremos proporcionando actualizaciones como avances de remediación. Proporcionaremos nuestra próxima actualización dentro de 30 minutos, o antes si tenemos información nueva significativa.

8. July 2, 2026 at 3:21 AM UTCmonitoring

   El servicio ahora ha sido restaurado; ahora debe ser capaz de reanudar las actividades normales. Seguiremos vigilando la plataforma para asegurar que no surjan problemas adicionales. Si tiene alguna pregunta, preocupación o sigue experimentando problemas, no dude en ponerse en contacto con Anaplan Support. Le proporcionaremos una actualización final cuando consideremos esta situación totalmente resuelta.

9. July 2, 2026 at 4:00 AM UTCresolved

   Hemos confirmado que la cuestión se resuelve ahora. Nos disculpamos profundamente por cualquier impacto que pueda haber causado esta cuestión. Apreciamos su paciencia y asociación mientras trabajamos a través de este tema. Seguiremos en un plazo de 7 días hábiles con un análisis detallado de causa raíz (RCA) que se compartirá en nuestra página de estado. Si tiene alguna pregunta o preocupación, no dude en ponerse en contacto con nosotros en Anaplan Support.

10. July 10, 2026 at 6:35 PM UTCpostmortem

    El 1 de julio de 2026, aproximadamente a las 23:52 UTC, nuestros sistemas de monitoreo detectaron una interrupción del servicio que impactó a los clientes en el me1: Nube – Oriente Medio y eu5: Nube — regiones de Europa. Durante este tiempo, los clientes afectados no pudieron acceder a la plataforma. El servicio fue restaurado a las 03:21 UTC *Causa de raíz* La perturbación se originó de un cambio de configuración de red planificado a nuestra infraestructura de resolución de nombres internos. Se introdujo una desconfiguración errónea como parte del cambio que dejó en su lugar un conflicto subyacente de enrutamiento. Esto hizo que el tráfico de retorno para buscar nombres internos tomara una ruta incorrecta durante la actividad rutinaria de la red. Como resultado, la resolución del nombre interno comenzó a fracasar en las dos regiones afectadas. Esto impidió que el flujo de autenticación completara y detuvo a los clientes de iniciar sesión. *Recuperación* En detección a las 23:52 UTC, nuestro equipo de ingeniería y nuestro socio de infraestructura comenzaron a investigar en paralelo. Debido a que los problemas de resolución de nombres internos pueden presentarse de varias maneras diversas, el equipo trabajó a través de múltiples líneas de investigación antes de aislar el conflicto de enrutamiento específico responsable. Una vez identificados, volamos el cambio reciente para restaurar la configuración anterior conocida-buena enrutamiento. La conectividad se recuperó progresivamente a medida que el retroceso se propagaba, y por 03:21 UTC, la autenticación fue totalmente restaurada para ambas regiones afectadas. ** Acciones correctivas y preventivas** Estamos implementando las siguientes acciones para prevenir una recurrencia: * Estamos añadiendo validación previa al cambio que detecta específicamente la clase de conflicto de enrutamiento responsable de este incidente. Esto cierra el problema de configuración subyacente antes de que cualquier cambio similar pueda llegar al medio ambiente. * Estamos re-arquitectando la configuración de routing afectada para evitar que esta clase de malconfiguración sea introducida de nuevo. Esto elimina la cuestión subyacente en la fuente. * Estamos mejorando nuestro monitoreo de los caminos de resolución de nombres internos entre nuestros entornos cloud. Esto acorta el tiempo para detectar y resolver esta clase de problema. *Cerrar* Nos disculpamos por el impacto que esta perturbación ha tenido en sus operaciones. Las medidas correctivas anteriores se centran en prevenir la repetición de cualquier cuestión similar en el futuro. Si tiene preguntas o preocupaciones, sírvase ponerse en contacto con [Apoyo](https://support.anaplan.com/).

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

1. June 22, 2026 at 7:29 AM UTCinvestigating

   We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 22, 2026 at 7:48 AM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 22, 2026 at 8:23 AM UTCinvestigating

   We are actively investigating a service disruption currently affecting customers' ability to open Models. This issue is also affecting CloudWorks Integrations. Our engineering teams are prioritizing this issue and evaluating immediate mitigation steps to restore full service as quickly and safely as possible. We do not yet have an estimated time to resolution, but will provide progress updates every 30 minutes or sooner.

4. June 22, 2026 at 8:52 AM UTCidentified

   We are progressing with active mitigation steps to resolve the disruption affecting Model opening and CloudWorks integrations. Initial reports indicate positive outcomes from these activities. Our engineering teams are closely monitoring system stability while we complete the remaining mitigation steps to ensure a full and durable recovery. We will continue to provide updates every 30 minutes as we work to bring all systems back to standard operations.

5. June 22, 2026 at 9:25 AM UTCidentified

   We are currently proceeding with the final remediation steps while continuing our investigation into the root cause. Customers should now be able to open models, though some may still encounter temporary delays; however, CloudWorks integrations are not yet completing. We are monitoring these recovery steps closely to ensure full system stability and will continue to provide updates every 30 minutes.

6. June 22, 2026 at 9:36 AM UTCidentified

   We are pleased to report that all issues affecting model loading have been fully resolved, and normal access has been restored. Additionally, CloudWorks integrations are running again, and our teams are currently processing the accumulated backlog of queued jobs. We are monitoring the queue progression closely to ensure all delayed integrations complete successfully. We will provide our next update in 30 minutes or once the backlog is fully cleared.

7. June 22, 2026 at 10:05 AM UTCidentified

   Our teams confirm that the CloudWorks integration backlog is actively processing and recovering. Access to opening models remains fully restored and stable. We are continuing to monitor the integration queues closely as jobs complete, and we will provide our next status update in 30 minutes.

8. June 22, 2026 at 10:22 AM UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

9. June 22, 2026 at 10:52 AM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

10. July 1, 2026 at 7:34 PM UTCpostmortem

    On June 22, 2026, at 07:20 UTC, we became aware of an issue affecting our us7: Cloud – US region. Customers experienced difficulties loading models, with impact beginning at approximately 05:12 UTC. CloudWorks™ integrations in the region were also unable to run during this period. Customers with active workspace sessions weren't affected. However, any workspace that was unloaded during this time couldn't be loaded until service was restored. Full service was restored at 10:21 UTC.  **Root cause**  A component that manages active workspace resources in the us7 region encountered an unexpected fault and restarted. On restart, the component entered a state where it appeared to be operating normally but couldn't process new workspace requests. Our systems normally recover automatically from this kind of state, but in this case the fault wasn't detected by our recovery processes. We intervened manually and performed a corrective restart of the component, which restored normal operation.  **Recovery**  We conducted a thorough investigation of the platform and identified the source of the issue. We performed a targeted reset of the resource scheduling services to clear the pending connections and restore normal communication. Once communication was re-established at 08:48 UTC, the platform began successfully assigning resources and loading models.  To handle the accumulated backlog of scheduled integrations, we scaled up the processing capacity for CloudWorks™. By 10:21 UTC, the backlog had finished processing, and the issue was fully resolved.  **Corrective and preventative actions**  We're implementing the following actions to prevent recurrence:  * We're deploying enhanced automated monitoring specifically designed to detect the condition seen in this incident, where a component appears operational but isn't processing requests. This closes the detection gap that extended the impact of this issue.  * We're developing automated self-healing for the resource scheduling component, so that a corrective restart can be performed automatically without engineering intervention. This directly addresses the failure mode that caused this incident.  * We're streamlining our scaling procedures for CloudWorks™, so that integration processing capacity can be expanded more rapidly during recovery. This shortens the time to clear integration backlogs following incidents like this one.  We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support](https://support.anaplan.com/) website. We appreciate your patience during this incident and value the trust you place in Anaplan.

1. June 17, 2026 at 7:02 AM UTCinvestigating

   We are currently investigating an issue resulting in some customers not being able to load models. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 17, 2026 at 8:00 AM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 17, 2026 at 8:31 AM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Our technical teams are fully engaged, and restoring normal service operations as quickly and safely as possible is our absolute priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

4. June 17, 2026 at 8:59 AM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Our coordinated technical response has made progress in narrowing down the scope of our investigation. We have isolated the primary area of concern to our storage configuration layer and are evaluating mitigation steps to alleviate the issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

5. June 17, 2026 at 9:22 AM UTCidentified

   We have identified the likely cause of the issue, and we are focused right now on restoring service as quickly as possible. We have identified mitigation steps to alleviate the issue and initial reports indicate positive outcomes of these activities. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

6. June 17, 2026 at 9:50 AM UTCidentified

   We are pleased to report a significant milestone in our resolution efforts. Our cross-functional engineering teams have successfully validated a targeted configuration adjustment to restore access to the affected workspaces. We have initiated a phased deployment of this mitigation across the region to safely and systematically restore full access to all affected workspaces. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

7. June 17, 2026 at 10:06 AM UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

8. June 17, 2026 at 10:23 AM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

9. June 26, 2026 at 5:41 PM UTCpostmortem

   On June 17, 2026, at 06:50 UTC, we became aware of an issue affecting a subset of workspaces in our eu4: Cloud - Europe region. Customers with affected workspaces were unable to load models, seeing persistent loading screens or errors when opening their work. CloudWorks™ integrations in the region also experienced a period of degradation, from approximately 05:20 UTC to 06:26 UTC, because of the same underlying issue. The impact was limited to a specific subset of workspaces — all other regions, and many workspaces in eu4: Cloud - Europe, continued to operate normally. Full service for the affected workspaces was restored at 10:00 UTC.   Root cause  The affected workspaces ran on a previous storage configuration in the eu4 region. Over time, a storage directory used by these workspaces accumulated a large number of small temporary files. The directory reached its operational limit and could no longer accept new file operations. This prevented models from loading for customers whose workspaces were running on this configuration.  Recovery  Our engineering team cleared the accumulated temporary files, which provided immediate relief. We then moved all affected workspaces from the old configuration to the new configuration through an automated process. We checked that model loading was restored through testing. By 10:00 UTC, the issue was fully resolved. On the same day, we implemented a change across the eu4 region to make sure no workspace can be directed to the old configuration.  Corrective and preventative actions  We've taken the following actions to address this incident and prevent it from happening again:  1. We've deployed an update across all regions that prevents any workspace from being directed to the older storage configuration. This eliminates the specific configuration condition that caused this incident.  2. We're decommissioning the older storage configuration. This permanently removes the configuration that caused this incident.  3. We’re strengthening our automated validation checks to confirm that workspaces are running on the correct configuration. This catches any configuration mismatch before it can cause customer impact.  4. We're implementing automated cleanup rules for the temporary files involved in this incident. This prevents storage directories from reaching operational limits and supports faster automatic recovery.  Closing  We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 11, 2026 at 5:20 PM UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 11, 2026 at 5:45 PM UTCidentified

   We want to sincerely apologize to our customers for the continued disruption to the Anaplan Platform today. We understand how critical access to Anaplan is for your business, and we deeply regret the impact this is having on your teams. Our engineers have identified the root cause of this issue and are actively working to restore service. We are currently executing remediation steps and will continue to provide updates here every 30 minutes until full service is restored.

3. June 11, 2026 at 6:15 PM UTCidentified

   We want to start by offering our sincere apologies to every customer affected by today's disruption to the Anaplan Platform. We know your teams rely on Anaplan to do critical work. Our engineering team has identified the root cause and is fully focused on resolution. Active remediation steps are underway, and we are committed to keeping you informed with updates every 30 minutes — or sooner if there is meaningful progress to share.

4. June 11, 2026 at 6:27 PM UTCmonitoring

   We are pleased to share that the core Anaplan Platform has successfully recovered and all primary services are fully operational. Our engineering teams are actively monitoring platform stability while corrective actions to address the underlying root cause continue to advance. We sincerely apologize for the disruption today and recognize that this has been a difficult week for many of our customers. Restoring your trust and ensuring platform stability remains our highest priority. Next update: In 30 minutes or sooner

5. June 11, 2026 at 6:47 PM UTCmonitoring

   Our engineering team has successfully implemented a targeted infrastructure patch and completed a controlled failover to the updated version. All primary services are fully restored and accessible to customers. Our teams remain in active monitoring as we continue to validate the patch and advance corrective work across the remaining infrastructure. We do not anticipate further disruption at this time, and we will continue to monitor platform performance closely over the next several hours. We sincerely apologize for the impact today's incidents have had on your teams. A full incident summary will be published once our corrective actions are complete.

6. June 12, 2026 at 12:30 AM UTCmonitoring

   The issue impacting access to the Anaplan Platform across all affected regions has been mitigated. The platform is stable and all services have returned to normal operation. Corrective measures to prevent recurrence are actively advancing and will continue to be applied to ensure this issue does not reoccur. We are continuing to monitor the platform to confirm stability. We do not anticipate any further customer impact from these activities. We appreciate your patience and partnership. If you have any questions or concerns, please do not hesitate to contact us at Anaplan Support.

7. June 12, 2026 at 3:09 PM UTCresolved

   We would like to provide you with the latest update regarding the recent service disruption affecting our platform. Working in close collaboration with our vendor, our engineering team were able to identify a software bug in our network infrastructure that was causing temporary connection instability. To resolve the instability, we applied the fix recommended by the Vendor for the software bug, then successfully moved platform traffic to updated infrastructure at 18:17 UTC on 11 June. All connections stabilised with no disruption observed post the transition. Since then, the platform has remained stable and our engineering teams have continued to monitor this closely. This is our final update on this incident. We will provide a thorough Root Cause Analysis (RCA) within 7 business days. Thank you for your patience and understanding throughout this incident.

8. June 19, 2026 at 2:38 PM UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 11, 2026 at 4:32 AM UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 11, 2026 at 4:58 AM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 11, 2026 at 5:03 AM UTCidentified

   The symptoms currently being observed are similar to the platform issue experienced earlier today. Our engineering and operations teams have been immediately mobilized and are actively diagnosing the root cause. We treat any recurrence with the utmost urgency and priority. We sincerely apologize for this disruption, we treat any recurrence with the utmost urgency and priority. We will provide another update in 30 minutes, or sooner as we obtain more actionable technical details.

4. June 11, 2026 at 5:25 AM UTCidentified

   We are beginning to see signs of platform recovery, and primary services are starting to stabilize. As systems come back online, a backlog of queued CloudWorks jobs has accumulated and is currently processing. Our engineering teams are closely monitoring the stability of the platform and tracking the queue clearance velocity. We will provide our next update in 30 minutes, or sooner as we confirm continued stability.

5. June 11, 2026 at 5:44 AM UTCmonitoring

   The platform has successfully recovered and is exhibiting stable performance. We are now focused on clearing the accumulated backlog of CloudWorks jobs. Our engineering teams are actively managing and verifying the processing queue to ensure all delayed jobs complete as quickly and safely as possible. We will continue to supervise the queue clearance and will provide our next update in 30 minutes, or sooner as we approach full restoration. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

6. June 11, 2026 at 6:14 AM UTCmonitoring

   The platform remains stable and fully operational. We are continuing to process the remaining backlog of CloudWorks jobs. Our engineering teams are actively overseeing the processing queues to ensure all jobs complete successfully and system performance remains steady. We appreciate your continued patience as we work through this remaining queue. We will provide our next update in 30 minutes, or sooner as queue clearance nears completion.

7. June 11, 2026 at 6:30 AM UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

8. June 11, 2026 at 11:05 AM UTCmonitoring

   We want to keep you informed with the latest update on the service disruption affecting our platform. What we've done We have identified the source of the instability and are actively working to resolve it. Our engineering team, in collaboration with our vendor, has already implemented a configuration change that has reduced the frequency of errors. We are monitoring the platform closely and have seen improvement as a result. We are aware that some customers are experiencing delays and interruptions with their CloudWorks integrations as a direct result of this incident. Our engineering team is actively identifying and resolving any affected integration jobs. Current status The platform is operational. Integration processing is being actively monitored and remediated. We will not consider this incident closed until we are fully satisfied that the platform is stable, all integration jobs are running normally, and the risk of recurrence has been addressed. We will now provide updates every 2 hours, as our investigation progresses and we work with our Vendor. We understand the impact this has had on your operations and we appreciate your patience.

9. June 11, 2026 at 2:01 PM UTCmonitoring

   We want to keep you informed with the latest update on the service disruption affecting our platform. After collaboration with our Vendor, we have identified two fixes to our underlying infrastructure. The first fix has now been implemented successfully without further disruption and initial monitoring is proving positive. We are continuing to liaise with our Vendor for the secondary fix, to ensure no further disruption is caused. The platform remains stable and all Cloudworks integrations are working as expected and the backlog has been cleared. The incident will remain open and we will provide updates every 2 hours or sooner, as we continue to investigate and have full resolution. We understand the impact this has had on your operations and we appreciate your patience

10. June 11, 2026 at 2:31 PM UTCresolved

    We want to provide you with the latest update regarding the recent service disruption affecting our platform. All agreed-upon fixes have been successfully implemented across our underlying infrastructure. Our ongoing monitoring shows that system performance remains stable and positive. Our engineering teams will continue to monitor the platform closely to ensure continued stability. Additionally, we are conducting thorough Root Cause Analysis (RCA) and this will be provided within 7 business days. We sincerely understand the impact this disruption has had on your daily operations, and we deeply appreciate your patience and continued partnership as we work to ensure a reliable experience.

11. June 19, 2026 at 3:02 PM UTCpostmortem

    **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 10, 2026 at 11:14 PM UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to access the Anaplan Platform. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 10, 2026 at 11:34 PM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 11, 2026 at 12:07 AM UTCidentified

   We are starting to observe the first initial signs of platform recovery. Our engineering teams are proceeding with extreme caution and are closely monitoring system stability and telemetry as services begin to stabilize. We remain actively engaged in verifying that this early recovery is sustained. We will provide our next update in 30 minutes, or sooner if we detect any changes in performance.

4. June 11, 2026 at 12:41 AM UTCidentified

   The core platform has successfully recovered, and all primary services are fully operational. We are currently processing a backlog of queued jobs within Cloudworks resulting from the incident. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

5. June 11, 2026 at 12:57 AM UTCmonitoring

   We are pleased to report that the CloudWorks backlog is actively processing, and we are now seeing jobs successfully and steadily completing. System throughput has returned to normal operational levels as the queue continues to clear. Our engineering teams remain focused on monitoring the queue velocity until the backlog is fully exhausted and all services have returned to a completely nominal state. We will provide our next update in 30 minutes, or sooner once queue clearance is complete.

6. June 11, 2026 at 1:15 AM UTCmonitoring

   We are currently processing a backlog of queued jobs within Cloudworks for US1 and US2 region. While this backlog is being processed, some customers may experience delays in processing times. We will continue to track performance and will provide our next update in 30 minutes, or sooner as the backlog clears.

7. June 11, 2026 at 1:52 AM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

8. June 19, 2026 at 3:00 PM UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 10, 2026 at 11:11 AM UTCinvestigating

   We are currently investigating an active incident that may affect Basic Authentication access. If you encounter issues when attempting to access the platform please use the following workaround while we resolve the issue: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support

2. June 10, 2026 at 11:35 AM UTCinvestigating

   Since our last update, we have detected a further degradation in general platform performance. Our engineering teams are actively investigating the root cause with the highest priority, and we will provide further updates as the situation develops Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 10, 2026 at 12:01 PM UTCinvestigating

   Following our previous notification, the ongoing performance issues have escalated, resulting in broader platform-wide degradation. Our senior engineering teams have successfully identified the root cause of the issue and are currently executing targeted remediation steps to restore normal operations as our absolute highest priority. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

4. June 10, 2026 at 12:34 PM UTCinvestigating

   Our engineering teams continue to actively investigate the incident while simultaneously implementing targeted remediation steps to stabilize the platform. We are closely monitoring the system's response to these actions and will provide our updates every 30 minutes as we work to resolve this issue as quickly as possible.

5. June 10, 2026 at 12:51 PM UTCidentified

   The general platform has successfully recovered and is operating normally; however, we are actively addressing a residual issue impacting Cloudworks that is currently preventing integration jobs from completing. Our technical teams remain focused on resolving this remaining component to restore full service across all integrations as quickly as possible. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

6. June 10, 2026 at 1:18 PM UTCidentified

   We are pleased to report that integration jobs are now successfully completing, and our systems are actively processing the accumulated backlog across all regions. To accelerate this recovery, we have scaled out our service capacity, with a particular focus on the us7: Cloud - US region to expedite the clearance of its more significant backlog. We will provide further updates in 30 minutes or upon resolution.

7. June 10, 2026 at 1:27 PM UTCidentified

   We are pleased to report that integration processing has returned to normal operational levels across all global regions, with the sole exception of us7: Cloud - US. The us7: Cloud - US region continues to steadily work through its remaining queue utilizing our expanded capacity, and we are monitoring progress closely to ensure a complete return to baseline performance. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

8. June 10, 2026 at 1:55 PM UTCidentified

   As we continue our active recovery efforts, we have identified localized capacity constraints in the us1: Data Center - US East region that may intermittently affect customers attempting to load models. Our engineering teams are addressing this resource bottleneck to restore full service. The CloudWorks backlog in us7: Cloud - US has finished processing, and the service has returned to normal operations. While an estimated time to resolution is not yet established, our teams are treating this with the highest urgency. We will provide our next update in 30 minutes, or sooner if a resolution is reached.

9. June 10, 2026 at 2:33 PM UTCinvestigating

   Our investigation indicates that the backend connectivity issues in US1, stemming from a localized network disruption, are specifically isolated to the loading of large models in excess of 200GB. Customers attempting to load smaller models should experience normal performance and remain unaffected as our network engineering teams actively work to restore stable pathways for larger model payloads. Currently, we do not yet have a time to resolution. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

10. June 10, 2026 at 3:04 PM UTCidentified

    Our network engineering teams continue to actively implement remediation steps to address the localized network issue in the us1: Data Center - US East region. We remain focused on resolving the backend connectivity disruptions affecting the loading of larger models, while smaller models continue to perform normally. We are closely monitoring system behavior as we deploy these targeted fixes and will provide our next update in 30 minutes, or sooner if significant progress is made. Currently, we do not yet have a time to resolution. We will provide further updates in 30 minutes or upon resolution.

11. June 10, 2026 at 3:27 PM UTCmonitoring

    Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

12. June 10, 2026 at 4:35 PM UTCresolved

    We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

13. June 19, 2026 at 2:58 PM UTCpostmortem

    **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 10, 2026 at 9:48 AM UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to run Cloudworks integrations. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 10, 2026 at 10:15 AM UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

3. June 10, 2026 at 10:42 AM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

4. June 19, 2026 at 3:12 PM UTCpostmortem

   **Introduction**   On June 10, 2026, at 09:48 UTC, customers in us1: Data Center - US East experienced slight delays in the processing and successful completion of CloudWorks™ integrations.   **Root cause**  During routine database patching on June 10, all regions completed without issue except for the us1: Data Center - US East region, where CloudWorks encountered an unexpected loss of database connectivity. This caused deadlocks within the scheduler service.  Our investigation determined that one remote connection had been dropped while a second remained active, resulting in connection conflicts and errors. The issue was remediated by performing a rolling restart of the scheduler service and clearing the database rules.  **Recovery**  Upon identifying the issue, our engineering team acted quickly to initiate a rolling restart of the scheduler service across the affected region. To fully resolve the connection conflict and errors, the team cleared the internal routing and caching rules associated with the database gateway. Following this action, the database connection errors ceased immediately, and manual validation confirmed that integration scheduling had been fully restored. The issue was completely resolved by 10:42 UTC.  **Corrective and preventative actions**  We are implementing the following actions to prevent recurrence and improve service reliability:  * We are developing enhanced system alerts to immediately detect database connectivity issues and abnormal error volumes.  * We are working to replicate the scenario in non-production environments to strengthen CloudWorks' ability to recover from database disconnections.   * We are currently reviewing the errors encountered, along with the relevant system settings, to determine whether any changes can be implemented to better handle this type of issue in the future.  * We are reviewing and optimizing the capacity and sizing of our integration services across all regions to ensure they are robust and resilient.  * We are establishing more detailed incident response runbooks and centralizing triage procedures to accelerate resolution of similar issues.   * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly.  We apologize for any impact this issue may have had on your business operations.` `We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.

1. June 9, 2026 at 11:14 AM UTCinvestigating

   We are currently investigating an active incident that may affect Basic Authentication access. If you encounter errors when attempting to log in please do the following: - Close your current session— Close the active browser tab or open a new Incognito/Private window. - Re-authenticate— Navigate to the portal and log in again with your credentials to establish a fresh session. We are actively monitoring the platform and will continue to do so until the issue is fully resolved. If you are still experiencing difficulties or have any questions, please reach out to Anaplan Support We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 9, 2026 at 11:28 AM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

3. June 19, 2026 at 2:45 PM UTCpostmortem

   **June 8–12, 2026 Platform Disruptions** On June 8, 2026, at 11:05 UTC, our monitoring detected a brief drop in incoming traffic across the Anaplan platform, with automated monitoring checks failing across all affected regions \(us1: Data Center - US East, us2: Data Center - US West, eu1: Data Center - Netherlands, eu2: Data Center - Germany, eu4: Cloud - Europe, us5: Cloud - US East, us7: Cloud - US, and ap1: Cloud - Japan\). Over the four days, a series of related disruptions affected the same regions. Customers experienced intermittent difficulties logging in, opening models, and running integrations. The platform was fully stabilized on June 11, 2026, at 18:12 UTC. These disruptions are linked to our previously communicated infrastructure modernization program. On the weekend of June 6, we migrated our control plane, the part of the platform that directs how traffic is routed between services. This was the most complex of the planned migration weekends, and it was completed successfully, as had the two previous migration weekends. The issues described in this report emerged in the days following that migration. This report covers the seven linked incidents that occurred between June 8 and June 11, 2026. **Root cause** As part of our infrastructure modernization program, on the weekend of June 6, we completed a successful migration of our control plane. In the days that followed, we observed two discrete network-hardware issues that interacted to drive these disruptions. _Issue 1: Media Access Control \(MAC\) flapping \(June 8–9\)_ Every device on a network has a MAC address, a unique hardware identifier that network switches use to route traffic to the correct destination. In our environment, the MAC addresses involved are virtual — assigned to logical network gateways rather than to fixed physical hardware — which allows them to legitimately move between hosts as part of normal operation. MAC flapping occurs when a switch sees the same MAC address appearing on two different physical ports in rapid succession, forcing it repeatedly to update its routing tables. This briefly slows or interrupts traffic. For customers, this surfaced as a brief, self-recovering instability. Short bursts of load and intermittent errors appeared and cleared on their own within minutes. The trigger for this behavior was the specific way live production traffic interacted with the new post-migration network. To resolve the issue, we scaled capacity, engaged our vendor, and deployed configuration changes to contain the impact. _Issue 2: network card driver defect \(June 10–11\)_ Once the first set of mitigations were in place, we identified a second issue: A defect in the network card driver, which is the software that controls how a network card sends and receives data. The defect affected fewer than 0.005% of the cards in our estate. Those cards failed randomly and unpredictably, dropping traffic while still appearing healthy to our monitoring systems. This is known as a "gray failure" condition, because the affected components don’t flag themselves as broken. The cards sat in the part of the network that routes traffic between the regions impacted. This resulted in failures that cascaded across the platform and drove disruptions on June 10 and June 11. The defect hadn't been observed in previous migrations or in any other environment, and there were no indicators in pre-deployment testing. The gray failure pattern was also what initially masked the defect as a load issue, until further investigation pointed us to the driver itself. We engaged our vendor, who confirmed the defect. Working closely with them, we rapidly prepared, tested, and deployed the patch to the affected hosts on the evening of June 11, UTC. After that, the platform stabilized. **Recovery** From the first occurrence on June 8 through to permanent resolution on June 11, our engineering team led a continuous, round-the-clock response, working closely with our vendor to identify, diagnose, and resolve the underlying defect. We deployed configuration mitigations, repeatedly rerouted traffic between hosts and across alternative network paths, and scaled out capacity to restore service to customers as quickly as possible while the underlying defect was being addressed. The seven linked incidents and their impact windows were: * **June 8, 2026, 11:00–11:20 UTC** — A short network disruption from the initial MAC flapping event caused intermittent login failures and slow page loads. For most customers, this appeared as a brief 6-minute blip and recovered automatically. Some basic authentication users experienced a longer impact and needed to start a new browser session, with full recovery by 11:20 UTC. * **June 9, 2026, 11:05–11:29 UTC** — A recurrence of the same MAC flapping condition caused a similar brief disruption. Again, most customers experienced only a short blip of around 6 minutes, with basic authentication users seeing a longer impact. We applied scaling changes to address the issue. * **June 10, 2026, 11:02–12:40 UTC** — Customers across all affected regions experienced a loss of access to the platform for approximately 98 minutes. We worked with the vendor and applied configuration changes to address the issue. * **June 10–11, 2026, 23:06–00:04 UTC** — A disruption of approximately 58 minutes, caused when the network card defect affected the backup host that traffic had been moved to. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 03:43–05:20 UTC** — A disruption of approximately 97 minutes, as the next backup host was affected by the same defect. We restored connectivity by moving traffic onto an alternative network path. * **June 11, 2026, 11:10–13:02 UTC** — A further recurrence of the network traffic surge caused customers to experience slow or failed access to the platform. We restored service by applying an underlying configuration change. * **June 11, 2026, 17:04–17:48 UTC** — A final disruption of approximately 44 minutes during which we moved traffic to a host running the updated network card driver. The platform was fully stabilized at 18:12 UTC on June 11, 2026, once traffic was successfully moved to a host running the updated network card driver. We then applied the same update to a second host for resilience. Monitoring continued through to midday Friday before the incident was closed. CloudWorks™ experienced a backlog of queued jobs during and immediately after each disruption. Our engineering team scaled out CloudWorks capacity to accelerate processing, and the backlog was fully cleared shortly after each recovery. **Corrective and preventative actions** The control plane migration that preceded these disruptions was a one-time, foundational piece of work. The actions below reflect the learnings we are carrying forward from the event to further strengthen the platform. 1. The updated network card driver has been rolled out across all hosts matching the affected hardware profile, in every region. This removes the underlying defect from our infrastructure, even though it hasn't been observed in any other region. 2. The conditions that allowed MAC flapping to surface as customer-visible instability have been addressed at multiple layers. Configuration changes have been deployed in the affected regions. The underlying network configuration has been standardized across the wider production estate, and we have tuned the network behavior that triggered the initial event. 3. During the incident, our engineering team deployed dedicated alerting in real time for the specific network conditions causing the disruptions, enabling faster detection and intervention throughout the response. We are continuing to strengthen proactive monitoring and early-warning detection across post-release windows, so that emerging anomalies are surfaced and investigated before they escalate into customer-visible disruptions. 4. The remaining infrastructure update that supports the network card fix is being completed across our other environments. This brings the full benefit of the fix to every part of our infrastructure. **What's next** One final migration weekend is scheduled for June 20, 2026. After this, the migration phase of the infrastructure modernization program is complete. **Closing** We apologize for the impact this issue has had on your operations. We're committed to the improvements outlined above to prevent similar disruptions. If you have questions or concerns, please contact [Support](https://support.anaplan.com/).

1. June 8, 2026 at 1:25 PM UTCinvestigating

   We are currently investigating an issue impacting customers’ ability to run Cloudworks integrations. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

2. June 8, 2026 at 1:52 PM UTCinvestigating

   Thank you for your patience as we continue to investigate this issue. Currently, we do not yet have a time to full resolution.  Access to the UI has been restored and we are currently investigating the degradation to integrations. We will continue to provide updates every 30 minutes as we work to resolve this issue as quickly as possible.

3. June 8, 2026 at 3:18 PM UTCinvestigating

   We are currently investigating an issue impacting impacting Cloudworks. We are working to resolve this issue as quickly as possible and will provide updates every 30 minutes or upon resolution.

4. June 8, 2026 at 3:31 PM UTCmonitoring

   Service has now been restored; you should now be able to resume normal activities. We will continue to monitor the platform to ensure no additional issues arise. If you have any questions, concerns, or continue to experience issues, please do not hesitate to contact Anaplan Support. We will provide a final update to you when we consider this situation fully resolved.

5. June 8, 2026 at 3:51 PM UTCresolved

   We have confirmed that the issue is now resolved. We deeply apologize for any impact this issue may have caused. We appreciate your patience and partnership as we worked through this issue. We will follow up within 7 business days with a detailed root cause analysis (RCA) that will be shared on our Status Page. If you have any question or concerns, please do not hesitate to contact us at Anaplan Support.

6. June 17, 2026 at 5:08 PM UTCpostmortem

   **Introduction**  On June 8, 2026, at 13:14 UTC, customers in our ap1: Cloud - Japan, eu1: Data Center - Netherlands, eu2: Data Center - Germany, us2: Data Center - US West, us5: Cloud - US East, us7: Cloud - US, and eu4: Cloud - Europe regions experienced delays and difficulties accessing the CloudWorks™ user interface. During this period, users experienced slow UI access and a temporary inability to create new integrations or run certain scheduled jobs. Existing workflows were unaffected, although some experienced minor delays in completion.  **Root cause**  The root cause of this incident was an incorrect configuration setting where certain backend components did not automatically pick up updated hostname configurations following a scheduled system migration. Consequently, these components continued to attempt connections using the outdated configuration, leading to connection failures. This prevented users from accessing the user interface and successfully initiating new integration runs. The issue was resolved by reloading the updated configuration on the affected services.  **Recovery**  Our engineering team identified the issue and took immediate action. We initiated a rolling restart of the job management service across the affected regions, which restored user interface access. To fully resolve the connection errors, the engineering team performed a comprehensive restart of all related service components in every affected region, forcing them to load the updated database configurations. Following these restarts, database connection errors immediately ceased, and manual validation confirmed that both user-interface access and integration scheduling were fully restored and functioning normally. By 15:52 UTC, the issue was fully resolved.  **Corrective and preventative actions**  We are implementing the following actions to prevent recurrence and improve service reliability:  * We are developing enhanced system alerts to immediately detect database connectivity issues and abnormal error volumes.  * We are reviewing and optimizing the capacity and sizing of our integration services across all regions to ensure they are robust and resilient.  * We are establishing more detailed incident response runbooks and centralizing triage procedures to accelerate resolution of similar configuration mismatches.  * We are strengthening our platform observability and system telemetry to improve our diagnostic capabilities and detect connection issues more rapidly.  * We are refining our strategy and APIs to proactively detect and manage delayed integration workflows.   We apologize for any impact this issue may have had on your business operations. We are continuously strengthening our systems and procedures to ensure we avoid future disruptions to your business and users.  If you have further questions or concerns, please visit our [Support website](https://www.google.com/url?q=https%3A%2F%2Fsupport.anaplan.com%2F). We appreciate your patience during this incident and value the trust you place in Anaplan.