Cisco Security Cloud Control Outage History

Cisco Security Cloud Control is up right now

Cisco Security Cloud Control had 10 outages in the last 2 years totaling 25h 14m of downtime — averaging 0.4 incidents per month.

There were 10 Cisco Security Cloud Control outages since December 17, 2024 totaling 25h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.security.cisco.com

Minor April 16, 2026

Notification of Degraded Performance on Security Cloud Control

Detected by Pingoru
Apr 16, 2026, 02:02 PM UTC
Resolved
Apr 16, 2026, 03:24 PM UTC
Duration
1h 22m
Affected: User InterfaceSign-OnProvisioning
Timeline · 2 updates
  1. investigating Apr 16, 2026, 02:02 PM UTC

    We want to inform you that we are currently experiencing degraded performance affecting your service. Our team is actively investigating the issue to identify the root cause and implement a resolution as quickly as possible

  2. resolved Apr 16, 2026, 03:24 PM UTC

    we have identified the cause and fix has been deployed.

Read the full incident report →

Minor December 12, 2025

SCC Sign-On Affected by Duo Authentication Outage

Detected by Pingoru
Dec 12, 2025, 07:34 AM UTC
Resolved
Dec 12, 2025, 11:17 AM UTC
Duration
3h 43m
Affected: Sign-On
Timeline · 5 updates
  1. investigating Dec 12, 2025, 07:34 AM UTC

    We are currently experiencing an issue affecting Duo Single Sign-On (SSO) functionality. Our team is actively working to resolve this matter. We will provide updates as progress is made.

  2. monitoring Dec 12, 2025, 08:17 AM UTC

    We are seeing improvement in our system. We are currently monitoring the system.

  3. monitoring Dec 12, 2025, 09:04 AM UTC

    We are seeing improvement in our system. We are currently monitoring the system.

  4. monitoring Dec 12, 2025, 10:06 AM UTC

    We are currently monitoring the system

  5. resolved Dec 12, 2025, 11:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 11, 2025

CCI/SCSO Redirection issue

Detected by Pingoru
Dec 11, 2025, 03:36 PM UTC
Resolved
Dec 11, 2025, 04:20 PM UTC
Duration
43m
Affected: Sign-On
Timeline · 3 updates
  1. investigating Dec 11, 2025, 03:36 PM UTC

    We're currently investigating an issue affecting customers with CCI integrated to their SCSO accounts: Problem: Auto-redirect from https://sign-on.security.cisco.com/ to https://id.cisco.com/ is no longer working after email entry. Workaround: Users need to manually select "Other login option" → "Cisco" to access their accounts. Will update as we have more information.

  2. monitoring Dec 11, 2025, 04:13 PM UTC

    A fix has been identified and we are currently monitoring

  3. resolved Dec 11, 2025, 04:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 3, 2025

Updated: Intermittent SCC Login issue

Detected by Pingoru
Dec 03, 2025, 02:01 PM UTC
Resolved
Dec 03, 2025, 04:59 PM UTC
Duration
2h 58m
Affected: User InterfaceSign-On
Timeline · 7 updates
  1. investigating Dec 03, 2025, 02:01 PM UTC

    SCC UI is facing frequent intermittent timeouts. We're looking into the root cause of the issue. We will keep you posted about the progress in issue resolution.

  2. investigating Dec 03, 2025, 03:23 PM UTC

    We are seeing the improvement in our service. And our User Interface & Sign-On are slowly recovering back now.

  3. investigating Dec 03, 2025, 03:28 PM UTC

    We are continuing to investigate this issue.

  4. investigating Dec 03, 2025, 03:56 PM UTC

    We continue to see improved responsiveness in our service.

  5. monitoring Dec 03, 2025, 04:15 PM UTC

    We are observing SCC login functionality is stabilizing. We are currently monitoring our system

  6. monitoring Dec 03, 2025, 04:16 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Dec 03, 2025, 04:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 29, 2025

SCC is currently down on APJC region

