Historial de interrupciones de Palo Alto Networks

1. August 11, 2026 at 11:06 AM UTCinvestigating

   WildFire is currently experiencing an issue in the regional Clouds. We are actively working on this issue and will provide another update by with 1:00 PM UTC for frther details. Customer Impact: Service degradation. Workaround: NA

2. August 11, 2026 at 12:08 PM UTCidentified

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

3. August 11, 2026 at 12:09 PM UTCmonitoring

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

4. August 11, 2026 at 12:09 PM UTCresolved

   This incident has been resolved.

1. August 7, 2026 at 6:55 AM UTCmonitoring

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

2. August 12, 2026 at 3:30 PM UTCmonitoring

   We are continuing to monitor for any further issues.

1. August 2, 2026 at 12:29 AM UTCinvestigating

   El Portal de Servicio al Cliente pasará por una gestión de cambios de emergencia no planificada para abordar un problema que repercute en la infraestructura. Los clientes pueden enfrentar problemas de inicio de sesión intermitente y fallos de activación de licencias de 8.2.26 12:00a a 8.2.26 a 3:30a UTC.

2. August 2, 2026 at 3:16 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 1, 2026 at 12:25 AM UTCidentified

   Los clientes que utilizan Panorama para gestionar su entorno Native Next-Generation Firewall (CNGFW) de Azure Cloud pueden experimentar errores al crear o actualizar firewalls y servicios, o al utilizar servicios de registro. Hemos identificado la cuestión y estamos trabajando activamente en una solución. Nuestra próxima actualización será proporcionada por 9:00 PM PT el 1 de agosto de 2026

2. August 2, 2026 at 6:13 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 30, 2026 at 3:35 AM UTCinvestigating

   El equipo de gestión de incidentes está trabajando activamente en la cuestión.

2. July 30, 2026 at 4:43 AM UTCinvestigating

   El número fue identificado como agotamiento de la piscina NAT en el cortafuegos debido al tráfico pesado de un solo IP. Esto ha sido remediado y los servicios se restauran parcialmente. El equipo de incidentes sigue vigilando.

3. July 30, 2026 at 5:16 PM UTCinvestigating

   Esta cuestión se ha resuelto y el Portal de Atención al Cliente si está plenamente operativo.

4. July 30, 2026 at 5:29 PM UTCinvestigating

   RCA en progreso.

5. July 30, 2026 at 5:32 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 17, 2026 at 6:44 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 17, 2026 at 7:28 AM UTCidentified

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

3. July 17, 2026 at 8:58 AM UTCmonitoring

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

4. July 17, 2026 at 10:50 AM UTCresolved

   Este incidente ha sido resuelto.

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

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

   Actualmente estamos investigando mayores tasas de error y latencia en múltiples regiones.

2. July 16, 2026 at 11:18 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 16, 2026 at 11:57 AM UTCmonitoring

   Hemos implementado una solución y estamos viendo que la funcionalidad comienza a volver a la normalidad en algunas regiones. Seguiremos vigilando la situación.

4. July 16, 2026 at 12:54 PM UTCmonitoring

   Todavía estamos viendo algunos problemas intermitentes en varias regiones, pero las tasas de error han disminuido significativamente. Estamos trabajando para aliviar estos problemas intermitentes ahora.

5. July 16, 2026 at 1:57 PM UTCmonitoring

   Estamos viendo la recuperación total en todas las regiones ahora. Seguiremos vigilando durante unas horas antes de resolver el incidente.

6. July 16, 2026 at 7:12 PM UTCresolved

   Este incidente ha sido resuelto.

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

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

   We are currently investigating this issue.

2. July 10, 2026 at 7:19 AM UTCidentified

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

3. July 10, 2026 at 7:24 AM UTCmonitoring

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

4. July 10, 2026 at 7:27 AM UTCmonitoring

   We have applied a fix and are currently monitoring the system.

5. July 10, 2026 at 10:05 AM UTCmonitoring

   We are still monitoring and waiting for the system to catch up.

6. July 10, 2026 at 1:10 PM UTCmonitoring

   We are continuing to monitor the system as it catches up on the lag.

7. July 10, 2026 at 1:37 PM UTCresolved

   This incident has been resolved.

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

1. July 7, 2026 at 7:36 PM UTCinvestigating

   We are currently investigating this issue.

2. July 7, 2026 at 8:07 PM UTCidentified

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

3. July 7, 2026 at 9:30 PM UTCmonitoring

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

4. July 8, 2026 at 12:00 AM UTCresolved

   This incident has been resolved.

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

1. July 7, 2026 at 6:06 PM UTCmonitoring

   Hemos identificado un problema con Azure que afecta a las regiones de Cloud NGFW westeurope y Southcentralus. Los clientes pueden experimentar fallos durante el autoescalamiento y durante el despliegue de nuevos recursos. Situación actual: Azure está experimentando problemas de capacidad informática en las regiones. Esto está impactando nuestra capacidad de escalar nuevas máquinas virtuales. Acciones en curso: Nuestro equipo de ingeniería está monitoreando los esfuerzos de recuperación del proveedor y está preparado para validar la salud de los servicios tan pronto como la infraestructura se estabilice. Siguiente actualización: 13 de julio, 8:00UTC

2. July 12, 2026 at 4:53 AM UTCmonitoring

   Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso. Siguiente actualización: 13 de julio, 8:00UTC

3. July 12, 2026 at 4:53 AM UTCmonitoring

   Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso. Siguiente actualización: 15 de julio, 8:00UTC

4. July 15, 2026 at 3:12 PM UTCmonitoring

   Actualización - Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso. Siguiente actualización: 16 de julio, 8:00UTC

