- Detected by Pingoru
- Mar 06, 2026, 10:55 AM UTC
- Resolved
- Mar 07, 2026, 02:02 AM UTC
- Duration
- 15h 6m
Affected: APICisco Secure ClientData Loss PreventionDNSExperience InsightsNetwork Tunnel GroupsPolicy EnforcementRemote Access VPNRemote Browser IsolationReporting and LoggingReserved IPResource ConnectorWeb SecurityZero Trust Access
Timeline · 5 updates
-
investigating Mar 06, 2026, 10:55 AM UTC
During our routine maintenance window on the Kubernetes cluster, we encountered an issue impacting the Miami region. Traffic continues to flow, but some customers may experience degraded performance. As a precaution, some customers may be moved to other data centers to ensure service stability. Our teams are working to restore normal operations and will provide updates as more information becomes available. Thank you for your understanding and cooperation. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your continued support as we work to enhance your Cisco Secure Access experience.
-
investigating Mar 06, 2026, 12:03 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 06, 2026, 12:37 PM UTC
We are taking the Miami data center Out Of Rotation to address ongoing performance concerns. All customer traffic will be automatically redirected to the nearest data center to maintain service continuity. No disruption to customer traffic is expected during this transition. We will continue to monitor the situation and provide updates as needed.
-
identified Mar 06, 2026, 02:44 PM UTC
We are continuing with taking the Miami data center Out Of Rotation
-
resolved Mar 07, 2026, 02:02 AM UTC
The issue of performance degradation at the Miami Data Center has been resolved. All services are now operating normally without any interruptions
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 05:30 AM UTC
- Resolved
- Mar 06, 2026, 05:46 AM UTC
- Duration
- 15m
Affected: DNSDNSDNSDNSDNSDNSDNSDNSDNSDNS
Timeline · 2 updates
-
investigating Mar 06, 2026, 05:30 AM UTC
We are investigating a potential issue with SWG FQDN service affecting customers connecting to the India, Asia, Europe Region across Multiple 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 05, 2026, 08:00 AM UTC
- Resolved
- Mar 05, 2026, 08:00 AM UTC
- Duration
- —
Affected: Data Loss PreventionWeb Security
Timeline · 1 update
-
resolved Mar 05, 2026, 08:00 AM UTC
We have identified an issue impacting DLP services in the India South region between 6:50 UTC and 07:43 UTC which has been identified and resolved
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 11:11 AM UTC
- Resolved
- Mar 04, 2026, 11:50 AM UTC
- Duration
- 38m
Affected: Data Loss PreventionWeb Security
Timeline · 2 updates
-
investigating Mar 04, 2026, 11:11 AM UTC
We are currently investigating an issue involving fail-open for DLP affecting services in the London region. Our teams are working to identify the cause and will provide updates as more information becomes available. Thank you for your patience and understanding. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your support as we work to enhance your Cisco Secure Access experience.
-
resolved Mar 04, 2026, 11:50 AM UTC
The issue involving fail-open for DLP affecting services in the London region has been resolved. All services are now operating normally. We appreciate your patience and understanding while we worked to address this matter.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 01:02 PM UTC
- Resolved
- Mar 02, 2026, 08:30 PM UTC
- Duration
- 7h 27m
Affected: Remote Access VPN (LA)
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 04:09 PM UTC
- Resolved
- Mar 02, 2026, 02:29 AM UTC
- Duration
- 10h 19m
Affected: Reserved IP
Timeline · 4 updates
-
identified Mar 01, 2026, 04:09 PM UTC
We have identified an issue affecting a limited subset of customers using Reserved IP configurations in the Dubai region. The impact is isolated to specific infrastructure components, and our team is actively working on mitigation efforts. We are also coordinating with our cloud partner as part of the recovery process. We will continue to provide updates as progress is made toward full restoration.
-
identified Mar 01, 2026, 07:08 PM UTC
We continue to make progress on the issue affecting a limited subset of customers using Reserved IP configurations in the Dubai (mec1-1-0) region. Mitigation actions are actively underway, and we are closely coordinating with our cloud partner to restore full service. No broader service impact has been observed. We will provide further updates as additional progress is made.
-
identified Mar 02, 2026, 12:04 AM UTC
We are observing continued progress in restoring functionality for limited subset of customers impacted by Reserved IP configurations in the Dubai (mec1-1-0) region. Improvements have been seen in infrastructure operations, and mitigation efforts remain actively in progress.
-
resolved Mar 02, 2026, 02:29 AM UTC
The issue affecting a limited subset of customers using Reserved IP configurations in the Middle East (UAE) region has been fully resolved.Service functionality has been fully restored, and the environment is stable. We will continue to monitor the region to ensure sustained performance and reliability. 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.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 01:12 PM UTC
- Resolved
- Mar 01, 2026, 03:57 PM UTC
- Duration
- 2h 45m
Affected: Cisco Secure ClientExperience InsightsNetwork Tunnel GroupsPolicy EnforcementRemote Access VPNRemote Browser IsolationReserved IPResource ConnectorZero Trust Access
Timeline · 5 updates
-
investigating Mar 01, 2026, 01:12 PM UTC
We are currently investigating a service availability issue affecting Secure Access in the Dubai. Some users may experience timeouts and difficulties accessing resources. Our engineering team is actively 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 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.
-
investigating Mar 01, 2026, 01:14 PM UTC
We are continuing to investigate this issue.
-
identified Mar 01, 2026, 01:55 PM UTC
We have identified the root cause of the issue affecting customer connectivity and service stability in Dubai. Remediation efforts are underway. Updates will be provided as restoration progresses.
-
identified Mar 01, 2026, 03:27 PM UTC
We are continuing to work on the issue, which has been identified as related to a cloud infrastructure disruption impacting services in the Dubai region. Our team remains actively engaged in mitigation efforts and is closely monitoring the situation. We will provide further updates as additional information becomes available.
-
resolved Mar 01, 2026, 03:57 PM UTC
The migration of services from mec1-1-0 to mec1-1-1 has been successfully completed. This action has restored service stability, and the issue is now resolved. 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
- Feb 27, 2026, 06:16 PM UTC
- Resolved
- Mar 12, 2026, 03:13 PM UTC
- Duration
- 12d 20h
Affected: Dashboard
Timeline · 4 updates
-
investigating Feb 27, 2026, 06:16 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:18 PM UTC
We have identified the issue impacting 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 Mar 02, 2026, 07:48 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:13 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 26, 2026, 07:28 AM UTC
- Resolved
- Feb 26, 2026, 07:28 AM UTC
- Duration
- —
Affected: Data Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss Prevention (LA)Data Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionRemote Access VPNPolicy EnforcementRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPN (LA)Remote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPNRemote Access VPN
Timeline · 1 update
-
resolved Feb 26, 2026, 07:28 AM UTC
We recently experienced an issue that affected Policy Updates, DLP Reporting, RAVPN, and Firewall-as-a-Service. The issue started at 05:12 UTC and was fully resolved by 05:51 UTC. During this period, DLP Policy updates would not have been propagated, and DLP Event reporting also would have failed. Customers may also have been unable to establish new RAVPN connections, Firewall policies were affected and configuration updates were not processed. All services are now operating normally. We sincerely apologize for any inconvenience this may have 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
- Feb 25, 2026, 03:20 PM UTC
- Resolved
- Feb 25, 2026, 05:57 PM UTC
- Duration
- 2h 37m
Affected: Zero Trust AccessZero Trust Access
Timeline · 6 updates
-
investigating Feb 25, 2026, 12:59 PM UTC
We are currently investigating an issue affecting Secure Access services in the Singapore (ap-southeast-1) and Stockholm ( eu-north-1_1_0) data centers. Some customers may be unable to access newly created private resources at this time. Our engineering teams are actively working to identify the cause and restore full functionality as quickly as possible. We will provide updates as more information becomes available. 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.
-
investigating Feb 25, 2026, 02:41 PM UTC
We are still investigating the issue affecting Secure Access services in the Singapore (ap-southeast-1) and Stockholm (eu-north-1_1_0) data centers. Updates will be provided as more information becomes available. Thank you for your patience and understanding.
-
investigating Feb 25, 2026, 03:20 PM UTC
A backend mitigation has been implemented and we are working to confirm its effectiveness. Investigation into the root cause remains ongoing.
-
investigating Feb 25, 2026, 03:58 PM UTC
As part of our ongoing investigation, we have redirected traffic away from a subset of our infrastructure to test for service restoration. We are observing system behavior over the next several minutes to validate the effectiveness of this change. We appreciate your patience as we work toward a resolution.
-
monitoring Feb 25, 2026, 05:07 PM UTC
Service has been stabilized following successful mitigation efforts and are being monitored.
-
resolved Feb 25, 2026, 05:57 PM UTC
Issue is resolved
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 08:57 AM UTC
- Resolved
- Feb 25, 2026, 09:13 AM UTC
- Duration
- 16m
Affected: Resource ConnectorResource ConnectorResource ConnectorZero Trust AccessZero Trust AccessZero Trust Access
Timeline · 2 updates
-
investigating Feb 25, 2026, 08:57 AM UTC
We are currently investigating a service availability issue affecting Secure Access in the Osaka, Tokyo, and Sydney regions. Some users may experience difficulties accessing resources through the application portal or private connections. Our teams are actively working to identify the cause and restore full service as quickly as possible. We will share updates as more information becomes available. 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.
-
resolved Feb 25, 2026, 09:13 AM UTC
The service availability issue affecting Secure Access in the Osaka, Tokyo, and Sydney regions has been resolved as of 08:55 UTC. Access to resources through the application portal and private connections is now functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 03:42 AM UTC
- Resolved
- Feb 25, 2026, 04:17 AM UTC
- Duration
- 34m
Affected: Reserved IPReserved IPReserved IP
Timeline · 2 updates
-
investigating Feb 25, 2026, 03:42 AM UTC
We are investigating a potential issue with the Reserved IP service affecting customers connecting to the sa-east110, us-west210, and us-west211 data centers. Multiple reserved IPs are currently not reachable in these regions. As a result, network traffic may not pass through the affected reserved IPs, which could cause network connectivity issues for impacted customers. Our engineering team is actively 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 Feb 25, 2026, 04:17 AM UTC
The issue affecting Reserved IP service in sa-east110 (Brazil), us-west210 (US - California), and us-west211 (US - Pacific Northwest) has been resolved. The Reserved IP service is 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
- Feb 21, 2026, 03:00 AM UTC
- Resolved
- Feb 21, 2026, 05:34 AM UTC
- Duration
- 2h 33m
Affected: Policy EnforcementPolicy EnforcementPolicy Enforcement
Timeline · 4 updates
-
investigating Feb 21, 2026, 03:00 AM UTC
We are currently encountering delays in the propagation of firewall policy changes in the Mumbai, Middle East, and Saudi Arabia regions. Our engineering team is actively 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
-
investigating Feb 21, 2026, 04:23 AM UTC
Our engineering team is actively investigating the issue. We will provide another update as soon as any new information becomes available.
-
monitoring Feb 21, 2026, 05:24 AM UTC
We are no longer seeing delays in firewall policy changes in the Mumbai, Middle East, and Saudi Arabia regions, and we continue to monitor the situation closely.
-
resolved Feb 21, 2026, 05:34 AM UTC
The issue has been resolved. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 10:02 PM UTC
- Resolved
- Feb 11, 2026, 11:23 PM UTC
- Duration
- 1h 21m
Affected: Zero Trust Access
Timeline · 4 updates
-
investigating Feb 11, 2026, 10:02 PM UTC
We are investigating an issue affecting Cisco Secure Access, where some customers may be experiencing issues with loading ZTNA posture profiles. Our engineering team is actively 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
-
investigating Feb 11, 2026, 10:26 PM UTC
We are still actively investigating the issue where some customers are experiencing ZTNA posture profiles not loading for multiple users. In addition, we have identified that VPN posture profiles are also impacted.
-
identified Feb 11, 2026, 11:04 PM UTC
We have identified the root cause of the issue. Our engineering teams are actively working to implement a resolution and restore full functionality as quickly as possible
-
resolved Feb 11, 2026, 11:23 PM UTC
The issue affecting ZTNA profiles and VPN posture profiles has been resolved.Thank you for your patience and understanding while we worked to restore full service.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 09:12 PM UTC
- Resolved
- Feb 11, 2026, 10:35 PM UTC
- Duration
- 1h 23m
Affected: Dashboard
Timeline · 4 updates
-
investigating Feb 11, 2026, 09:12 PM UTC
We are investigating an issue affecting the Cisco Secure Access Dashboard, where some customers are unable to open the Digital Experience element, including Experience Insights and ZTNA posture, within the dashboard. Our engineering team is actively 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
-
investigating Feb 11, 2026, 09:46 PM UTC
We are still actively investigating the issue affecting access to the Digital Experience elements within the Cisco Secure Access Dashboard.We appreciate your patience and will provide updates as soon as new information becomes available.
-
identified Feb 11, 2026, 10:16 PM UTC
We have identified the root cause of the issue. Our engineering teams are actively working to implement a resolution and restore full functionality as quickly as possible.
-
resolved Feb 11, 2026, 10:35 PM UTC
We are pleased to inform you that the issue affecting access to the Digital Experience has been resolved. If you have any questions or need assistance, please contact our support team.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 05:37 AM UTC
- Resolved
- Feb 06, 2026, 08:40 AM UTC
- Duration
- 3h 2m
Affected: APICisco Secure ClientData Loss PreventionDNSExperience InsightsNetwork Tunnel GroupsPolicy EnforcementRemote Access VPNRemote Browser IsolationReporting and LoggingReserved IPResource ConnectorWeb SecurityZero Trust Access
Timeline · 5 updates
-
investigating Feb 06, 2026, 05:37 AM UTC
We are currently experiencing loss of network connectivity at our Miami data center. As a result, all services hosted in this Data center are currently unavailable. Our engineering team is currently moving services out of rotation to backup datacenter and restore the services. We’re Here to Help If you have any questions or need assistance, please contact our support team.
-
identified Feb 06, 2026, 06:07 AM UTC
We have identified the issue and are working to restore services.
-
identified Feb 06, 2026, 06:58 AM UTC
Network connectivity has been restored for the Miami data center. We are in the process of bringing all services back into rotation. Our engineering team is closely monitoring progress.
-
monitoring Feb 06, 2026, 07:46 AM UTC
All services at the Miami data center have been brought back into rotation and are currently operational. Our engineering team is actively monitoring the environment to ensure continued stability.
-
resolved Feb 06, 2026, 08:40 AM UTC
The network connectivity issue at the Miami data center has been resolved as of 08:37 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 21, 2026, 08:35 AM UTC
- Resolved
- Jan 21, 2026, 10:42 AM UTC
- Duration
- 2h 7m
Affected: Data Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss Prevention (LA)Data Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss PreventionData Loss Prevention
Timeline · 3 updates
-
investigating Jan 21, 2026, 08:35 AM UTC
We are investigating an issue impacting Data Loss Prevention (DLP) functionality for all location. Customers may experience reduced DLP effectiveness for AI-based policies only. There is no impact to creating or modifying policies, and all other DLP policies continue to function as expected. Our engineering teams are actively working to identify the root cause, and implement a resolution. Updates and additional details will be provided as new information becomes available.
-
identified Jan 21, 2026, 08:41 AM UTC
We have identified the root cause of the issue affecting DLP policy. Remediation efforts are underway. We are actively monitoring the situation and will provide a final update once the issue is fully resolved.
-
resolved Jan 21, 2026, 10:42 AM UTC
The issue affecting Data Loss Functionality for AI Based policy in all locations has been resolved as of 10:37 UTC. All services are now operating normally. 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. 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 15, 2026, 03:17 PM UTC
- Resolved
- Jan 15, 2026, 03:23 PM UTC
- Duration
- 5m
Affected: Network Tunnel GroupsZero Trust Access
Timeline · 2 updates
-
monitoring Jan 15, 2026, 03:17 PM UTC
[Impact Statement]: Customers in India (West) - Mumbai (csc_ap_south-1_1_0) may have experienced latency and connection failures with Network Tunnel Groups and Zero Trust due to ISP issues from 14:20 UTC until 14:50 UTC. We are coordinating with relevant parties to make sure everything is stable.
-
resolved Jan 15, 2026, 03:23 PM UTC
The issue with ISPs are now resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 08:11 PM UTC
- Resolved
- Jan 14, 2026, 12:00 AM UTC
- Duration
- 3h 48m
Affected: Web SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb Security (LA)Web SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb SecurityWeb Security
Timeline · 3 updates
-
investigating Jan 13, 2026, 08:11 PM UTC
The feature "allow access to encrypted files" located under Secure, Advanced 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.
-
resolved Jan 14, 2026, 12:00 AM UTC
The rollback has been completed, and the issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 02:20 PM UTC
- Resolved
- Jan 12, 2026, 02:29 PM UTC
- Duration
- 9m
Affected: Dashboard
Timeline · 2 updates
-
investigating Jan 12, 2026, 02:20 PM UTC
It has been observed that since January 9th, the "Experience Insights" function is currently not operational in the Cisco Secure Access Portal. Engineering team is working to fix this issue.
-
resolved Jan 12, 2026, 02:29 PM UTC
The incident is resolved at 13:21 UTC. Engineering team identified and corrected an internal configuration.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 09:58 AM UTC
- Resolved
- Jan 09, 2026, 11:11 AM UTC
- Duration
- 1h 13m
Affected: Dashboard
Timeline · 3 updates
-
investigating Jan 09, 2026, 09:58 AM UTC
Tenant configuration not Loading in Cisco Secure Access Dashboard We are currently investigating an issue causing Tenant configuration missing from the Cisco Secure Access 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:11 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
- Jan 06, 2026, 04:40 AM UTC
- Resolved
- Jan 06, 2026, 05:22 AM UTC
- Duration
- 42m
Affected: Dashboard
Timeline · 2 updates
-
investigating Jan 06, 2026, 04:40 AM UTC
We are currently investigating an issue where users are getting error downloading ThousandEyes module profile from SSE dashboard.
-
resolved Jan 06, 2026, 05:22 AM UTC
Subsequent investigation determined that this was a false-positive issue, and there was no customer facing impact.
Read the full incident report →
- Detected by Pingoru
- Dec 30, 2025, 02:18 PM UTC
- Resolved
- Dec 30, 2025, 06:15 PM UTC
- Duration
- 3h 56m
Affected: DNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSDNSWeb SecurityWeb Security
Timeline · 2 updates
-
monitoring Dec 30, 2025, 02:18 PM UTC
Service performance issues occurred with specific name resolution starting at 10:55 UTC, impacting multiple data centers. A fix was implemented at 13:12 UTC, and internal checks confirmed that the service is now functioning properly. The issue is resolved, and the team is monitoring the situation closely.
-
resolved Dec 30, 2025, 06:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2025, 08:47 PM UTC
- Resolved
- Dec 12, 2025, 08:47 PM UTC
- Duration
- —
Affected: Network Tunnel Groups
Timeline · 1 update
-
resolved Dec 12, 2025, 08:47 PM UTC
It was identified an issue with Network Tunnel Groups in Frankfurt (eu-central-1-1-0), tunnels may have been redirected to the secondary datacenter between 20:10 UTC and 20:23 UTC. Service has been restored. 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
- Dec 12, 2025, 12:44 PM UTC
- Resolved
- Dec 12, 2025, 01:05 PM UTC
- Duration
- 20m
Affected: Data Loss Prevention
Timeline · 2 updates
-
investigating Dec 12, 2025, 12:44 PM UTC
We are currently investigating an issue affecting Data Loss Prevention (DLP) enforcement, and customers in this UAE region may not see their AI Guardrail policies being applied. Our engineering team is actively working to restore full service.
-
resolved Dec 12, 2025, 01:05 PM UTC
The issue affecting AI Guardrail policies in UAE has been resolved as of 13:00 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.
Read the full incident report →