Status: Monitoring
Severity: Degraded
Locations: Jeddah, Jerusalem, Riyadh
Impact:
SCM Notifications Impact september 8th
Workaround:
SCM Notifications Workaround september 8th
A fix has been implemented. We are actively monitoring to ensure full restoration of services - state change monitoring
Sep 08, 2026 - 22:16 UTC
Status: Investigating
Severity: Degraded
Locations: Jeddah, Jerusalem, Riyadh
Impact:
SCM Notifications Impact september 8th
Workaround:
SCM Notifications Workaround september 8th
An incident has been identified. We are actively investigating to restore services - first comment
Sep 08, 2026 - 22:09 UTC
Status: Investigating
Severity: Degraded
Locations: Calgary, Quebec, San Jose
Impact:
No Impact
Workaround:
NO workaround
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 22:16 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 13:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:14 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 12:04 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:14 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 11:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:44 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 10:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:14 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 09:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:24 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 08:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 07:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:44 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 06:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:24 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:14 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 05:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 04:04 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 03:04 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:53 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:44 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 02:04 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:44 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 01:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:24 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 24, 2026 - 00:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:34 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:17 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 23:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:54 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:43 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:33 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:23 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:15 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:10 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:09 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:03 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:03 UTC
Status: Investigating
Severity: Degraded
Locations: Andorra la Vella, St. Ghislain, Vienna
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:02 UTC
Status: Investigating
Severity: Degraded
Locations: Oregon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 21:19 UTC
Status: Monitoring
Severity: Degraded
Locations: The Dalles
Impact:
Cusotmer Impact Test
Workaround:
Customer Workaround
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Aug 28, 2026 - 21:19 UTC
Status: Monitoring
Severity: Degraded
Locations: The Dalles
Impact:
Cusotmer Impact Test
Workaround:
Customer Workaround
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Aug 28, 2026 - 20:58 UTC
Status: Investigating
Severity: Degraded
Locations: Oregon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 20:58 UTC
Status: Investigating
Severity: Degraded
Locations: Oregon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 20:47 UTC
Status: Monitoring
Severity: Degraded
Locations: The Dalles
Impact:
Cusotmer Impact Test
Workaround:
Customer Workaround
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Aug 28, 2026 - 20:38 UTC
Status: Investigating
Severity: Degraded
Locations: The Dalles
Impact:
Cusotmer Impact Test
Workaround:
Customer Workaround
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 20:27 UTC
Update: Changes to Tenant_Ids
Status: Investigating
Severity: Disruption
Locations: Oregon
Impact:
dad
Workaround:
dad
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 10:07 UTC
Status: Investigating
Severity: Disruption
Locations: Oregon
Impact:
dad
Workaround:
dad
An incident has been identified. We are actively investigating to restore services.
Aug 28, 2026 - 10:05 UTC
Severity: Degraded
Locations: Dublin, London, Ohio, Oregon, Singapore, Sydney, Virginia
Impact: No Impact, test ticket
Workaround: No workaround
Incident is published only for demo testing
Feb 20, 2026 - 00:09 UTC
Severity: Degraded
Locations: Global
Impact: No Impact, test ticket
Workaround: No workaround
Incident is published only for demo testing
Feb 20, 2026 - 00:07 UTC
Severity: Degraded
Locations: Global
Impact: No Impact, test ticket
Workaround: No workaround
Incident is published only for demo testing
Feb 19, 2026 - 23:48 UTC
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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
Mar 04, 2026 - 23:25 UTC
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*
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by {}next week{}.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
{}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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
- Next Steps*
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal
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
Mar 04, 2026 - 23:12 UTC
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*
* *Rollout Halted:* We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
* *Resolution Timeline:* Engineering is working on the fix. A new, corrected image is expected to be released by {*}next week{*}.
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:
# Edit the GlobalProtect app configuration in your MDM.
# Click on Add Configuration Setting.
# Select the *Induce FIPS error* configuration key and add the following details:
# Value type: String
# Value: default
{*}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.
# Uninstall version 6.1.11.
# Reinstall version 6.1.10 from the App Store.
*Next Steps*
* *Monitoring:* Our support team is monitoring all active 6.1.11 environments.
* *Notification:* You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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
Mar 04, 2026 - 21:52 UTC
Status: Monitoring
Severity: Degraded
Locations: Berlin, Warsaw
Impact:
a
Workaround:
a
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 12, 2026 - 13:06 UTC
Status: Investigating
Severity: Degraded
Locations: Berlin, Warsaw
Impact:
a
Workaround:
a
An incident has been identified. We are actively investigating to restore services.
Mar 12, 2026 - 07:10 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 12, 2026 - 07:13 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn, The Dalles
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 12, 2026 - 07:41 UTC
Status: Monitoring
Severity: Degraded
Locations: Ashburn, Frankfurt
Impact:
Test Incident for checking ui status
Test Incident for checking ui status{}{}
Test Incident for checking ui status{}{}
Test Incident for checking ui status{}{}
Workaround:
Test Incident for checking ui status
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 15, 2026 - 07:40 UTC
Update: Changes to Impact
Status: Investigating
Severity: Degraded
Locations: Ashburn, Frankfurt
Impact:
Test Incident for checking ui status
Test Incident for checking ui status{}{}
Test Incident for checking ui status{}{}
Test Incident for checking ui status{}{}
Workaround:
Test Incident for checking ui status
An incident has been identified. We are actively investigating to restore services.
Mar 15, 2026 - 07:30 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn, Frankfurt
Impact:
Test Incident for checking ui status
Workaround:
Test Incident for checking ui status
An incident has been identified. We are actively investigating to restore services.
Mar 13, 2026 - 19:14 UTC
Status: Monitoring
Severity: Disruption
Locations: Oregon
Impact:
test
Workaround:
test
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 13, 2026 - 20:58 UTC
Status: Monitoring
Severity: Degraded
Locations: Doha
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 16, 2026 - 06:42 UTC
Status: Investigating
Severity: Degraded
Locations: Doha
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 16, 2026 - 06:37 UTC
Status: Monitoring
Severity: Degraded
Locations: Johannesburg
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 16, 2026 - 07:35 UTC
Status: Investigating
Severity: Degraded
Locations: Johannesburg
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 16, 2026 - 07:34 UTC
Status: Investigating
Severity: Degraded
Locations: Doha, Hong Kong, Jakarta, Johannesburg, Mumbai, Riyadh, Seoul, Singapore, Sydney, São Paulo, Taipei, Tel Aviv, Tokyo
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 16, 2026 - 07:39 UTC
Update: Changes to Locations
Status: Investigating
Severity: Degraded
Locations: Ashburn, Astana, Auckland, Bangkok, Brisbane, Calgary, ChangHua, Chennai, Chicago, Colombo, Dallas, Denver, Dhaka, Guadalajara, Guatemala City, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Los Angeles, Melbourne, Mexico City, Miami, Moncks Corner, Monterrey, Mumbai, New Delhi, New York City, Osaka, Panama City, Perth, Phnom Penh, Phoenix, Port Moresby, Quebec, Quezon City, Salt Lake City, San Francisco, San Jose, Seoul, Singapore, Sydney, Tashkent, The Dalles, Tokyo, Toronto, Yangon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 17, 2026 - 05:50 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn, Astana, Auckland, Bangkok, Brisbane, Calgary, ChangHua, Chennai, Chicago, Colombo, Dallas, Denver, Dhaka, Guadalajara, Guatemala City, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Los Angeles, Melbourne, Mexico City, Miami, Moncks Corner, Monterrey, Mumbai, New Delhi, New York City, Osaka, Panama City, Perth, Phnom Penh, Phoenix, Port Moresby, Quebec, Quezon City, Salt Lake City, San Francisco, San Jose, Seoul, Singapore, Sydney, Tashkent, The Dalles, Tokyo, Toronto, Yangon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 17, 2026 - 05:34 UTC
Update: Changes to Severity
Status: Investigating
Severity: Disruption
Locations: Ashburn, Astana, Auckland, Bangkok, Brisbane, Calgary, ChangHua, Chennai, Chicago, Colombo, Dallas, Denver, Dhaka, Guadalajara, Guatemala City, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Los Angeles, Melbourne, Mexico City, Miami, Moncks Corner, Monterrey, Mumbai, New Delhi, New York City, Osaka, Panama City, Perth, Phnom Penh, Phoenix, Port Moresby, Quebec, Quezon City, Salt Lake City, San Francisco, San Jose, Seoul, Singapore, Sydney, Tashkent, The Dalles, Tokyo, Toronto, Yangon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 17, 2026 - 05:56 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn, Astana, Auckland, Bangkok, Brisbane, Calgary, ChangHua, Chennai, Chicago, Colombo, Dallas, Denver, Dhaka, Guadalajara, Guatemala City, Ho Chi Minh City, Hong Kong, Hyderabad, Islamabad, Jakarta, Karachi, Kuala Lumpur, Lahore, Los Angeles, Melbourne, Mexico City, Miami, Moncks Corner, Monterrey, Mumbai, New Delhi, New York City, Osaka, Panama City, Perth, Phnom Penh, Phoenix, Port Moresby, Quebec, Quezon City, Salt Lake City, San Francisco, San Jose, Seoul, Singapore, Sydney, Tashkent, The Dalles, Tokyo, Toronto, Yangon
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 17, 2026 - 05:51 UTC
Status: Monitoring
Severity: Degraded
Locations: Madrid
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Mar 24, 2026 - 23:56 UTC
Update: Changes to Severity
Status: Investigating
Severity: Degraded
Locations: Madrid
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 18, 2026 - 23:13 UTC
Update: Changes to Locations
Status: Investigating
Severity: Disruption
Locations: Madrid
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 18, 2026 - 23:09 UTC
Status: Investigating
Severity: Disruption
Locations: Global
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 18, 2026 - 23:07 UTC
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
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:
- Edit the GlobalProtect app configuration in your MDM.
- Click on Add Configuration Setting.
- Select the Induce FIPS error configuration key and add the following details:
- Value type: String
- Value: default
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.
- Uninstall version 6.1.11.
- Reinstall version 6.1.10 from the App Store.
Next Steps
- Monitoring: Our support team is monitoring all active 6.1.11 environments.
- Notification: You will receive a follow-up notification as soon as the fixed image is available in the customer portal.
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.
Mar 18, 2026 - 23:09 UTC
Status: Investigating
Severity: Degraded
Locations: Montreal, Toronto
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 19, 2026 - 02:20 UTC
Status: Investigating
Severity: Disruption
Locations: Frankfurt, London, Madrid, Paris, Warsaw
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 23, 2026 - 22:03 UTC
Status: Investigating
Severity: Disruption
Locations: Los Angeles
Impact:
Unable to push website block policy via admin agent
Workaround:
Configure via management portal
An incident has been identified. We are actively investigating to restore services.
Mar 25, 2026 - 19:42 UTC
Status: Monitoring
Severity: Degraded
Locations: Ashburn, Virginia
Impact:
test
Workaround:
test
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
Apr 01, 2026 - 00:19 UTC
Status: Investigating
Severity: Degraded
Locations: Ashburn, Virginia
Impact:
test
Workaround:
test
An incident has been identified. We are actively investigating to restore services.
Mar 31, 2026 - 23:48 UTC
Scheduled Maintenance
Scheduled Maintenance : Prisma SDWAN Fedramp Mod Mar 16, 2026 06:25 - Oct 16, 2026 05:16 UTC
Status: Scheduled
Scheduled Window: March 15, 2026, 23:25 - October 15, 2026, 22:16 (America/Los_Angeles)
Locations: California
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
We will provide updates when maintenance begins.
Posted on Mar 16, 2026 - 06:08 UTC
Scheduled Maintenance : Strata Cloud Manager Mar 16, 2026 11:05-12:16 UTC
Update: Changes to Scheduled End.
Status: Scheduled
Scheduled Window: March 16, 2026, 11:05 - 12:16 (UTC)
Locations: Hong Kong, Seoul, Tokyo
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
You can track service status, maintenance-related updates, and sign up for notifications at:
https://sase.status.paloaltonetworks.com/
If you have any questions, please open a case at: https://support.paloaltonetworks.com/
Mar 16, 2026 - 06:13 UTC
Status: Scheduled
Scheduled Window: March 16, 2026, 11:05 - October 15, 2026, 22:16 (UTC)
Locations: Hong Kong, Seoul, Tokyo
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
- Rollout Halted: We have officially paused the rollout of version 6.1.11. No additional users or systems will be upgraded to this version until the fix is released.
- Resolution Timeline: Engineering is working on the fix. A new, corrected image is expected to be released by next week.
We will provide updates when maintenance begins.
Mar 16, 2026 - 06:08 UTC
Scheduled Maintenance : Next-Gen Trust Security (NGTS) Mar 16, 2026 22:25 - Mar 17, 2026 23:20 UTC
Status: Scheduled
Scheduled Window: March 16, 2026, 22:25 - March 17, 2026, 23:20 (Europe/London)
Locations: Ashburn, Frankfurt
Impact:
Test Incident for notification
We will provide updates when maintenance begins.
Posted on Mar 16, 2026 - 03:20 UTC
Scheduled Maintenance : Prisma Access Apr 3, 2026 21:35 - May 3, 2026 21:35 UTC
Scheduled Window: April 03, 2026, 14:35 - May 03, 2026, 14:35 (America/Los_Angeles)
Locations: Ashburn, New York City, The Dalles
Impact: Test future maintenance
We will provide updates when maintenance begins.
Posted on Mar 03, 2026 - 22:38 UTC
Scheduled Maintenance : HUB Apr 22, 2026 19:45 - Jul 8, 2026 19:44 UTC
Scheduled Window: April 22, 2026, 12:45 - July 08, 2026, 12:44 (America/Los_Angeles)
Locations: Council Bluffs, Toronto
Impact: Testing
We will provide updates when maintenance begins.
Posted on Feb 27, 2026 - 23:42 UTC