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: A work around has been rolled out and we are able to confirm successful autoscaling. We are continuing to monitor the health of the infrastructure very closely for any other symptoms. We appreciate your patience. Workaround: No work arounds at the moment.
Thank you for your patience.
Posted Feb 27, 2026 - 23:31 UTC
Update
Update: Changes to Customer Impact.
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: A work around has been rolled out and we are able to confirm successful autoscaling. We are continuing to monitor the health of the infrastructure very closely for any other symptoms. We appreciate your patience. Workaround: No work arounds at the moment.
We are continuing to monitor the situation.
Posted Feb 27, 2026 - 16:14 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: A work around has been rolled out and we are able to confirm successful autoscale. We are continuing to monitor the health of the infrastructure very closely for any other symptoms. We appreciate your patience. Workaround: No work arounds at the moment.
We are continuing to monitor the situation.
Posted Feb 27, 2026 - 16:12 UTC
Update
Update: Changes to Title.
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 Workaround: No work arounds at the moment.
We will provide updates as we learn more.
Posted Feb 27, 2026 - 15:06 UTC
Identified
We are currently investigating an issue affecting Configuration
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 Workaround: No work arounds at the moment.
We will provide updates as we learn more.
Posted Feb 27, 2026 - 15:04 UTC
This incident affected: Prisma Access (Configuration).