Potential impact to autoscaling and onboarding (SP-527) : Prisma Access Mobile Users

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.

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.