Prisma Access Status

Identified: We are currently investigating an issue affecting Configuration

Status: Investigating Severity: Degraded Affected Locations: San Francisco Customer Impact: Remote Browser Isolation team will be performing a scheduled maintenance on the infrastructure. Customers using RBI service might witness intermittent performance degradation during this maintenance window.

When: Friday 30th January, from 10 PM ISTto 00:00 IST. Workaround: Rollback to the previous version

We will provide updates as we learn more.

Resolved: The issue has been resolved. These systems should now be operating normally.

If you continue to experience any issues, please submit a ticket to our support team.

Monitoring: Service has reported a partial recovery and is working toward full restoration.

We are actively monitoring the environment as the rollout continues.

Identified: We are currently observing service degradation affecting instances in the us-south region, which may also impact onboarding and autoscaling. A workaround has been implemented, and we are working with the cloud provider on resolution.

Identified: Update: Changes to Customer Impact.

Status: Investigating Severity: Degraded Affected Locations: Dallas Customer Impact: Time: February 25, 2026 at 4:38:00 AM UTC We are currently investigating a cloud networking issue that is affecting a small, specific set of tenants in US-South.

Key Details & Impact Affected Components: The issue impacts traffic originating and egressing out of US-South 

Dataplane Impact: We are observing increased packet loss leading to IPSec tunnel and networking failures starting February 25, 2026 at 4:38:00 AM UTC

Please reconnect to nearest location if you continue to experiencing connectivity issues  Workaround: GP/PAA Users should reconnect to nearest locations

We will provide updates as we learn more.

Identified: We are actively working with our cloud provider to implement a fix; please open a support case if you are experiencing any issues in the US South.

Identified: We are currently investigating an issue affecting Configuration

Status: Investigating Severity: Degraded Affected Locations: Dallas Customer Impact: Time: February 25, 2026 at 4:38:00 AM UTC We are currently investigating a cloud networking issue that is affecting a small, specific set of tenants in US-South.

Key Details & Impact Affected Components: The issue impacts traffic originating and egressing out of US-South 

Dataplane Impact: We are observing increased packet loss leading to IPSec tunnel and networking failures starting February 25, 2026 at 4:38:00 AM UTC

  Workaround: GP/PAA Users should reconnect to nearest locations

We will provide updates as we learn more.

Resolved: Update: Status changed to Resolved.

Status: Resolved Severity: Disruption Affected Locations: Bern, Rome, Warsaw Customer Impact: SCM users in multiple regions are unable to login portal due to a 403 error. We are investigating the issue . 

THe issue has been resolved now . 

Thank you for your patience.

Monitoring: Update: Changes to Continent, Edge Location, Customer Impact.

Status: Monitoring Severity: Disruption Affected Locations: Bern, Rome, Warsaw Customer Impact: SCM users in multiple regions are unable to login portal due to a 403 error. We are investigating the issue . 

THe issue has been resolved now . 

We are continuing to monitor the situation.

Monitoring: Update: Status changed to Monitoring.

Status: Monitoring Severity: Disruption Affected Locations: Riyadh Customer Impact: SCM users in multiple regions are unable to login portal due to a 403 error. We are investigating the issue . 

We are continuing to monitor the situation.

Identified: Update: Changes to Edge Location.

Status: Investigating Severity: Disruption Affected Locations: Riyadh Customer Impact: SCM users in multiple regions are unable to login portal due to a 403 error. We are investigating the issue . 

We will provide updates as we learn more.

Identified: We are currently investigating an issue affecting Cloud Manager

Status: Investigating Severity: Disruption Affected Locations: Seoul Customer Impact: SCM users in multiple regions are unable to login portal due to a 403 error. We are investigating the issue . 

We will provide updates as we learn more.

Resolved: Update: Status changed to Resolved.

Status: Resolved Severity: Degraded Affected Locations: Columbus, Ohio, Oregon Customer Impact: Prisma Access SDWAN customers will get alerts that stats and flows were disconnected for their devices. No impact to the data plane. Workaround: No workaround.

Thank you for your patience.

Monitoring: Update: Status changed to Monitoring.

Status: Monitoring Severity: Degraded Affected Locations: Columbus, Ohio, Oregon Customer Impact: Prisma Access SDWAN customers will get alerts that stats and flows were disconnected for their devices. No impact to the data plane. Workaround: No workaround.

We are continuing to monitor the situation.

Identified: We are currently investigating an issue affecting Device Status, Metrics & Stats

Status: Investigating Severity: Degraded Affected Locations: Columbus, Ohio, Oregon Customer Impact: Prisma Access SDWAN customers will get alerts that stats and flows were disconnected for their devices. No impact to the data plane. Workaround: No workaround.

We will provide updates as we learn more.

Resolved: Update: Status changed to Resolved.

Status: Resolved Severity: Degraded Affected Locations: Adelaide, Almaty, Auckland, Bangkok, Beijing, Chennai, Colombo, Dhaka, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Manila, Mumbai, Ningxia, Osaka, Perth, Phnom Penh, Port Moresby, Seoul, Singapore, Sydney, Taipei, Tashkent, Tokyo, Yangon Customer Impact: On February 23, 2026, we identified a brief period of instability involving one of our underlying infrastructure provider that impacted our autoscaling services. While the incident lasted approximately 74 minutes, we want to emphasize that overall system impact was minimal. Our monitoring indicates that the vast majority of users experienced no disruption. A very small subset of customers may have encountered slight latency or temporary errors during peak scaling events.

Timeline (UTC) 07:30 PM: Potential scaling delays first identified via automated monitoring.

07:45 PM: Issue traced to a downstream degradation with our infrastructure provider.

08:15 PM: Provider confirmed a fix was in progress; our team monitored internal systems for any spillover effects.

08:44 PM: Provider confirmed full resolution. All autoscaling services returned to nominal performance levels. Workaround: No work around at this time.

Thank you for your patience.

Monitoring: We are currently investigating an issue affecting Prisma Access Mobile Users

Status: Monitoring Severity: Degraded Affected Locations: Adelaide, Almaty, Auckland, Bangkok, Beijing, Chennai, Colombo, Dhaka, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Manila, Mumbai, Ningxia, Osaka, Perth, Phnom Penh, Port Moresby, Seoul, Singapore, Sydney, Taipei, Tashkent, Tokyo, Yangon Customer Impact: On February 23, 2026, we identified a brief period of instability involving one of our underlying infrastructure provider that impacted our autoscaling services. While the incident lasted approximately 74 minutes, we want to emphasize that overall system impact was minimal. Our monitoring indicates that the vast majority of users experienced no disruption. A very small subset of customers may have encountered slight latency or temporary errors during peak scaling events.

Timeline (UTC) 07:30 PM: Potential scaling delays first identified via automated monitoring.

07:45 PM: Issue traced to a downstream degradation with our infrastructure provider.

08:15 PM: Provider confirmed a fix was in progress; our team monitored internal systems for any spillover effects.

08:44 PM: Provider confirmed full resolution. All autoscaling services returned to nominal performance levels. Workaround: No work around at this time.

We are continuing to monitor the situation.