⚠️

QA SASE Status Page Consolidation

We have consolidated our QA SASE status page components for improved clarity and better service visibility. All changes, migration details, and component mappings are thoroughly documented for your reference.

The most up-to-date list of products is displayed below. Regional impact details and workarounds will be included in incident descriptions when applicable.

View Full Documentation Contact Support

Prisma Access : Feb 16 - Test 3

Incident Report for NON PROD SASE STATUS PAGE

Resolved

Status: Resolved
Severity: Disruption
Locations: Ashburn
Impact: Test 1
Workaround: Test 1

Incident has been fully resolved, test it out

Posted Feb 17, 2026 - 02:47 UTC

Update

Update: Changes to Severity, Locations

Status: Monitoring
Severity: Disruption
Locations: Ashburn
Impact: Test 1
Workaround: Test 1

Active monitoring of resolution in progress

Posted Feb 17, 2026 - 02:45 UTC

Monitoring

Status: Monitoring
Severity: Degraded
Locations: Ashburn, Chennai, Columbus, Ohio, Dublin, Frankfurt, Hamburg, London, Mexico City, Montreal, Mumbai, Oregon, Paris, San Francisco, San Jose, Seoul, Singapore, Sydney, Tokyo
Impact: Test 1
Workaround: Test 1

Active monitoring of resolution in progress

Posted Feb 17, 2026 - 02:42 UTC

Investigating

Status: Investigating
Severity: Degraded
Locations: Ashburn, Chennai, Columbus, Ohio, Dublin, Frankfurt, Hamburg, London, Mexico City, Montreal, Mumbai, Oregon, Paris, San Francisco, San Jose, Seoul, Singapore, Sydney, Tokyo
Impact: Test 1
Workaround: Test 1

Incident has been identified and investigation is starting

Posted Feb 17, 2026 - 02:37 UTC

This incident affected: Prisma Access (Configuration).