Palo Alto Networks Cloud Services Status
Real-time updates of Palo Alto Networks Cloud Services issues and outages
Palo Alto Networks Cloud Services status is Under Maintenance
Palo Alto Networks Cloud Services AutoFocus
Palo Alto Networks Cloud Services Strata Logging Service
United States - Americas
Saudi Arabia
Palo Alto Networks Cloud Services Prisma Cloud
Americas - US - app2.prismacloud.io
China - app.prismacloud.cn
Active Incidents
There will be routine maintenance on August 27th, 2026, 12AM AST
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Recently Resolved Incidents
Prisma Cloud is currently experiencing an issue with Cloud Account Service. We are actively working on this issue and will provide another update once available with further details.
Customer Impact: Cloud Account Service services may be unavailable
Workaround: N/A
AutoFocus is currently experiencing an issue with infrastructure. We are actively working on resolving this issue and will provide another update.
Impact: Customers will not be able to access the AutoFocus application or API
Prisma Cloud is currently experiencing an issue in China. We are actively investigating this issue and will provide another update once available with further details.
Palo Alto Networks Cloud Services Outage Survival Guide
Palo Alto Networks Cloud Services Components
Palo Alto Networks Cloud Services AutoFocus
AutoFocus is currently experiencing an issue with infrastructure. We are actively working on resolving this issue and will provide another update.
Impact: Customers will not be able to access the AutoFocus application or API
Palo Alto Networks Cloud Services Cortex Gateway
Palo Alto Networks Cloud Services Cortex XDR
Australia
Canada
Germany
India
Japan
Netherlands - Europe
Switzerland
United Kingdom
United States - Americas
United States - Government
Poland
Taiwan
Singapore
Qatar
Israel
France
Saudi Arabia
Indonesia
Spain
Italy
Korea
South Africa
Palo Alto Networks Cloud Services Cortex XSIAM
Australia
Canada
Germany
India
Japan
Netherlands - Europe
Singapore
Switzerland
United Kingdom
United States - Americas
United States - Government
Poland
Taiwan
Qatar
Israel
France
Saudi Arabia
Indonesia
Spain
Italy
Korea
South Africa
Palo Alto Networks Cloud Services Cortex XSOAR 6.x
United States - East
United States - West
Canada
Germany
United Kingdom
Australia
Palo Alto Networks Cloud Services Cortex XSOAR 8.x
Australia
Canada
Germany
India
Japan
Netherlands - Europe
Singapore
Switzerland
United Kingdom
United States - Americas
United States - Government
Poland
Taiwan
Qatar
Israel
France
Saudi Arabia
Indonesia
Spain
Italy
Korea
South Africa
Palo Alto Networks Cloud Services Cortex XPANSE 2.x
Australia
Canada
Germany
India
Japan
Netherlands - Europe
Singapore
Switzerland
United Kingdom
United States - Americas
Poland
Taiwan
Qatar
FedRAMP Moderate
FedRAMP High
Israel
France
Saudi Arabia
Indonesia
Spain
Italy
Korea
South Africa
Palo Alto Networks Cloud Services Strata Logging Service
United States - Americas
Netherlands - Europe
United Kingdom
United States - Government
Australia
Canada
Switzerland
Germany
Spain
France
Indonesia
Israel
India
Italy
Japan
Korea
Poland
Qatar
Saudi Arabia
There will be routine maintenance on August 27th, 2026, 12AM AST
Singapore
Taiwan
China
Palo Alto Networks Cloud Services Data Security (SaaS Security API)
SaaS API - North America
SaaS API - Singapore
SaaS API - Frankfurt
SaaS API - India
SaaS API - Australia
SaaS API - London
SaaS API - Japan
FedRAMP Moderate IL2
Palo Alto Networks Cloud Services Data Security (SaaS Inline)
FedRAMP Moderate IL2
SaaS Inline - North America
FedRAMP High IL4
SaaS Inline - Singapore
SaaS Inline - Japan
SaaS Inline - Australia
SaaS Inline - London
SaaS Inline - Frankfurt
SaaS Inline - India
Palo Alto Networks Cloud Services Data Security (SSPM)
SSPM - North America
SSPM - Frankfurt
SSPM - Singapore
SSPM - India
SSPM - Australia
SSPM - London
SSPM - Japan
FedRAMP Moderate IL2
FedRAMP High IL4
Palo Alto Networks Cloud Services Data Security (Email DLP)
Email DLP - North America
Email DLP - Frankfurt
Email DLP - Singapore
Palo Alto Networks Cloud Services DLP
APAC (Mumbai) - Prisma SaaS
APAC (Singapore) - Prisma SaaS
APAC (Tokyo) - Prisma Access
Americas (Canada) - Prisma Access
Americas (US East) - Prisma Cloud
Americas (US West) - Prisma SaaS
EMEA (Frankfurt) - Prisma SaaS
EMEA (London) - Prisma SaaS
DLP (NGFW) APAC
DLP (NGFW) EU
DLP (NGFW) NAM
Prisma Access DLP
Palo Alto Networks Cloud Services Prisma Cloud
Americas - US - app.prismacloud.io
Americas - US - app2.prismacloud.io
Prisma Cloud is currently experiencing an issue with Cloud Account Service. We are actively working on this issue and will provide another update once available with further details.
Customer Impact: Cloud Account Service services may be unavailable
Workaround: N/A
Americas - US - app3.prismacloud.io
Americas - US - app4.prismacloud.io
Americas - US - app.gov.prismacloud.io
Americas - Canada - app.ca.prismacloud.io
Europe - app.eu.prismacloud.io
Europe - app2.eu.prismacloud.io
United Kingdom - UK - app.uk.prismacloud.io
France - FR - app.fr.prismacloud.io
China - app.prismacloud.cn
Prisma Cloud is currently experiencing an issue in China. We are actively investigating this issue and will provide another update once available with further details.
Asia Pacific - Singapore - app.sg.prismacloud.io
Asia Pacific - India - app.ind.prismacloud.io
Asia Pacific - Japan - app.jp.prismacloud.io
Asia Pacific - Australia - app.anz.prismacloud.io
Asia Pacific - Indonesia - app.id.prismacloud.io
Prisma Cloud Application Security
Prisma Cloud Data Security - Americas
Prisma Cloud Data Security - European Union
Palo Alto Networks Cloud Services Prisma Cloud Compute ( CWP )
Americas - US - app.prismacloud.io
Americas - US - app2.prismacloud.io
Americas - US - app3.prismacloud.io
Americas - US - app4.prismacloud.io
Americas - US - app.gov.prismacloud.io
Americas - Canada - app.ca.prismacloud.io
Europe - app.eu.prismacloud.io
Europe - app2.eu.prismacloud.io
Asia Pacific - Australia - app.anz.prismacloud.io
Asia Pacific - Singapore - app.sg.prismacloud.io
United Kingdom - UK - app.uk.prismacloud.io
Asia Pacific - Japan - app.jp.prismacloud.io
France - FR - app.fr.prismacloud.io
Asia Pacific - India - app.ind.prismacloud.io
Asia Pacific - Indonesia - app.id.prismacloud.io
Palo Alto Networks Cloud Services Prisma Access
Americas-Argentina
Visit Prisma Access Status - https://sase.status.paloaltonetworks.com
Palo Alto Networks Cloud Services Prisma Access - Insights
Americas-Bolivia
Americas-Brazil Central
Palo Alto Networks Cloud Services Hub
Americas-Brazil East
Palo Alto Networks Cloud Services Prisma Access Agent Manager
Palo Alto Networks Cloud Services Strata Cloud Manager
Palo Alto Networks Cloud Services Cloud Identity Engine
Americas-Brazil South
United States - Americas
Americas-Canada Central
Americas-Canada East
United States - Government
Netherlands - Europe
Americas-Canada West
Americas-Chile
United Kingdom
Singapore
Americas-Colombia
Canada
Americas-Costa Rica
Japan
Americas-Ecuador
Americas-Mexico Central
Australia
Americas-Mexico West
Germany
India
Americas-Panama
Americas-Paraguay
Switzerland
Americas-Peru
Spain
Americas-US Central
Italy
France
Americas-US East
Poland
Americas-US Northeast
China
Americas-US Northwest
Taiwan
Americas-US South
Qatar
Americas-US Southeast
Israel
Americas-US Southwest
Americas-US West
Indonesia
Americas-Venezuela
Saudi Arabia
APAC-Australia East
South Korea
FedRamp Moderate
APAC-Australia South
APAC-Australia Southeast
FedRamp High
APAC-Bangladesh
South Africa
APAC-Cambodia
Palo Alto Networks Cloud Services IoT/OT Security
APAC-Hong Kong
Australia
Canada
APAC-India North
APAC-India South
Germany
APAC-India West
Japan
APAC-Indonesia
Singapore
Switzerland
APAC-Japan Central
APAC-Japan South
United Kingdom
United States
APAC-Malaysia
United States - Government
APAC-Myanmar
Palo Alto Networks Cloud Services PAN-DB Cloud
APAC-New Zealand
APAC-Pakistan South
Americas - US East
Americas - US Central
APAC-Pakistan West
APAC-Papua New Guinea
Americas - US West
EMEA - Netherlands
APAC-Philippines
APAC-Singapore
APAC - Singapore
APAC-South Korea
APAC - Tokyo
APAC-Taiwan
Palo Alto Networks Cloud Services WildFire
APAC-Thailand
WildFire Global Cloud
APAC-Vietnam
WildFire Europe Cloud
WildFire Singapore Cloud
EMEA-Andorra
EMEA-Austria
WildFire Japan Cloud
EMEA-Belarus
WildFire UK Cloud
WildFire U.S. Government Cloud
EMEA-Belgium
WildFire Canada Cloud
EMEA-Bulgaria
EMEA-Croatia
WildFire Australia Cloud
EMEA-Czech Republic
WildFire Germany Cloud
WildFire India Cloud
EMEA-Denmark
WildFire Switzerland Cloud
EMEA-Finland
WildFire Poland Cloud
EMEA-France North
EMEA-France South
WildFire Indonesia Cloud
EMEA-Germany Central
WildFire Taiwan Cloud
EMEA-Germany North
WildFire France Cloud
WildFire Qatar Cloud
EMEA-Germany South
EMEA-Greece
WildFire South Korea Cloud
EMEA-Hungary
WildFire Israel Cloud
WildFire Saudi Arabia Cloud
EMEA-Ireland
EMEA-Italy
WildFire Italy Cloud
Wildfire Spain Cloud
EMEA-Liechtenstein
EMEA-Lithuania
WildFire AWF PubSec Cloud(FRM)
WildFire AWF GovCloud(FRH)
EMEA-Luxembourg
WildFire South Africa Cloud
EMEA-Moldova
EMEA-Monaco
WildFire EU Regulated Cloud
WildFire GVS Cloud
Europe Germany
EMEA-Netherlands Central
EMEA-Netherlands South
United States - AMERICAS
Palo Alto Networks Cloud Services Zero Touch Provisioning (ZTP) Service
Palo Alto Networks Cloud Services Strata Cloud Manager
Australia
EMEA-Norway
EMEA-Poland
Cloud Manager North America (United States)
Europe United Kingdom
Cloud Manager North America (Canada)
EMEA-Portugal
Singapore
Japan
EMEA-Romania
Cloud Manager Europe (United Kingdom)
Cloud Manager APAC (Japan)
EMEA-Russia Central
India
Cloud Manager APAC (India)
EMEA-Russia Northwest
EMEA-Slovakia
Cloud Manager APAC (Singapore)
Cloud Manager Europe (Switzerland)
EMEA-Slovenia
EMEA-Spain Central
Cloud Manager Europe (Germany)
Cloud Manager APAC (Australia)
EMEA-Spain East
Cloud Manager Middle East (Qatar)
EMEA-Sweden
EMEA-Switzerland
Cloud Manager Europe (France)
EMEA-UK
Cloud Manager APAC (Indonesia)
Cloud Manager Middle East (Israel)
EMEA-Ukraine
EMEA-Uzbekistan
Cloud Manager Middle East (Saudi Arabia)
Cloud Manager Africa (South Africa)
EMEA-Kenya
EMEA-Nigeria
Cloud Manager North America (FedRamp Moderate)
EMEA-South Africa Central
Cloud Manager North America (FedRamp High)
Palo Alto Networks Cloud Services EDL Hosting Service
EMEA-South Africa West
EMEA-Egypt
Palo Alto Networks Cloud Services Content Updates
EMEA-Israel
Content Updates (Dynamic)
EMEA-Jordan
Content Updates (Static)
Palo Alto Networks Cloud Services Okyo
EMEA-Kuwait
Cloudservice
EMEA-Saudi Arabia
EMEA-Turkey
Okyo site
EMEA-United Arab Emirates
Palo Alto Networks Cloud Services Cloud NGFW for AWS
Americas-Brazil South (Location on-boarded prior to version 1.4)
N.California(us-west-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Americas-Canada East (Location on-boarded prior to version 1.4)
N.Virginia(us-east-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Americas-US Central (Location on-boarded prior to version 1.4)
Ohio(us-east-2)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Oregon(us-west-2)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Americas-US East (Location on-boarded prior to version 1.4)
Canada(ca-central-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Americas-US Northwest (Location on-boarded prior to version 1.4)
Ireland(eu-west-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Americas-US West (Location on-boarded prior to version 1.4)
London(eu-west-2)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
APAC-Australia Southeast (Location on-boarded prior to version 1.4)
Paris(eu-west-3)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
APAC-India West (Location on-boarded prior to version 1.4)
Frankfurt(eu-central-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
APAC-Japan Central (Location on-boarded prior to version 1.4)
Stockholm(eu-north-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
APAC-Singapore (Location on-boarded prior to version 1.4)
Milan(eu-south-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
APAC-South Korea (Location on-boarded prior to version 1.4)
Singapore(ap-southeast-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
EMEA-France North (Location on-boarded prior to version 1.4)
EMEA-Germany Central (Location on-boarded prior to version 1.4)
Sydney(ap-southeast-2)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Tokyo(ap-northeast-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
EMEA-Ireland (Location on-boarded prior to version 1.4)
EMEA-UK (Location on-boarded prior to version 1.4)
Osaka(ap-northeast-3)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Bahrain(me-south-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Prisma Access - Autonomous DEM
Hong Kong(ap-east-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Africa(af-south-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Sao Paulo(sa-east-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Mumbai(ap-south-1)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
Seoul(ap-northeast-2)
We’ve identified a compatibility issue stemming from a recent AWS update to the boto3 library. This new boto3 version is incompatible with the older botocore version currently used in our deployments. Customer Impact There’s no impact on ongoing traffic, and all backend Cloud NGFW instances remain healthy. However, you might observe an incorrect status display in the UI related to two specific scenarios: When adding a new Availability Zone (AZ), the firewall status might incorrectly show “UPDATING” in the UI. The firewall status might incorrectly show “CREATING” in the UI. Please note, this issue is affecting less than 10% of our total firewalls. We’re actively working to resolve this and will provide another update as soon as we have more information.
