Is Cycode down?

Last checked 2m ago
Current status
Cycode is up

No active incidents. All 52 components operational.

  • Official status page: status.cycode.com
  • Checked every 5 minutes
  • 52 components tracked

Cycode is operational right now. Last checked 2m ago; the most recent incident resolved 2d ago.

Real-time Cycode status, recent outages, and incident history: pulled directly from Cycode's official status page at status.cycode.com every 5 minutes. Pingoru tracks 52 Cycode services and has captured 18 incidents in the last 90 days (99.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Cycode reports a new incident, free for 3 monitors, no credit card.

Users who monitor Cycode also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 8,000+ providers
Cycode uptime 99.83% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 15h 36m
    Started Nov 16, 2026, 02:31 PM UTC · Resolved Nov 17, 2026, 06:07 AM UTC
    US EnvironmentUS Environment
    Timeline · 6 updates
    • investigating · Nov 16, 2026, 02:22 PM UTC

      We are investigating delays in Cycode CLI scan results in the US region. Secret scans of commit ranges are the most affected. CLI scans can take longer than usual to complete. Pull request scans and other platform features work as usual. Our team is working on a fix.

    • investigating · Nov 16, 2026, 02:26 PM UTC

      We are investigating delays in Cycode CLI scan results in the US region. Secret scans of commit ranges are the most affected. CLI scans can take longer than usual to complete. Pull request scans and other platform features work as usual. Our team is working on a fix.

    • investigating · Nov 16, 2026, 02:31 PM UTC

      We are investigating delays in Cycode CLI scan results in the US region. Secret scans of commit ranges are the most affected. CLI scans can take longer than usual to complete. Pull request scans and other platform features work as usual. Our team is working on a fix.

    • identified · Nov 16, 2026, 03:07 PM UTC

      We identified the cause of the delayed CLI scan results in the US region: an unusually high volume of CLI scans. Only secret scans of commit ranges and IaC CLI scans were affected. We deployed a fix and increased our processing capacity. New secret scans of commit ranges now complete normally. Some secret scans of commit ranges that started earlier during the incident can still be delayed, and IaC CLI scans can still take longer than usual. Pull request scans were not affected.

    • monitoring · Nov 16, 2026, 04:00 PM UTC

      New CLI scans in the US region, including secret commit-range and IaC scans, now complete without delay. Secret commit-range scans that started earlier during the incident can still be delayed. We continue to monitor the system.

    • resolved · Nov 17, 2026, 06:07 AM UTC

      The issue has been resolved. We will continue to monitor the situation.

    Latest: The issue has been resolved. We will continue to monitor the situation.

  2. Resolved 5h 33m
    Started Nov 16, 2026, 12:43 PM UTC · Resolved Nov 16, 2026, 06:16 PM UTC
    GitHub
    Timeline · 2 updates
    • investigating · Nov 16, 2026, 12:43 PM UTC

      GitHub component: Pull Requests Original GitHub incident: https://www.githubstatus.com/incidents/2zfqmghmg3s3

    • resolved · Nov 16, 2026, 06:16 PM UTC

      Resolved

    Latest: Resolved

  3. Resolved 5h 6m
    Started Nov 10, 2026, 04:24 PM UTC · Resolved Nov 10, 2026, 09:30 PM UTC
    GitHub
    Timeline · 2 updates
    • investigating · Nov 10, 2026, 04:24 PM UTC

      GitHub component: Operations and Pull Requests Original GitHub incident: https://www.githubstatus.com/incidents/hnf21m9jkl3c

    • resolved · Nov 10, 2026, 05:55 PM UTC

      Resolved

    Latest: Resolved

  4. Resolved 3h 46m
    Started Nov 09, 2026, 10:31 AM UTC · Resolved Nov 09, 2026, 02:18 PM UTC
    GitHub
    Timeline · 2 updates
    • investigating · Nov 09, 2026, 10:31 AM UTC

      GitHub component: Webhooks and Actions Original GitHub incident: https://stspg.io/0xbhhq84v4mt: https://www.githubstatus.com/incidents/xxb3l2bm76dr

    • resolved · Nov 09, 2026, 02:18 PM UTC

      Resolved

    Latest: Resolved

  5. Resolved 17h 29m
    Started Nov 06, 2026, 12:14 PM UTC · Resolved Nov 07, 2026, 05:44 AM UTC
    US Environment
    Timeline · 3 updates
    • investigating · Nov 06, 2026, 12:14 PM UTC

      Analytical views may display outdated violation data. The Group by None view remains up to date and unaffected

    • monitoring · Nov 06, 2026, 01:22 PM UTC

      We identified the issue and applied a fix. The analytical views are now catching up with the latest data. We will continue monitoring until the data is fully up to date

    • resolved · Nov 06, 2026, 08:44 PM UTC

      The issue that delayed updates to some detections has been fixed, all pending updates have been processed

    Latest: The issue that delayed updates to some detections has been fixed, all pending updates have been processed

See the full Cycode outage history

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

Browse Cycode outage history →

Or sign up free to get alerts when Cycode breaks · 3 free monitors · No credit card

Incident record

Since April 2026 · incident.io · 52 components checked every 5 minutes
57incidents recorded
57last 12 months
18last 90 days
21 hourstypical duration, 12 months

The longest incident in the last year, Issues with Violations and Custom Dashboards (Prod-US) on July 5, 2026, ran for 12 days. 7 maintenance windows announced in the same period.

How Cycode compares

Cycode reported more incidents in the last 12 months than 537 of the 570 other Security services Pingoru tracks. The typical one reported 5. Its incidents typically last 21 hours; across Security services the typical figure is 7 hours. Counts come from each vendor's own status page, so a vendor that reports openly can show more incidents than one that does not.

How quickly Cycode posts incidents

20% of the 10 Cycode incidents Pingoru saw in the last 12 months first appeared on its status page more than 15 minutes after the start time Cycode gave them. Half appeared within 5 minutes. For the typical Security service, half appear within 5 minutes. Pingoru checks every 5 minutes, so a gap can read up to 5 minutes longer than the vendor's own delay.

Platforms Cycode names in its incidents

In the last 12 months Cycode named these platforms in the titles of its own incidents.

Most affected components, last 12 months

  • GitHub12
  • US Environment (PR Scanning & Developer Tools)8
  • US Environment (Web Application)4
  • US Environment (Secrets & Leaks)3
  • EU Environment2

Latest incidents

  • Delayed CLI scan results in the US region November 16, 2026 · 16 hours · degraded service

    We are investigating delays in Cycode CLI scan results in the US region. Secret scans of commit ranges are the most affected. CLI scans can take longer than…

  • GitHub incident can affect Cycode November 16, 2026 · 6 hours · degraded service

    GitHub component: Pull Requests Original GitHub incident: https://www.githubstatus.com/incidents/2zfqmghmg3s3

  • GitHub incident can affect Cycode November 10, 2026 · 5 hours · degraded service

    GitHub component: Operations and Pull Requests Original GitHub incident: https://www.githubstatus.com/incidents/hnf21m9jkl3c

Outage history

Past 90 days · 22 incidents View full outage history →