You've been redirected to our QA secondary SASE Health because the primary site is currently undergoing maintenance.
All service availability data displayed here is identical to the primary SASE QA Health.
⚠️ Important: Subscription and notification management for emails is temporarily unavailable on this page.
Update: Changes to Workaround
Status: Investigating
Severity: Degraded
Locations: Singapore, Sydney
Impact:
Our Engineering team has identified a bug impacting users on Global Protect Android Software Version 6.1.11 We have identified the Root Cause (RCA) and are currently working on a fix.
Current Status
Workaround:
Immediate Actions & Workarounds
For customers currently on version 6.1.11 who are experiencing issues, we recommend one of the following two paths:
configuration change to bypass the identified trigger:
Option 2: Version Rollback If the configuration change does not resolve your specific use case. Global Protect version 6.1.10 remains fully supported and available.
Next Steps
We apologize for the inconvenience and are working to resolve this as quickly as possible. If you require assistance with either workaround, please contact our technical support team.
Incident has been identified and investigation is starting
Update: Changes to Workaround
Status: Investigating
Severity: Degraded
Locations: Singapore, Sydney
Impact:
Our Engineering team has identified a bug impacting users on Global Protect Android Software Version 6.1.11 We have identified the Root Cause (RCA) and are currently working on a fix.
Workaround:
For customers currently on version 6.1.11 who are experiencing issues, we recommend one of the following two paths:
configuration change to bypass the identified trigger:
{}Option 2{}: Version Rollback If the configuration change does not resolve your specific use case. Global Protect version 6.1.10 remains fully supported and available.
We apologize for the inconvenience and are working to resolve this as quickly as possible. If you require assistance with either workaround, please contact our technical support team.
Incident has been identified and investigation is starting