You've been redirected to our secondary SASE Trust Center because the primary site is currently undergoing maintenance.
All trust and service availability data displayed here is identical to the primary trust center.
⚠️ Important: Subscription and notification management is temporarily unavailable on this page.
Status: Investigating
Severity: Disruption
Locations: Andorra la Vella, Ashburn, Astana, Athens, Auckland, Bangkok, Barcelona, Bratislava, Brisbane, Bucharest, Budapest, Calgary, ChangHua, Chennai, Chicago, Chisinau, Colombo, Copenhagen, Dallas, Denver, Dhaka, Dublin, Eemshaven, Frankfurt, Guadalajara, Guatemala City, Hamburg, Hamina, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Istanbul, Jakarta, Karachi, Kiev, Kuala Lumpur, Lahore, Lisbon, Ljubljana, London, Los Angeles, Luxembourg City, Madrid, Marseille, Melbourne, Mexico City, Miami, Milan, Minsk, Monaco, Moncks Corner, Monterrey, Moscow, Mumbai, Munich, New Delhi, New York City, Osaka, Oslo, Panama City, Paris, Perth, Phnom Penh, Phoenix, Port Moresby, Prague, Quebec, Quezon City, Riga, Rotterdam, Saint Petersburg, Salt Lake City, San Francisco, San Jose, Schaan, Seoul, Singapore, Sofia, St. Ghislain, Stockholm, Sydney, Tashkent, The Dalles, Tokyo, Toronto, Vienna, Vilnius, Warsaw, Yangon, Zagreb, Zurich
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:
Option 1: Technical Workaround (Recommended for immediate stability) Apply the following
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.
An incident has been identified. We are actively investigating to restore services.