We have consolidated our 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.
Status: Resolved Severity: Degraded Affected Locations: Ashburn, Atlanta, Calgary, Chicago, Columbus, Ohio, Council Bluffs, Dallas, Guadalajara, Guatemala City, Los Angeles, Mexico City, Miami, Monterrey, Montreal, New York, Oregon, Panama City, Phoenix, San Francisco, San Jose, Toronto Customer Impact: Some mobile users may experience unstable Prisma Access connectivity due to autoscaling failures.
Customers may potentially see an impact during new Prisma Access onboarding.
Dataplane traffic across existing instances is *not* affected. Workaround: There are currently no workarounds
Thank you for your patience.
Posted Feb 11, 2026 - 16:11 UTC
Monitoring
Update: Status changed to Monitoring.
Status: Monitoring Severity: Degraded Affected Locations: Ashburn, Atlanta, Calgary, Chicago, Columbus, Ohio, Council Bluffs, Dallas, Guadalajara, Guatemala City, Los Angeles, Mexico City, Miami, Monterrey, Montreal, New York, Oregon, Panama City, Phoenix, San Francisco, San Jose, Toronto Customer Impact: Some mobile users may experience unstable Prisma Access connectivity due to autoscaling failures.
Customers may potentially see an impact during new Prisma Access onboarding.
Dataplane traffic across existing instances is *not* affected. Workaround: There are currently no workarounds
We are continuing to monitor the situation.
Posted Feb 10, 2026 - 22:58 UTC
Update
We are continuing to work on a fix for this issue.
Posted Feb 10, 2026 - 22:56 UTC
Update
Update: Changes to Product Type.
Status: Investigating Severity: Degraded Affected Locations: Ashburn, Atlanta, Calgary, Chicago, Columbus, Ohio, Council Bluffs, Dallas, Guadalajara, Guatemala City, Los Angeles, Mexico City, Miami, Monterrey, Montreal, New York, Oregon, Panama City, Phoenix, San Francisco, San Jose, Toronto Customer Impact: Some mobile users may experience unstable Prisma Access connectivity due to autoscaling failures.
Customers may potentially see an impact during new Prisma Access onboarding.
Dataplane traffic across existing instances is *not* affected. Workaround: There are currently no workarounds
We will provide updates as we learn more.
Posted Feb 10, 2026 - 22:54 UTC
Identified
We are currently investigating an issue affecting Prisma Access
Status: Investigating Severity: Degraded Affected Locations: Ashburn, Atlanta, Calgary, Chicago, Columbus, Ohio, Council Bluffs, Dallas, Guadalajara, Guatemala City, Los Angeles, Mexico City, Miami, Monterrey, Montreal, New York, Oregon, Panama City, Phoenix, San Francisco, San Jose, Toronto Customer Impact: Some mobile users may experience unstable Prisma Access connectivity due to autoscaling failures.
Customers may potentially see an impact during new Prisma Access onboarding.
Dataplane traffic across existing instances is *not* affected. Workaround: There are currently no workarounds
We will provide updates as we learn more.
Posted Feb 10, 2026 - 22:41 UTC
This incident affected: Prisma Access (Configuration).