⚠️

SASE Status Page Consolidation

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.

View Full Documentation Contact Support
Prisma SASE Logo

New Onboarding, Autoscaling and Commit failures for Prisma Access (SP-317) : Prisma Access

Incident Report for Prisma SASE

Resolved

This incident has been resolved.
Posted Jan 13, 2026 - 08:10 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 08:06 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:53 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:43 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:34 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:23 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:13 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 07:05 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 06:54 UTC

Update

Update: Changes to Customer Impact.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 06:51 UTC

Monitoring

Update: Status changed to Monitoring.

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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We are continuing to monitor the situation.
Posted Jan 13, 2026 - 06:48 UTC

Identified

We are currently investigating an issue affecting Configuration

Status: Investigating
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: We have identified and resolved an issue affecting Auto-scale, New Onboarding, and Commit failures for Prisma Access customers. The fix has been deployed and verified in production.
Issue start time: Jan 13th 2025, 05:44 UTC
Issue fix time: Jan 13th 2025, 06:32 UTC

Please open a support case if you continue to experience any deployment or performance issues. 
Workaround: No work arounds at the moment.

We will provide updates as we learn more.
Posted Jan 13, 2026 - 06:46 UTC
This incident affected: Prisma Access (Configuration).
← Current Status Powered by Atlassian Statuspage