5. July 17, 2026 at 12:10 PM UTCmonitoring

   Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso. Siguiente actualización: 20 de julio, 8:00UTC

6. July 22, 2026 at 5:05 AM UTCmonitoring

   Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso. Siguiente actualización: 23 de julio, 8:00UTC

7. July 23, 2026 at 8:00 PM UTCmonitoring

   Nos impacta un problema de capacidad dentro de los centros de datos Azure que afectan a Cloud NGFW en Europa Occidental y regiones del Sur de Estados Unidos. Los clientes pueden experimentar fallos durante el autoescalamiento, las migraciones panorámicas, las migraciones a instancias premium, actualizaciones de software o el despliegue de nuevos recursos. Hasta que el problema de la capacidad sea resuelto por Microsoft: - Mantener Steady-State: Mantener las configuraciones de recursos actuales intactas y posponer las migraciones de SKU premium o las migraciones panorámicas. - Normalizar el tráfico: Mantenga sus bases de datos de tráfico actuales cuando sea posible para evitar desencadenar necesidades repentinas de autoescalamiento. - Diferir nuevos despliegues: Mantenerse en el lanzamiento de nuevos recursos hasta que se restablezca toda la capacidad.

8. July 27, 2026 at 7:02 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

9. August 3, 2026 at 7:05 AM UTCmonitoring

   Azure sigue trabajando en recuperación. Estamos monitoreando continuamente su progreso.

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

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

   We are currently investigating this issue.

2. July 2, 2026 at 11:22 AM UTCidentified

   We have identified the issue and actively working on a solution.

3. July 2, 2026 at 1:12 PM UTCidentified

   We have applied a mitigation and currently monitoring the progress.

4. July 2, 2026 at 5:09 PM UTCidentified

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

5. July 2, 2026 at 5:16 PM UTCmonitoring

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

6. July 2, 2026 at 5:55 PM UTCresolved

   This incident has been resolved.

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

1. June 30, 2026 at 9:30 PM UTCidentified

   We are aware of an ongoing AWS operational issue in the EU-NORTH-1 (Stockholm) region affecting EC2 APIs and Elastic Load Balancing. This is impacting provisioning and management operations for Cloud NGFW resources in EU-NORTH-1. Existing Cloud NGFW instances and traffic processing are not affected — the impact is limited to new instance launches and API-driven operations in this region. We are monitoring AWS's progress and will update as we learn more.

2. June 30, 2026 at 10:04 PM UTCresolved

   The issue has been resolved and all services are operating normally.

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

1. June 30, 2026 at 1:52 PM UTCinvestigating

   We are currently investigating this issue.

2. June 30, 2026 at 3:15 PM UTCresolved

   This incident has been resolved.

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

1. June 29, 2026 at 4:15 PM UTCinvestigating

   WildFire is currently experiencing an issue in the Singapore Cloud. We are actively working on this issue and will provide another update by 18:00 UTC with further details. Customer Impact: Intermittent failures may occur during the file upload process and while querying verdicts. Workaround: N/A

2. June 29, 2026 at 11:38 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 30, 2026 at 12:39 AM UTCidentified

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

4. June 30, 2026 at 1:25 AM UTCmonitoring

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

5. June 30, 2026 at 1:34 AM UTCresolved

   This incident has been resolved.

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

1. June 29, 2026 at 12:57 PM UTCinvestigating

   We are currently investigating this issue.

2. June 29, 2026 at 1:10 PM UTCidentified

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

3. June 29, 2026 at 2:38 PM UTCmonitoring

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

4. June 29, 2026 at 3:06 PM UTCresolved

   This incident has been resolved.

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

1. June 25, 2026 at 9:33 AM UTCidentified

   We have identified a service disruption affecting Cloud NGFW. Customers may experience degraded performance or connectivity. Current Status: An issue within the Data Plane has triggered a degraded service interruption. Our team has initiated a high-priority incident response to restore normal traffic flow as quickly as possible. Ongoing Actions: We are currently working on the resolution. Next Update: 11:30 UTC 25th Jun 2026

2. June 25, 2026 at 11:18 AM UTCresolved

   This incident has been resolved.

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

1. June 18, 2026 at 3:02 PM UTCinvestigating

   Alerts are delayed in app2.eu stack, we are investigating.

2. June 18, 2026 at 7:46 PM UTCidentified

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

3. June 18, 2026 at 10:16 PM UTCidentified

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

4. June 18, 2026 at 10:30 PM UTCmonitoring

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

5. June 18, 2026 at 11:38 PM UTCresolved

   This incident has been resolved.

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

1. June 16, 2026 at 4:41 PM UTCinvestigating

   We are currently experiencing issues with Cortex XDR/XSIAM – EU region. We are actively working on this and will post continuous updates on the issue. The current impact is that agents in EU region are having sporadic connectivity issues to Cortex XDR. All agent side protection is still active as well as the UI connectivity

2. June 16, 2026 at 5:12 PM UTCresolved

   This incident has been resolved.

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

1. June 11, 2026 at 12:57 AM UTCinvestigating

   API Gateway is currently experiencing an issue . We are actively working on this issue and will provide another update by 3:00 AM UTC with further details.

2. June 11, 2026 at 1:38 AM UTCresolved

   This incident has been resolved.

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

1. June 5, 2026 at 5:38 PM UTCresolved

   Between 7:40am - 9:20am, Enterprise DLP in the US East region experienced increased latency and error rates for all traffic utilizing the EDM feature. The issue has been resolved and we are continuing to monitor the situation.

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