- Detected by Pingoru
- Mar 06, 2026, 05:22 AM UTC
- Resolved
- Mar 06, 2026, 05:46 AM UTC
- Duration
- 24m
Affected: SWGSWGSWGSWG
Timeline · 2 updates
-
investigating Mar 06, 2026, 05:22 AM UTC
We are investigating a potential issue with SWG FQDN service affecting customers connecting to the Multiple Region across data center. Customer will not be able to access as SWG FQDN as the Service is not be able resolve the IP Cisco is currently working to confirm the impact, identify the root cause, and implement a resolution. We are committed to restoring full service as quickly as possible. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time
-
resolved Mar 06, 2026, 05:46 AM UTC
The issue affecting SWG FQDN has been resolved as of 05:36 UTC Mar 06, 2026 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 07:51 PM UTC
- Resolved
- Mar 02, 2026, 07:51 PM UTC
- Duration
- —
Affected: API Reporting
Timeline · 1 update
-
resolved Mar 02, 2026, 07:51 PM UTC
We identified an issue impacting DLP event reporting between 18:43 UTC and 19:09 UTC. During this time, DLP policies continued to be enforced. However, some DLP events may not have been recorded or displayed in dashboards. DLP Reporting functionality has now been fully restored. We apologize for the inconvenience.If you have any questions or need assistance, please contact our support team.
Read the full incident report →
- Detected by Pingoru
- Feb 28, 2026, 04:20 PM UTC
- Resolved
- Feb 28, 2026, 05:44 PM UTC
- Duration
- 1h 23m
Affected: Real Time DLP
Timeline · 4 updates
-
investigating Feb 28, 2026, 04:20 PM UTC
We are investigating an issue where the 'AnyDestination' functionality within DLP is currently experiencing a service degradation. As a result, scanners are failing to process 'any destination' requests appropriately and are instead reverting to legacy enforcement behavior. This has resulted in a 'fail-open' state, where policy enforcement is currently wide open. Our team is actively working to restore full functionality.
-
identified Feb 28, 2026, 04:49 PM UTC
We have identified the cause affecting 'AnyDestination' functionality within Data Loss Prevention. Remediation efforts are underway. Updates will be provided as restoration progresses.
-
monitoring Feb 28, 2026, 05:31 PM UTC
Remediation efforts have been implemented to address the issue affecting 'AnyDestination' functionality. We are now monitoring the environment as service functionality is restored across the platform. We will provide a final update once full stability is confirmed.
-
resolved Feb 28, 2026, 05:44 PM UTC
Full service functionality has been restored. All services are now operating normally. We’re Here to Help We apologize for any inconvenience caused and thank you for your patience.If you have any questions or need assistance, please contact our support team.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:23 PM UTC
- Resolved
- Mar 12, 2026, 03:23 PM UTC
- Duration
- 12d 22h
Affected: Dashboard
Timeline · 6 updates
-
investigating Feb 27, 2026, 05:23 PM UTC
We are currently investigating an issue impacting one feature within the Investigate dashboard, specifically the DNS query volume . This affects the visibility of query volume data in the UI. All other Umbrella services, including DNS resolution, traffic handling, and policy enforcement, remain fully operational. Our team is actively working to restore normal data processing for the affected dashboard feature and will provide updates as they become available.
-
identified Feb 27, 2026, 06:03 PM UTC
We have identified the issue impacting the DNS query volume display within the Investigate dashboard. DNS resolution, traffic handling, and policy enforcement remain fully operational. The team is preparing remediation steps and will continue monitoring the system
-
identified Feb 27, 2026, 06:27 PM UTC
We are continuing to work on a fix for this issue.
-
identified Feb 27, 2026, 06:31 PM UTC
We are continuing to work on a fix for this issue.
-
identified Mar 02, 2026, 06:36 PM UTC
Our engineering teams are continuing to make progress on resolving the display issue within the Investigate dashboard. While remediation is in progress, we anticipate it may take a few more days to fully resolve. We will provide further updates as they become available.
-
resolved Mar 12, 2026, 03:23 PM UTC
We are pleased to confirm that the display issue impacting the Investigate dashboard has been fully resolved. All dashboard functions are now operating as expected. Thank you for your patience and understanding while we worked to restore full service.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 09:16 AM UTC
- Resolved
- Feb 12, 2026, 02:05 PM UTC
- Duration
- 4h 49m
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 11:41 PM UTC
- Resolved
- Jan 30, 2026, 11:45 PM UTC
- Duration
- 4m
Affected: Dashboard
Timeline · 2 updates
-
investigating Jan 30, 2026, 11:41 PM UTC
We are aware of an issue with the Umbrella App Discovery page impacting some customers in Central United States. Certain components of the page may not be loading as expected. Our team is actively investigating the problem and working to restore full functionality. Thank you for your patience and understanding
-
resolved Jan 30, 2026, 11:45 PM UTC
This incident has been resolved. If you continue to experience any problems, please contact support.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 12:38 AM UTC
- Resolved
- Jan 28, 2026, 01:38 AM UTC
- Duration
- 1h
Affected: Network Tunnels
Timeline · 4 updates
-
investigating Jan 28, 2026, 12:38 AM UTC
We are currently investigating a potential issue affecting tunnel service creation for customers connecting to the Minneapolis data center. Customers may experience disconnections or failures when establishing new tunnels or modifying PSKs. Our engineering team is actively working to confirm the impact, identify the root cause, and implement a resolution. Updates and additional details will be provided as more information becomes available.
-
investigating Jan 28, 2026, 12:39 AM UTC
We are continuing to investigate this issue.
-
investigating Jan 28, 2026, 12:47 AM UTC
We are continuing to investigate this issue.
-
resolved Jan 28, 2026, 01:38 AM UTC
The issue has been identified and resolved as of 2026-01-28 01:17 UTC All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 08:45 AM UTC
- Resolved
- Jan 27, 2026, 08:04 AM UTC
- Duration
- 23h 19m
Affected: Cloud Delivered FirewallIPsec Tunnel Head-EndSWGNetwork TunnelsRemote Access (Client)Remote Access (Clientless)SWG
Timeline · 5 updates
-
identified Jan 26, 2026, 08:45 AM UTC
We have performed mitigation actions to address the intermittent connectivity issues affecting customers connecting via the Copenhagen (CPH1.EDC) data center and are currently monitoring the situation for continued stability. Customers may still experience intermittent connectivity. For the best possible experience, we recommend connecting to the nearest available data center while we continue to address the situation. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
-
identified Jan 26, 2026, 08:52 AM UTC
The Copenhagen (CPH1.EDC) data center has been taken Out of Rotation (OOR) as we continue to address and monitor intermittent connectivity issues. All customers are advised to connect to the nearest available data center for the best possible experience while our engineering team monitors the situation for stability. We will provide updates as more information becomes available and appreciate your patience during this time. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
-
identified Jan 26, 2026, 08:54 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jan 26, 2026, 12:33 PM UTC
The intermittent connectivity issues affecting the Copenhagen (CPH1.EDC) data center have been mitigated, and we are currently monitoring the site to ensure continued stability. At this time, customers should continue to use the nearest available data center for optimal performance. Once Copenhagen (CPH1.EDC) is ready to be brought back into rotation (BIR), we will provide further updates with all relevant details. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
-
resolved Jan 27, 2026, 08:04 AM UTC
The issue affecting connectivity in Copenhagen (CPH1.EDC) has been resolved as of 07:50 UTC. The data center has now been brought back into rotation (BIR), and all services are up and running. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 10:37 PM UTC
- Resolved
- Jan 25, 2026, 12:32 PM UTC
- Duration
- 1d 13h
Timeline · 2 updates
-
investigating Jan 23, 2026, 10:37 PM UTC
Customers connecting via Copenhagen (CPH1.EDC) may have experience intermittent connectivity issues. We recommend connecting to the nearest available data center for the best possible experience while we continue to address the situation. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.
-
resolved Jan 25, 2026, 12:32 PM UTC
Traffic has been redirected to the nearest site.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 12:26 PM UTC
- Resolved
- Jan 23, 2026, 09:22 PM UTC
- Duration
- 8h 55m
Affected: Cloud Delivered FirewallIPsec Tunnel Head-EndSWGNetwork TunnelsRemote Access (Client)Remote Access (Clientless)SWG
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 08:18 AM UTC
- Resolved
- Jan 15, 2026, 02:05 PM UTC
- Duration
- 5h 46m
Affected: Cloud Delivered FirewallIPsec Tunnel Head-End
Timeline · 5 updates
-
investigating Jan 15, 2026, 08:18 AM UTC
We are currently investigating an issue affecting tunnel services at the Palo Alto Datacenter. To maintain service continuity, traffic has been redirected to our Los Angeles (LAX1) Data Center. We will provide periodic updates and share new information as it becomes available.
-
identified Jan 15, 2026, 10:58 AM UTC
We have identified the cause of the issue affecting tunnel services at the Palo Alto Datacenter. Remediation efforts are underway, and service stability has improved. We are actively monitoring the situation and will provide a final update once the issue is fully resolved.
-
identified Jan 15, 2026, 11:48 AM UTC
We are continuing to work on a fix for this issue.
-
investigating Jan 15, 2026, 02:04 PM UTC
The issue affecting instabilities in Palo Alto has been resolved as of 13:35 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
-
resolved Jan 15, 2026, 02:05 PM UTC
The issue affecting instabilities in Palo Alto has been resolved as of 13:35 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 08:01 PM UTC
- Resolved
- Jan 14, 2026, 02:17 AM UTC
- Duration
- 6h 16m
Affected: SWGSWGSWGSWGSWGSWGSWGSWGSWGSWGSWGSWG
Timeline · 4 updates
-
investigating Jan 13, 2026, 08:01 PM UTC
The Web Policy feature "Protect bypass" which is designed to allow encrypted files to bypass blocking, is currently not functioning as intended. Our engineering team is actively working to resolve this issue.
-
identified Jan 13, 2026, 08:47 PM UTC
The engineering team has identified the issue and is currently performing a rollback to restore full functionality. The rollback process may take up to three hours to complete.
-
identified Jan 14, 2026, 12:51 AM UTC
Rollback has been completed in all locations except for Singapore, which is still in progress.
-
resolved Jan 14, 2026, 02:17 AM UTC
Rollback has been completed in Singapore, and all issues have been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 10:02 AM UTC
- Resolved
- Jan 09, 2026, 11:12 AM UTC
- Duration
- 1h 9m
Affected: Dashboard
Timeline · 3 updates
-
investigating Jan 09, 2026, 10:02 AM UTC
Tenant configuration not Loading on dashboard We are currently investigating an issue causing Tenant configuration missing from the dashboard. Customers will not be able to view configured tenants (new or existing) on the dashboard. However, the tenants are correctly configured on the backend and are functioning as expected. Updates will be provided as more information becomes available.
-
monitoring Jan 09, 2026, 10:15 AM UTC
The issue has been identified and fixed by the ENG team. We are currently monitoring the situation and will provide updates as soon as they are available.
-
resolved Jan 09, 2026, 11:12 AM UTC
The issue affecting Tenant configuration missing from the Dashboard has been resolved as of 10:02UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 30, 2025, 12:14 PM UTC
- Resolved
- Dec 30, 2025, 06:15 PM UTC
- Duration
- 6h 1m
Affected: SWGSWGSWG
Timeline · 4 updates
-
investigating Dec 30, 2025, 12:14 PM UTC
We are currently experiencing a service performance issue affecting multiple data centers. You may notice an increased number of fail opens and timeouts, resulting in delays or failures when making requests. Our engineers are currently working to identify the root cause and implement a resolution. Updates will be provided as new information becomes available.
-
monitoring Dec 30, 2025, 01:26 PM UTC
We identified issues and implemented a fix at 13:12 UTC. Subsequent internal checks indicate everything is working fine now. The team continues to monitor the situation closely.
-
monitoring Dec 30, 2025, 02:52 PM UTC
We are continuing to monitor for any further issues.
-
resolved Dec 30, 2025, 06:15 PM UTC
This incident has been resolved.
Read the full incident report →
Critical December 12, 2025 - Detected by Pingoru
- Dec 12, 2025, 10:18 AM UTC
- Resolved
- Dec 12, 2025, 11:30 AM UTC
- Duration
- 1h 11m
Affected: IPsec Tunnel Head-EndRemote Access (Client)
Timeline · 2 updates
-
investigating Dec 12, 2025, 10:18 AM UTC
Users are unable to connect to Stockholm - STO1.EDC headend using VPN. Our engineers are currently working to confirm the impact, identify the root cause and implement a resolution. Updates and additional details will be provided as new information becomes available.
-
resolved Dec 12, 2025, 11:30 AM UTC
The issue affecting connection in STO1.EDC has been resolved. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 04:26 AM UTC
- Resolved
- Dec 11, 2025, 05:49 AM UTC
- Duration
- 1h 23m
Affected: Meraki SD-WAN Head-End
Timeline · 2 updates
-
investigating Dec 11, 2025, 04:26 AM UTC
Some customers may experience connectivity issues with their tunnels in FRA1.EDC; the tunnels may appear to be connected, but traffic may not be able to be sent/received over the tunnel. Our engineers are currently working to identify the root cause and implement a resolution. Updates and additional details will be provided as new information becomes available.
-
resolved Dec 11, 2025, 05:49 AM UTC
The issue affecting Meraki SD-WAN Head-End in FRA1 has been resolved as of 2025-12-11 05:06 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 11:19 AM UTC
- Resolved
- Dec 10, 2025, 03:39 PM UTC
- Duration
- 4h 20m
Affected: Cloud Delivered FirewallCloud Delivered FirewallCloud Delivered FirewallCloud Delivered Firewall
Timeline · 5 updates
-
investigating Dec 10, 2025, 11:19 AM UTC
We are investigating an issue affecting tunnel connectivity for few Data Centers listed below: Singapore Atlanta Tokyo Paris Denver Ashburn New York Dallas Mexico City Chicago Madrid London Stockholm Customers may experience dropped or blackholed traffic, or see tunnels appear as down in dashboards. Our team is working to restore full connectivity as quickly as possible.
-
investigating Dec 10, 2025, 11:32 AM UTC
We are continuing to investigate this issue.
-
investigating Dec 10, 2025, 01:10 PM UTC
We are investigating an issue affecting tunnel connectivity.We will provide further updates as more information becomes available.
-
identified Dec 10, 2025, 02:33 PM UTC
We have identified that a small number of servers have been impacted by the ongoing tunnel connectivity issue, while the majority of servers continue to operate normally. Our engineering team has initiated the mitigation process to fully resolve the issue. We will provide another update once the mitigation process is complete. Thank you for your continued patience as we work to restore full service.
-
resolved Dec 10, 2025, 03:39 PM UTC
An issue was identified and resolved by our engineering team as of 15:30 UTC today. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 05:20 PM UTC
- Resolved
- Dec 09, 2025, 06:25 AM UTC
- Duration
- 13h 4m
Affected: Meraki SD-WAN Head-EndRemote Access (Client)
Timeline · 4 updates
-
identified Dec 08, 2025, 05:20 PM UTC
We have identified a management plane issue at the Frankfurt Data Center and we are failing over Secure Connect users to London Data Center. Will provide updates as soon as more information becomes available. Thank you for your understanding and cooperation.
-
identified Dec 08, 2025, 05:59 PM UTC
We also identified that Secure Connect Remote Client Services got affected by the issue, customer will be redirected to the closest Data Center.
-
identified Dec 08, 2025, 08:10 PM UTC
Meraki SD-WAN users are redirected to the London Data Center, and Secure Connect Remote Client Services will be redirected to the closest available data center to ensure service continuity. The team is actively working to resolve the issue and bring the Frankfurt data center back into rotation. We appreciate your patience and understanding during this process. Further updates will be provided as they become available. Thank you for your continued cooperation.
-
resolved Dec 09, 2025, 06:25 AM UTC
The Frankfurt data center has been brought back into rotation, and all Secure Connect services have been restored there. We appreciate your patience and understanding during this process. Thank you for your continued cooperation, this incident has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 06, 2025, 02:45 AM UTC
- Resolved
- Dec 06, 2025, 03:25 AM UTC
- Duration
- 39m
Affected: APIDashboard
Timeline · 3 updates
-
investigating Dec 06, 2025, 02:45 AM UTC
We are currently investigating an issue where users are seeing a "500 Internal Server Error" when attempting to access the dashboard. We will provide updates as soon as more information is available.
-
identified Dec 06, 2025, 03:01 AM UTC
We have identified the cause of the issue resulting in the "500 Internal Server Error" on the dashboard after login. This issue also extends to related APIs, which may be unavailable at this time. Our Engineering team is actively working to restore service for both the dashboard and affected APIs. We will provide another update in 30 minutes. Thank you for your continued patience.
-
resolved Dec 06, 2025, 03:25 AM UTC
We are pleased to report that the issue causing the "500 Internal Server Error" on the dashboard and related APIs has been resolved. All affected services have been restored and are now operating normally. Thank you for your patience while we worked to resolve this issue. If you continue to experience any problems, please contact support.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 03:45 PM UTC
- Resolved
- Dec 03, 2025, 05:22 PM UTC
- Duration
- 1h 37m
Affected: Dashboard
Timeline · 4 updates
-
monitoring Dec 03, 2025, 03:45 PM UTC
If you are having problems logging in, we recommend retrying the authentication process and please contact your Identity Provider (IDP) provider. We have identified authentication issues related to the use of one particular (IDP). We will continue to monitor the issue.
-
monitoring Dec 03, 2025, 04:19 PM UTC
We are continuing to monitor the issue.
-
monitoring Dec 03, 2025, 04:55 PM UTC
We are continuing to monitor the issue.
-
resolved Dec 03, 2025, 05:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 11:00 AM UTC
- Resolved
- Dec 02, 2025, 11:27 AM UTC
- Duration
- 27m
Affected: SWGSWGSWGSWGSWG
Timeline · 2 updates
-
investigating Dec 02, 2025, 11:00 AM UTC
We are investigating an issue affecting File Inspection services in various Data centers. Customers may experience delays in file analysis, missing inspection logs, or partial visibility in the dashboard. Our engineering teams are actively working to identify the root cause and restore normal processing. We will provide updates as new information becomes available.
-
resolved Dec 02, 2025, 11:27 AM UTC
The issue affecting File scanning has now been resolved as of 11:09 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Nov 29, 2025, 08:00 AM UTC
- Resolved
- Nov 29, 2025, 10:09 AM UTC
- Duration
- 2h 9m
Affected: DNS
Timeline · 2 updates
-
investigating Nov 29, 2025, 08:00 AM UTC
We are currently investigating an issue involving an intermittent latency increase on some DNS resolution requests.
-
resolved Nov 29, 2025, 10:09 AM UTC
The incident has been resolved as of approximately 2025-11-29 09:33 UTC.
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2025, 10:59 PM UTC
- Resolved
- Nov 28, 2025, 12:44 AM UTC
- Duration
- 1h 44m
Affected: DNS
Timeline · 3 updates
-
identified Nov 27, 2025, 10:59 PM UTC
We are currently investigating an issue with the secondary Protective DNS (PDNS) IP Address (204.194.234.200) not being reachable from the public internet. The primary IP Address (204.194.232.200) remains operational. Only customers using this specific IP Address may be impacted in the event that they are unable to reach the primary IP Address.
-
monitoring Nov 27, 2025, 11:51 PM UTC
A fix has been implemented and we are monitoring the results. The issue should be resolved for most (but not all) customers.
-
resolved Nov 28, 2025, 12:44 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 10:50 PM UTC
- Resolved
- Nov 18, 2025, 11:05 PM UTC
- Duration
- 14m
Affected: Meraki SD-WAN Head-End
Timeline · 3 updates
-
investigating Nov 18, 2025, 10:50 PM UTC
We are currently investigating a potential incident in the Denver Data Centre. Some customers may not be able to access public internet resources via Denver, but services should have failed over to Dallas.
-
identified Nov 18, 2025, 10:59 PM UTC
The issue has been identified, and our engineers are working on the resolution. Some tunnels in Denver may be interrupted during this process, but any services that failed over to Dallas would not be interrupted.
-
resolved Nov 18, 2025, 11:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 06:07 PM UTC
- Resolved
- Nov 18, 2025, 10:00 PM UTC
- Duration
- 3h 52m
Timeline · 1 update
-
resolved Nov 18, 2025, 06:07 PM UTC
Remote Access (Clients) may have experienced a a brief 15-minute traffic interruption during this period at the London data center. Timeframe: London: 16:00 UTC – 16:35 UTC, November 18th, 2025 We apologize for any inconvenience this may have caused and appreciate your understanding.
Read the full incident report →