Prisma Cloud outage history

We are currently experiencing a login issue in prisma CLOUD. Two-factor authentication (2FA) is not working due to an issue with our authentication provider. We are investigating the problem and working to restore normal login functionality as soon as possible.

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

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

This incident has been resolved.

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.

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.

We are currently investigating this issue.

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

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

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.

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

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

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

This incident has been resolved.

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.

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.

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

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.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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

This incident has been resolved.

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.

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

We are currently investigating this issue.

This incident has been resolved.

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.

We are currently investigating this issue.

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.

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

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.

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

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

This incident has been resolved.

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.

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.

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

This incident has been resolved.

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

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.

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

This incident has been resolved.

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

A fix has been implemented, We are monitoring the results

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

This incidence has been resolved