Prisma Cloud Outage History

Prisma Cloud is up right now

Prisma Cloud had 2 outages in the last 2 years totaling 1h 43m of downtime — averaging 0.1 incidents per month.

There were 2 Prisma Cloud outages since January 28, 2026 totaling 1h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.prismacloud.com

Critical April 14, 2026

prisma CLOUD is unavailable

Detected by Pingoru
Apr 14, 2026, 06:36 AM UTC
Resolved
Apr 14, 2026, 07:17 AM UTC
Duration
40m
Affected: prisma CLOUD websiteAPISFTPprisma APP
Timeline · 4 updates
  1. investigating Apr 14, 2026, 06:36 AM UTC

    We are currently investigating this issue.

  2. identified Apr 14, 2026, 06:42 AM UTC

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

  3. monitoring Apr 14, 2026, 06:51 AM UTC

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

  4. resolved Apr 14, 2026, 07:17 AM UTC

    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.

Read the full incident report →

Critical January 28, 2026

API availability problem

Detected by Pingoru
Jan 28, 2026, 04:44 PM UTC
Resolved
Jan 28, 2026, 05:46 PM UTC
Duration
1h 2m
Affected: API
Timeline · 4 updates
  1. investigating Jan 28, 2026, 04:44 PM UTC

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

  2. identified Jan 28, 2026, 04:44 PM UTC

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

  3. monitoring Jan 28, 2026, 05:16 PM UTC

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

  4. resolved Jan 28, 2026, 05:46 PM UTC

    This incident has been resolved.

Read the full incident report →