- Detected by Pingoru
- Mar 10, 2026, 12:41 PM UTC
- Resolved
- Mar 10, 2026, 10:47 PM UTC
- Duration
- 10h 6m
Affected: australiaeastaustraliasoutheastcanadacentralcentraluseastasiaeastuseastus2northeuropeuksouthukwestwesteuropewestuswestus2westus3brazilsouthjapaneastnorthcentralussoutheastasiacanadaeastcentralindiafrancecentralgermanywestcentralisraelcentralitalynorthjapanwestkoreacentralmexicocentralnewzealandnorthnorwayeastsouthafricanorthsouthcentralussouthindiaspaincentralswedencentralswitzerlandnorthswitzerlandwestuaenorthwestcentralus
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:41 PM UTC
We have identified an issue with Azure affecting the Cloud NGFW Customers may experience delays/failures to deploy new resources Ongoing Actions: Our engineering team is working closely with the azure and We are working with the azure team to restore the services
-
investigating Mar 10, 2026, 02:33 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 10, 2026, 02:58 PM UTC
We are continuing to investigate this issue.
-
resolved Mar 10, 2026, 10:47 PM UTC
The resolution has been implemented across all regions. We confirm the successful deployment of the fix and will continue to monitor the sanity jobs.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 12:30 PM UTC
- Resolved
- Mar 10, 2026, 01:45 AM UTC
- Duration
- 13h 14m
Affected: United States - AmericasUnited States - AmericasUnited States - AmericasUnited States - AmericasUnited States - Americas
Timeline · 4 updates
-
investigating Mar 09, 2026, 12:30 PM UTC
We are currently investigating this issue.
-
investigating Mar 09, 2026, 05:44 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 09, 2026, 07:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 10, 2026, 01:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 08:22 PM UTC
- Resolved
- Mar 06, 2026, 08:24 PM UTC
- Duration
- 1m
Affected: ADNS Resolver 96.9.97.9ADNS Resolver 96.9.96.9
Timeline · 3 updates
-
investigating Mar 06, 2026, 08:22 PM UTC
One of our detectors is experiencing an issue that caused false positive blocking. Specifically, res-stls-prod[.]edgesuite[.]net.globalredir[.]akadns88[.]net was misclassified as phishing from 3/6/2026 13:08 UTC to 3/6/2026 16:50 UTC. This domain is a CNAME of res.cdn.office[.]net and res-stls-prod.edgesuite[.]net. So, the DNS resolution of res.cdn.office[.]net or res-stls-prod.edgesuite[.]net might experience blockage during the period of time mentioned above.
-
investigating Mar 06, 2026, 08:23 PM UTC
We have disabled the false positive signature to resume customer utility. We are continuing to investigate the root cause.
-
resolved Mar 06, 2026, 08:24 PM UTC
This incident has been resolved. We have identified the root cause. The incorrect verdict was due to multiple 3rd party intelligence feeds providing malicious verdicts. Enhancement measure will be added to reduce false positives caused by CNAME domains from 3rd party intelligence ingestions.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 11:10 PM UTC
- Resolved
- Mar 04, 2026, 01:07 AM UTC
- Duration
- 1h 57m
Affected: United States - Americas
Timeline · 2 updates
-
investigating Mar 03, 2026, 11:10 PM UTC
The edgeService stop to fetch latest verdicts from backend service. We have identified the issue in upstream component. We are monitoring the upstream service and will post the update here.
-
resolved Mar 04, 2026, 01:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 06:25 PM UTC
- Resolved
- Mar 04, 2026, 12:46 AM UTC
- Duration
- 6h 21m
Affected: United States
Timeline · 5 updates
-
investigating Mar 03, 2026, 06:25 PM UTC
The IoT service in the US is currently experiencing a portal access issue due to a database outage. As a result, US customers may have difficulties accessing the IoT portal at this time. The team is actively working to resolve the issue and will provide an update shortly.
-
investigating Mar 03, 2026, 09:49 PM UTC
The team is actively investigating the ongoing issue impacting the IoT service in the US. Efforts are focused on recovering the affected systems and restoring portal access for our customers. We will provide further updates as soon as more information is available. Thanks,
-
investigating Mar 03, 2026, 11:56 PM UTC
The IoT US Portal is currently recovering as connection limits have been stabilized and services are returning to baseline levels.
-
monitoring Mar 04, 2026, 12:08 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 04, 2026, 12:46 AM UTC
Status: Service is fully Restored Summary: The technical team has successfully addressed the underlying database issue and restored all affected services to full functionality. Details: Data integrity has been verified, and all system components are now operating within normal parameters. We are continuing to monitor the environment closely to ensure ongoing stability.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 05:30 PM UTC
- Resolved
- Mar 04, 2026, 03:44 AM UTC
- Duration
- 10h 13m
Timeline · 5 updates
-
investigating Mar 03, 2026, 05:30 PM UTC
We are currently investigating this issue.
-
investigating Mar 03, 2026, 05:32 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 03, 2026, 05:33 PM UTC
We are continuing to investigate this issue.
-
identified Mar 04, 2026, 12:42 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 04, 2026, 03:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 01:04 AM UTC
- Resolved
- Mar 03, 2026, 04:59 PM UTC
- Duration
- 15h 54m
Timeline · 4 updates
-
investigating Mar 03, 2026, 01:04 AM UTC
We are currently investigating this issue.
-
identified Mar 03, 2026, 01:19 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 03, 2026, 03:46 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 03, 2026, 04:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 04:51 PM UTC
- Resolved
- Mar 02, 2026, 09:49 PM UTC
- Duration
- 4h 58m
Affected: Bahrain (me-south-1)
Timeline · 2 updates
-
identified Mar 02, 2026, 04:51 PM UTC
AWS Middle East(Bahrain) outage impacting Cloud NGFW Services. We are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region. Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-history Next Update: 9:00PM 3/02/2026 UTC.
-
resolved Mar 02, 2026, 09:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 28, 2026, 07:59 AM UTC
- Resolved
- Feb 28, 2026, 09:59 AM UTC
- Duration
- 1h 59m
Affected: brazilsouth
Timeline · 4 updates
-
investigating Feb 28, 2026, 07:59 AM UTC
Azure Brazil South region experiencing Intermittent Network connectivity issue which is impacting CNGFW Services. Customers may experience intermittent service unavailability, degraded performance, or delays in monitoring and telemetry. Current Status : Azure notified intermittent connectivity and packet loss issue affecting network traffic to and from this region. We are actively investigating and mitigation actions are currently in progress to stabilize connectivity. Ongoing Actions: Our engineering team is working closely with the Azure team to restore full service. You can also monitor the underlying platform status via the Azure Service Page. https://app.azure.com/h/CQLF-C40/3f4a19
-
monitoring Feb 28, 2026, 09:37 AM UTC
Azure has mitigated the underlying intermittent network issue. We are monitoring for continued stability.
-
monitoring Feb 28, 2026, 09:42 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 28, 2026, 09:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 07:34 PM UTC
- Resolved
- Feb 26, 2026, 11:30 PM UTC
- Duration
- 3h 55m
Timeline · 2 updates
-
identified Feb 26, 2026, 07:34 PM UTC
WildFire analysis on February 25, 2026, PST, resulted in an incorrect verdict for a specific set of files. We are currently correcting the verdicts for all affected files.
-
resolved Feb 26, 2026, 11:30 PM UTC
By 1:00 PM PST on February 26, 2026, the verdicts for all affected files have been corrected.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 04:06 AM UTC
- Resolved
- Feb 20, 2026, 04:21 AM UTC
- Duration
- 14m
Affected: Customer Support Portal
Timeline · 2 updates
-
identified Feb 20, 2026, 04:06 AM UTC
Adding new comments to support cases is currently unavailable. The issue has been identified and a fix is being implemented.
-
resolved Feb 20, 2026, 04:21 AM UTC
The issue has been resolved and adding comments is now functional.
Read the full incident report →
- Detected by Pingoru
- Feb 14, 2026, 12:14 AM UTC
- Resolved
- Feb 12, 2026, 05:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 14, 2026, 12:14 AM UTC
Briefly during the morning of 2/12/2026, the domain svc.ha-teams.office.com was miscategorized within AURL filtering and ADNS products. This may have caused interruptions in Microsoft Teams traffic. The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 04:03 AM UTC
- Resolved
- Feb 11, 2026, 10:29 AM UTC
- Duration
- 6h 25m
Affected: centraluseastus2westus3
Timeline · 3 updates
-
investigating Feb 11, 2026, 04:03 AM UTC
Azure East US 2, South Central US & West US 3 Resource Manager impacting CNGFW services. Customers may experience intermittent service unavailability, degraded performance, or delays in on creating firewall where Public IP is needed. It would not impact already created Firewall resources. Ongoing Actions: Our engineering team is working closely with the Azure team. Further updates on the underlying azure platform status can be followed through the Azure Status Page. https://app.azure.com/h/B_6T-NXZ/418272
-
monitoring Feb 11, 2026, 06:44 AM UTC
CNGFW Services continues to remain being monitored & currently No impact detected.
-
resolved Feb 11, 2026, 10:29 AM UTC
CNGFW Services continues to operate normally & no impact observed.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 12:11 PM UTC
- Resolved
- Feb 09, 2026, 11:50 PM UTC
- Duration
- 11h 38m
Timeline · 3 updates
-
investigating Feb 09, 2026, 12:11 PM UTC
We are currently investigating this issue.
-
investigating Feb 09, 2026, 01:13 PM UTC
We have engaged all relevant teams and are actively investigating the issue with the highest priority. Further updates will be shared as soon as more information is available.
-
resolved Feb 09, 2026, 11:50 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 7, 2026 - Detected by Pingoru
- Feb 07, 2026, 05:04 PM UTC
- Resolved
- Feb 08, 2026, 12:55 AM UTC
- Duration
- 7h 50m
Affected: westuswestus2westus3
Timeline · 3 updates
-
investigating Feb 07, 2026, 05:04 PM UTC
Azure US West outage impacting CNGFW Services. We have identified an Azure outage affecting the Cloud NGFW West US region. Customers may experience intermittent service unavailability, degraded performance, or delays in monitoring and telemetry. Current Status: Earlier today, an unexpected utility power interruption at a Azure West US datacenter caused a partial facility outage. While backup power systems engaged immediately and utility power has since been stabilized, some infrastructure components were temporarily affected. Ongoing Actions: Our engineering team is working closely with the Azure team to restore full service. You can also monitor the underlying platform status via the Azure Status Page. https://azure.status.microsoft/en-us/status Next Update: 01:30 UTC, 08 February 2026
-
investigating Feb 07, 2026, 05:21 PM UTC
The Azure outage that impacted your CNGFW service is now resolved and your service is back up. The firewall resources that were experiencing service degradation has been restored. Please contact Palo Alto Networks support team to address any concerns. Thank you,
-
resolved Feb 08, 2026, 12:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 02:42 PM UTC
- Resolved
- Feb 06, 2026, 03:59 PM UTC
- Duration
- 1h 16m
Affected: AustraliaAustraliaAustraliaAustraliaCanadaCanadaCanadaCanadaGermanyGermanyGermanyGermanyIndiaIndiaIndiaIndiaJapanJapanJapanJapanNetherlands - EuropeNetherlands - EuropeNetherlands - EuropeNetherlands - EuropeSingaporeSwitzerlandSingaporeSwitzerlandUnited KingdomSwitzerlandSwitzerlandUnited KindomUnited States - AmericasUnited KingdomUnited KingdomUnited States - AmericasUnited States - GovernmentUnited States - AmericasUnited States - AmericasUnited States - GovermentUnited States - GovernmentUnited States - GovernmentPolandPolandPolandPolandTaiwanTaiwanSingaporeTaiwanTaiwanSingaporeQatarQatarQatarQatarIsraelIsraelIsraelIsraelFranceFranceFranceFranceSaudi ArabiaSaudi ArabiaSaudi ArabiaSaudi ArabiaIndonesiaIndonesiaIndonesiaIndonesiaSpainSpainSpainSpainItalyItalyItalyItalyKoreaKoreaKoreaKoreaSouth AfricaSouth AfricaSouth AfricaSouth Africa
Timeline · 2 updates
-
investigating Feb 06, 2026, 02:42 PM UTC
We are currently investigating this issue.
-
resolved Feb 06, 2026, 03:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 09:15 PM UTC
- Resolved
- Feb 04, 2026, 10:45 PM UTC
- Duration
- 1h 30m
Affected: United States - Americas
Timeline · 2 updates
-
investigating Feb 10, 2026, 07:44 AM UTC
We are currently investigating this issue. Customer Impact: Customer Firewalls may be unable to send data to the AIRS Cloud in the United States region.
-
resolved Feb 10, 2026, 07:46 AM UTC
This incident has been resolved.
Read the full incident report →