Detected by Pingoru
Sep 29, 2025, 05:16 PM UTC
Resolved
Sep 29, 2025, 05:38 PM UTC
Duration
22m
Timeline · 3 updates
  1. identified Sep 29, 2025, 05:16 PM UTC

    Security Cloud control team has identified an issue with SCC in APJC region. SCC currently not available in APJC region

  2. monitoring Sep 29, 2025, 05:32 PM UTC

    We introduced a fix and currently monitoring the health

  3. resolved Sep 29, 2025, 05:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 18, 2025

SMS based authentication issue

Detected by Pingoru
Sep 18, 2025, 12:52 AM UTC
Resolved
Sep 18, 2025, 07:18 AM UTC
Duration
6h 26m
Affected: Sign-On
Timeline · 3 updates
  1. identified Sep 18, 2025, 12:52 AM UTC

    Security cloud control currently experiencing an issue with login to the service via SMS authentication method (MFA). All other multi factor authentication methods are working fine. Team is currently working on implementing a fix

  2. identified Sep 18, 2025, 12:53 AM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Sep 18, 2025, 07:18 AM UTC

    SMS MFA login issue fixed

Read the full incident report →

Notice August 13, 2025

The Unified Assistant in Security Cloud Control is currently experiencing an intermittent issue in all regions

Detected by Pingoru
Aug 13, 2025, 05:48 PM UTC
Resolved
Aug 14, 2025, 01:17 AM UTC
Duration
7h 29m
Timeline · 3 updates
  1. investigating Aug 13, 2025, 05:48 PM UTC

    The Unified Assistant in Security Cloud Control is currently experiencing an intermittent issue in all regions due to an issue with a third-party AI service provider. This prevents the system from generating responses to user requests periodically. We are working on resolving this issue . There are no observed impacts to other Assistants outside of Unified in SCC at this time.

  2. investigating Aug 13, 2025, 08:49 PM UTC

    Team is still investigating the issue and working toward a remediation

  3. resolved Aug 14, 2025, 01:17 AM UTC

    Team implemented a fix and the issue is now resolved

Read the full incident report →

Minor July 22, 2025

All the policies nav under Firewall is missing for all US tenants. SCC UI

Detected by Pingoru
Jul 22, 2025, 05:39 PM UTC
Resolved
Jul 22, 2025, 06:54 PM UTC
Duration
1h 15m
Affected: User Interface
Timeline · 3 updates
  1. investigating Jul 22, 2025, 05:39 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 22, 2025, 06:00 PM UTC

    A fix has been implemented and we are currently monitoring the results

  3. resolved Jul 22, 2025, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 13, 2025

Investigating the Issue

Detected by Pingoru
Jun 13, 2025, 12:45 PM UTC
Resolved
Jun 13, 2025, 01:39 PM UTC
Duration
53m
Affected: User Interface
Timeline · 3 updates
  1. investigating Jun 13, 2025, 12:45 PM UTC

    We are currently experiencing a specific outage on SCC, indicated by the following error: Code 740: Something went wrong on SCC.Our team is working to identify the cause and evaluate the scope of the impact. We will provide more information as soon as it becomes available. Next Update: [Insert timeframe for next update]

  2. investigating Jun 13, 2025, 12:58 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 13, 2025, 01:39 PM UTC

    a fix has been successfully deployed. Issue is now resolved SCC is functioning properly.

Read the full incident report →

Notice December 17, 2024

IDP routing issue - configuration error impacted sign-on

Detected by Pingoru
Dec 17, 2024, 08:59 PM UTC
Resolved
Dec 17, 2024, 07:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 17, 2024, 08:59 PM UTC

    On December 17, 2024, a configuration error on an Identity Provider routing rule resulted in a targeted rule being enforced as a default rule. All systems utilizing Security Cloud Sign On (SCSO) were impacted. This caused a service degradation for customers attempting to authenticate via SCSO. Cisco offers our sincerest apologies for the disruption caused by this incident.

Read the full incident report →