Is Cisco Secure Access down?

Last checked 5m ago
Current status
Cisco Secure Access has degraded performance

Active incident: [Cisco Secure Access] - Connectivity Issue – Dubai

Official status page: https://status.sse.cisco.com · Polled every 5 minutes · 431 components tracked

Cisco Secure Access is reporting degraded performance right now (last checked 5m ago). Services are up but slower or partially failing.

Real-time Cisco Secure Access status, recent outages, and incident history — pulled directly from Cisco Secure Access's official status page at https://status.sse.cisco.com every 5 minutes. Pingoru tracks 431 Cisco Secure Access services and has captured 238 incidents in the last 90 days (99.52% uptime). Get email, Slack, Discord, or webhook alerts the moment Cisco Secure Access reports a new incident — free for 5 monitors, no credit card.

Users who monitor Cisco Secure Access also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Cisco Secure Access uptime 99.52% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incident 1

  1. Ongoing ● 202d 6h
    Started Mar 02, 2026, 05:55 AM UTC
    APICisco Secure ClientData Loss PreventionDNSExperience InsightsNetwork Tunnel GroupsPolicy EnforcementRemote Access VPNRemote Browser IsolationReporting and Logging
    Timeline · 9 updates
    • investigating · Mar 02, 2026, 05:55 AM 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. If you are using a reserved IP and need to steer your traffic to an alternate region, please contact us for assistance. 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 02, 2026, 06:18 AM UTC

      We are continuing to investigate this issue.

    • investigating · Mar 02, 2026, 07:49 AM UTC

      We are continuing to investigate this issue.

    • investigating · Mar 02, 2026, 08:34 AM UTC

      We are continuing our investigation into the service availability issue impacting Secure Access. Some users may still experience intermittent timeouts or difficulties accessing resources. Our engineering team is actively working to confirm the impact, identify the root cause, and implement a resolution. We apologize for any inconvenience caused and thank you for your patience.

    • investigating · Mar 02, 2026, 09:03 AM UTC

      For Organizations Located Only in ME-Central: Please follow these steps: • Select the nearest available data center (Mumbai or Hyderabad) as your migration target. • Configure VPN IP pools and profiles to match your organization’s current session load, mirroring your existing ME-Central setup. SWG Services in ME-Central: Due to the ongoing situation at this location, ME-Central has been taken out of rotation and customer traffic is being redirected to other regions. Please follow these steps to change Network Tunnel Group region: • Go to the NTG options as described here: https://securitydocs.cisco.com/docs/csa/olh/120421.dita • Edit your existing tunnel for the Middle East (UAE) region. • Change the region from Middle East (UAE) to India (West). • Do not modify other settings; save the configuration. • When prompted, type “UPDATE” and confirm. • Use the new India (West) IP addresses shown to update your IPSEC CPE device. • If Multi-Region Backhaul or route-maps are used, update BGP community values according to the new settings from Cisco SSE. ACGW Services in ME-Central: Please follow these steps: • Create Connector groups in your new region(s). • Assign private resources to the new Connector groups. For detailed instructions and screenshots, refer to the Resource Connector deployment guide: https://securitydocs.cisco.com/docs/csa/olh/118906.dita This guide provides a clear, step-by-step walkthrough to ensure a smooth migration process. If you require any assistance, please contact us. We will provide guidance on the necessary actions. We appreciate your cooperation and patience as we work to restore full service. Further updates will be provided as information becomes available.

    • investigating · Mar 02, 2026, 12:17 PM UTC

      We are continuing to investigate this issue.

    • investigating · Mar 02, 2026, 06:07 PM UTC

      We are continuing to investigate this issue.

    • identified · Mar 03, 2026, 07:55 PM UTC

      We are working closely with our cloud partners to address the regional data center issue. In the meantime, we strongly recommend that customers continue to follow the previously shared mitigation guidance, including migrating traffic to alternate regions (Mumbai or Hyderabad), updating Network Tunnel Group configurations where applicable, and reconfiguring Connector Groups for ACGW/ZTNA services as outlined in earlier updates. We are closely monitoring the situation and will provide further updates as more information becomes available.

    • identified · Apr 27, 2026, 05:47 PM UTC

      We have implemented a mitigation to redirect UAE traffic to an alternate data center (Mumbai) to address the ongoing service impact. Traffic is being steered to the Mumbai region, and we are actively monitoring system stability and performance. This mitigation primarily applies to automatically steered (roaming) UAE traffic. Customers in the affected region are advised to ensure their configurations align with previously shared guidance for alternate region routing, including any required updates to Network Tunnel Groups or Connector Groups. Customers already configured to alternate regions will continue using their configured region. Our engineering teams continue to investigate the underlying cause and are working closely with partners to ensure full service restoration. If you require any assistance, please contact us. We will provide guidance on the necessary actions.

    Latest: We have implemented a mitigation to redirect UAE traffic to an alternate data center (Mumbai) to address the ongoing service impact. Traffic is being steered to the Mumbai region, …

Recent outages & incidents

