Histórico de interrupções do Prisma Cloud

1. 18 Eost 2026 da 12:41 UTCinvestigating

   Atualmente estamos experimentando um problema de login no prisma CLOUD. A autenticação de dois fatores (2FA) não está funcionando devido a um problema com nosso provedor de autenticação. Estamos investigando o problema e trabalhando para restaurar a funcionalidade de login normal o mais rápido possível.

2. 18 Eost 2026 da 13:56 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 18 Eost 2026 da 14:19 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 18 Eost 2026 da 18:10 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 09:21 UTCresolved

   prisma APP experimentou uma degradação temporária do desempenho. A questão foi investigada, foi identificada a causa raiz e implementadas ações corretivas. A degradação pode ter causado breves períodos de indisponibilidade de serviços para alguns usuários. O desempenho foi restaurado e o aplicativo está funcionando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gouere 2026 da 08:25 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. 14 Ebrel 2026 da 06:36 UTCinvestigating

   We are currently investigating this issue.

2. 14 Ebrel 2026 da 06:42 UTCidentified

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

3. 14 Ebrel 2026 da 06:51 UTCmonitoring

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

4. 14 Ebrel 2026 da 07:17 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. 28 Genver 2026 da 16:44 UTCinvestigating

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

2. 28 Genver 2026 da 16:44 UTCidentified

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

3. 28 Genver 2026 da 17:16 UTCmonitoring

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

4. 28 Genver 2026 da 17:46 UTCresolved

   This incident has been resolved.

1. 14 Ebrel 2025 da 06:39 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. 14 Ebrel 2025 da 08:54 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. 14 Ebrel 2025 da 09:33 UTCidentified

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

4. 14 Ebrel 2025 da 11:32 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. 14 Ebrel 2025 da 14:16 UTCmonitoring

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

6. 14 Ebrel 2025 da 16:46 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 14 Ebrel 2025 da 16:46 UTCresolved

   This incident has been resolved.

1. 8 Ebrel 2025 da 15:24 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. 8 Ebrel 2025 da 18:12 UTCmonitoring

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

3. 8 Ebrel 2025 da 18:36 UTCresolved

   This incident has been resolved.

1. 7 Ebrel 2025 da 10:05 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. 16 Du 2024 da 12:27 UTCresolved

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

1. 15 Du 2024 da 11:43 UTCinvestigating

   We are currently investigating this issue.

2. 15 Du 2024 da 11:49 UTCresolved

   This incident has been resolved.

3. 15 Du 2024 da 11:50 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. 11 Here 2024 da 10:45 UTCinvestigating

   We are currently investigating this issue.

2. 11 Here 2024 da 11:28 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. 8 Here 2024 da 11:10 UTCresolved

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

1. 18 Mezheven 2024 da 08:16 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. 18 Mezheven 2024 da 08:18 UTCidentified

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

3. 18 Mezheven 2024 da 09:12 UTCmonitoring

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

4. 18 Mezheven 2024 da 11:14 UTCresolved

   This incident has been resolved.

1. 10 Genver 2024 da 15:28 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. 10 Genver 2024 da 15:20 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. 10 Here 2023 da 06:35 UTCidentified

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

2. 10 Here 2023 da 07:31 UTCresolved

   This incident has been resolved.

1. 16 Gwengolo 2023 da 07:54 UTCresolved

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

1. 29 Eost 2023 da 12:02 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. 21 Kerzu 2022 da 13:06 UTCinvestigating

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

2. 21 Kerzu 2022 da 13:45 UTCresolved

   This incident has been resolved.

1. 19 Gouere 2022 da 13:07 UTCidentified

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

2. 19 Gouere 2022 da 15:50 UTCmonitoring

   A fix has been implemented, We are monitoring the results

3. 19 Gouere 2022 da 15:51 UTCmonitoring

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

4. 19 Gouere 2022 da 17:12 UTCresolved

   This incidence has been resolved