Historial de interrupciones de Prisma Cloud

1. August 18, 2026 at 12:41 PM UTCinvestigating

   Actualmente estamos experimentando un problema de inicio de sesión en prisma CLOUD. La autenticación de dos factores (2FA) no funciona debido a un problema con nuestro proveedor de autenticación. Estamos investigando el problema y trabajando para restaurar la funcionalidad normal de inicio de sesión lo antes posible.

2. August 18, 2026 at 1:56 PM UTCidentified

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

3. August 18, 2026 at 2:19 PM UTCmonitoring

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

4. August 18, 2026 at 6:10 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 21, 2026 at 9:21 AM UTCresolved

   prisma APP experimentó una degradación temporal del rendimiento. The issue was investigated, the root cause was identified, and corrective actions were implemented. La degradación puede haber causado breves períodos de falta de servicios para algunos usuarios. Se ha restaurado el rendimiento y la aplicación funciona normalmente.

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

1. July 13, 2026 at 8:25 AM UTCresolved

   prisma APP experienced a temporary performance degradation. The issue was investigated, the root cause was identified, and corrective actions were implemented. The degradation may have caused brief periods of service unavailability for some users. Performance has been restored, and the application is operating normally.

1. April 14, 2026 at 6:36 AM UTCinvestigating

   We are currently investigating this issue.

2. April 14, 2026 at 6:42 AM UTCidentified

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

3. April 14, 2026 at 6:51 AM UTCmonitoring

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

4. April 14, 2026 at 7:17 AM UTCresolved

   The incident has been fully resolved. The root cause was an error during scheduled infrastructure maintenance performed by our hosting provider. We have implemented technical safeguards to prevent similar issues in the future. In parallel, we are working with our hosting provider on additional organizational measures to further minimize such risks. We confirm that no data was lost and data consistency was not affected at any point. We sincerely apologize for any inconvenience caused and appreciate your patience.

1. January 28, 2026 at 4:44 PM UTCinvestigating

   We are aware of an availability issue with our API and are working on a fix.

2. January 28, 2026 at 4:44 PM UTCidentified

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

3. January 28, 2026 at 5:16 PM UTCmonitoring

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

4. January 28, 2026 at 5:46 PM UTCresolved

   This incident has been resolved.

1. April 14, 2025 at 6:39 AM UTCinvestigating

   We are currently experiencing a data processing issue. Our team is fully engaged and making every effort to resolve the problem as quickly as possible.

2. April 14, 2025 at 8:54 AM UTCinvestigating

   We are continuing to work on restoring prisma CLOUD functionality. We apologize for the inconvenience and will provide the next update at 10:00 AM UTC.

3. April 14, 2025 at 9:33 AM UTCidentified

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

4. April 14, 2025 at 11:32 AM UTCidentified

   We have identified and fixed the root cause of the issue. However, our system needs additional time to process the accumulated data. We expect this process to be completed around 16:00 CEST / 2:00 PM UTC. After that, all data will be fully available again. We apologise for the inconvenience and appreciate your patience.

5. April 14, 2025 at 2:16 PM UTCmonitoring

   prisma CLOUD is back online and we are closely monitoring the system to ensure stable operation. Thank you for your patience!

6. April 14, 2025 at 4:46 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. April 14, 2025 at 4:46 PM UTCresolved

   This incident has been resolved.

1. April 8, 2025 at 3:24 PM UTCidentified

   We are aware of an issue where detailed night overview data is unavailable in some cases due to processing issues. No data will be lost — our team is currently re-processing the affected entries. Updates will follow shortly.

2. April 8, 2025 at 6:12 PM UTCmonitoring

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

3. April 8, 2025 at 6:36 PM UTCresolved

   This incident has been resolved.

1. April 7, 2025 at 10:05 AM UTCresolved

   On April 6th, around 08:00 AM CEST, during routine preparations for prisma CLOUD release on the next day, we experienced an incident in prisma CLOUD, which led to downtime from approximately 08:00 AM to 09:30 AM CEST. There were no further risks or issues. No customer data was lost. We apologize for the unplanned downtime.

1. November 16, 2024 at 12:27 PM UTCresolved

   There was an unexpected downtime during infrastructure maintenance. The system was unavailable from 08:25 CET to 08:50 CET.

1. November 15, 2024 at 11:43 AM UTCinvestigating

   We are currently investigating this issue.

2. November 15, 2024 at 11:49 AM UTCresolved

   This incident has been resolved.

3. November 15, 2024 at 11:50 AM UTCpostmortem

   The root cause of this issue was an unanticipated spike in traffic that exceeded our database's current capacity. While our systems are designed to scale dynamically, the load exceeded thresholds we had not optimized for, exposing areas in need of improvement.

1. October 11, 2024 at 10:45 AM UTCinvestigating

   We are currently investigating this issue.

2. October 11, 2024 at 11:28 AM UTCresolved

   One of our server experienced software problem and needed an attention of our hosting provider. prisma CLOUD was not available starting from ca. 12:00 CEST till 13:04 CEST.

1. October 8, 2024 at 11:10 AM UTCresolved

   Between 22:30 and 23:30 our services were affected due to a firewall malfunction at out infrastructure provider.

1. June 18, 2024 at 8:16 AM UTCinvestigating

   Starting 09:45 CEST, we are facing a downtime due to an outage at our infrastructure provider. The team is working on it. We will post the next update soon.

2. June 18, 2024 at 8:18 AM UTCidentified

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

3. June 18, 2024 at 9:12 AM UTCmonitoring

   Our infrastructure provider has applied the fix. The services are now operational. We will continue to monitor our services.

4. June 18, 2024 at 11:14 AM UTCresolved

   This incident has been resolved.

1. January 10, 2024 at 3:28 PM UTCresolved

   We updated our auth component and kept the old API tokens valid until the end of Mar 2024. Some very old tokens may have failed the auth. It was fully resolved.

1. January 10, 2024 at 3:20 PM UTCresolved

   A temporary slow-down since the prisma CLOUD service now provides the device configuration via external API. For this reason, we had to make the full re-calculation of our config records (just once). We increased the number of calculators to keep the normal speed. Fully resolved by now.

1. October 10, 2023 at 6:35 AM UTCidentified

   Starting 5:15 UTC our infrastructure provider has reported problems with services. We have identified the issue and are on it.

2. October 10, 2023 at 7:31 AM UTCresolved

   This incident has been resolved.

1. September 16, 2023 at 7:54 AM UTCresolved

   It was temporary impossible to create reports. The issue was fixed 15.09.2023 at 05:02 UTC.

1. August 29, 2023 at 12:02 PM UTCresolved

   From 22:09, Aug 28 to 06:51, Aug 29 UTC, the data was being processed with a delay, which resulted as temporary inability to create reports. The problem was caught and fixed first thing in the UTC morning. Please accept our apologies for any inconvenience it might have caused.

1. December 21, 2022 at 1:06 PM UTCinvestigating

   Due to connectivity issues from our GSM provider, some devices fail to communicate. We are investigating the cause

2. December 21, 2022 at 1:45 PM UTCresolved

   This incident has been resolved.

1. July 19, 2022 at 1:07 PM UTCidentified

   Our Infrastructure provider is facing system issues. We are working on it

2. July 19, 2022 at 3:50 PM UTCmonitoring

   A fix has been implemented, We are monitoring the results

3. July 19, 2022 at 3:51 PM UTCmonitoring

   Our infrastructure provider informed us, that the issue is resolved. We are continuing to monitor the system for any further issues.

4. July 19, 2022 at 5:12 PM UTCresolved

   This incidence has been resolved