Past 90 days
  1. Resolved 7h 56m
    Started Sep 18, 2026, 03:23 AM UTC · Resolved Sep 18, 2026, 11:20 AM UTC
    Policy Enforcement
    Timeline · 4 updates
    • investigating · Sep 18, 2026, 03:23 AM UTC

      We are investigating a potential issue with the Riyadh DCv2 (Saudi Arabia) data center. Customers may experience intermittent connectivity and traffic disruption. 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 new information becomes available.

    • identified · Sep 18, 2026, 04:17 AM UTC

      We have identified the root cause of the issue affecting Riyadh DCv2 data center in Saudi Arabia. Remediation efforts are underway. Our engineering teams are actively working to restore normal service. We will continue monitoring the situation and provide a final update once the issue is fully resolved.

    • identified · Sep 18, 2026, 05:59 AM UTC

      We are taking the affected Riyadh DCv2 (csc_me-central-2_1_2) data center out of rotation to mitigate the issue. Customer traffic is being redirected to a nearby data center.

    • resolved · Sep 18, 2026, 11:20 AM UTC

      The issue affecting the Riyadh DCv2 data center has been resolved, and all affected services have been successfully Back In Rotation. 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, please contact our support team. Thank you for your understanding as we improve your Cisco Secure Access experience.

    Latest: The issue affecting the Riyadh DCv2 data center has been resolved, and all affected services have been successfully Back In Rotation. Services are now operating normally. We apolog…

  2. Resolved 15m
    Started Sep 17, 2026, 11:52 PM UTC · Resolved Sep 18, 2026, 12:07 AM UTC
    Data Loss PreventionWeb Security
    Timeline · 2 updates
    • investigating · Sep 17, 2026, 11:52 PM UTC

      We are investigating an issue affecting file scanning services for customers connecting through the US West region. Affected file scanning requests may operate in fail-open mode, allowing traffic to continue without completing file inspection. Our engineering teams are actively investigating. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

    • resolved · Sep 18, 2026, 12:07 AM UTC

      This issue has been resolved. Customer traffic is no longer operating in fail-open mode. Thank you for your patience. If you continue to experience issues, please contact Cisco Support.

    Latest: This issue has been resolved. Customer traffic is no longer operating in fail-open mode. Thank you for your patience. If you continue to experience issues, please contact Cisco Sup…

  3. Resolved
    Started Sep 16, 2026, 04:11 PM UTC · Resolved Sep 16, 2026, 04:11 PM UTC
    Dashboard
    Timeline · 1 update
    • resolved · Sep 16, 2026, 04:11 PM UTC

      Between approximately 11:25 and 14:50 UTC, customers using the Investigate dashboard and associated data retrieval APIs may have experienced 503 errors, unavailable graphs or data, and errors when retrieving logs or graph information. The issue has been resolved, and service has returned to normal.

    Latest: Between approximately 11:25 and 14:50 UTC, customers using the Investigate dashboard and associated data retrieval APIs may have experienced 503 errors, unavailable graphs or data,…

  4. Resolved 2h 52m
    Started Sep 16, 2026, 03:18 PM UTC · Resolved Sep 16, 2026, 06:11 PM UTC
    Policy Enforcement
    Timeline · 6 updates
    • investigating · Sep 16, 2026, 03:18 PM UTC

      We are investigating an issue affecting the Policy Enforcement service in the Israel (Tel Aviv) region. Policy updates and newly created policies will not propagate or take effect. Existing policies remain unaffected. Our engineering teams are actively working towards resolution.We will provide further updates as more information becomes available.

    • identified · Sep 16, 2026, 03:58 PM UTC

      Our engineering teams have identified the issue and are actively working on a resolution. We will keep you informed as our work progresses.

    • identified · Sep 16, 2026, 04:26 PM UTC

      Our engineering teams are implementing the remediation and working to restore normal service.

    • identified · Sep 16, 2026, 05:47 PM UTC

      Remediation efforts are ongoing, and our engineering teams continue working toward restoration.

    • identified · Sep 16, 2026, 06:02 PM UTC

      At 17:47 UTC, remediation was completed for il-central-1_1_0. Customers should no longer experience issues, and policy updates are expected to work normally. Remediation for il-central-1_1_1 remains in progress.

    • resolved · Sep 16, 2026, 06:11 PM UTC

      At 18:06 UTC remediation for il-central-1_1_1 has also been completed. The Policy Enforcement service in the Israel (Tel Aviv) region is now fully operational, and policy updates are working normally. We’re Here to Help If you have any questions or need assistance, please contact our support team.

    Latest: At 18:06 UTC remediation for il-central-1_1_1 has also been completed. The Policy Enforcement service in the Israel (Tel Aviv) region is now fully operational, and policy updates a…

  5. Resolved
    Started Sep 11, 2026, 05:55 PM UTC · Resolved Sep 11, 2026, 05:55 PM UTC
    Policy Enforcement
    Timeline · 1 update
    • resolved · Sep 11, 2026, 05:55 PM UTC

      Between 15:30 UTC and 16:50 UTC on September 11, 2026, customers routed through the Europe (Germany) data center, eu-central-1_1_1, may have experienced intermittent fail-open behavior. As a result, URL-based security policies may have been applied with default or unknown category verdicts. Some TLS decryption processing may also have been intermittently affected. The issue has been mitigated, and the service is operating normally. We’re Here to Help If you have any questions or need assistance, please contact our support team.

    Latest: Between 15:30 UTC and 16:50 UTC on September 11, 2026, customers routed through the Europe (Germany) data center, eu-central-1_1_1, may have experienced intermittent fail-open beha…

See the full Cisco Secure Access outage history

40 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Cisco Secure Access outage history →

Or sign up free to get alerts when Cisco Secure Access breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 44 incidents View full outage history →