Cycode Outage History

Cycode is up right now

Cycode had 16 outages in the last 2 years totaling 288h 35m of downtime — averaging 0.7 incidents per month.

There were 16 Cycode outages since February 16, 2026 totaling 288h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cycode.com

Minor May 6, 2026

GitHub Pull Request Service Incident

Detected by Pingoru
May 06, 2026, 06:59 PM UTC
Resolved
May 06, 2026, 07:18 PM UTC
Duration
19m
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 2 updates
  1. investigating May 06, 2026, 06:59 PM UTC

    https://www.githubstatus.com/incidents/f5pb5d5mr9yh

  2. resolved May 06, 2026, 07:18 PM UTC

    Resolved

Read the full incident report →

Minor May 4, 2026

GitLab Webhook Processing Failure Due to Time Format Change

Detected by Pingoru
May 04, 2026, 09:00 PM UTC
Resolved
May 05, 2026, 10:00 AM UTC
Duration
13h
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 1 update
  1. investigating May 05, 2026, 11:53 AM UTC

    GitLab recently changed the time format in some of their webhooks, which caused our webhook processing to fail starting at 00:00 IST. As a result, some webhook events were not processed successfully. A fix supporting both the old and new formats was deployed at 13:00 IST.

Read the full incident report →

Minor April 28, 2026

Short service interruption

Detected by Pingoru
Apr 28, 2026, 12:38 PM UTC
Resolved
Apr 28, 2026, 01:30 PM UTC
Duration
52m
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)
Timeline · 1 update
  1. investigating Apr 28, 2026, 01:38 PM UTC

    Between 15:40 and 16:30 (IDT), some users in the EU region may have experienced intermittent issues accessing the service. The issue has been identified and resolved, and the service is now fully operational.

Read the full incident report →

Minor April 27, 2026

Unprocessed Push Events

Detected by Pingoru
Apr 27, 2026, 09:00 PM UTC
Resolved
Apr 28, 2026, 09:00 AM UTC
Duration
12h
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 1 update
  1. investigating May 06, 2026, 11:10 AM UTC

    Between 14.04.2026 and 28.04.2026, a small portion of push events were not processed correctly. As a result, some violations were not resolved as expected. The underlying issue has been identified and resolved. We are currently performing a retroactive data correction process to ensure all affected violations are updated accordingly.

Read the full incident report →

Minor April 14, 2026

Slow CLI scans

Detected by Pingoru
Apr 14, 2026, 09:30 AM UTC
Resolved
Apr 14, 2026, 11:30 AM UTC
Duration
2h
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 1 update
  1. investigating Apr 14, 2026, 08:50 PM UTC

    We have noticed general slowness in CLI scans for all scan types. We have found the root cause as a bug in newly introduced feature and resolved the underlying issue.

Read the full incident report →

Minor April 13, 2026

Slow Pull request and CLI scans

Detected by Pingoru
Apr 13, 2026, 01:20 PM UTC
Resolved
Apr 14, 2026, 11:30 AM UTC
Duration
22h 10m
Affected: US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 1 update
  1. investigating Apr 14, 2026, 01:46 PM UTC

    We have noticed general slowness in Pull Request and CLI scans. We have found the root cause in round-robin load balancing which we have solved by increasing the number of node to handle the load and the size of the nodes.

Read the full incident report →

Minor April 10, 2026

Increase SAST violations

Detected by Pingoru
Apr 10, 2026, 06:30 AM UTC
Resolved
Apr 14, 2026, 10:48 AM UTC
Duration
4d 4h
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 1 update

Read the full incident report →

Minor March 24, 2026

Platform Slowness

Detected by Pingoru
Mar 24, 2026, 03:47 PM UTC
Resolved
Mar 24, 2026, 07:29 PM UTC
Duration
3h 42m
Affected: US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 3 updates
  1. investigating Mar 24, 2026, 03:47 PM UTC

    We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.

  2. monitoring Mar 24, 2026, 04:28 PM UTC

    The system is operating normally, and we are continuing to monitor closely.

  3. resolved Mar 24, 2026, 07:29 PM UTC

    The issue has been resolved. We will share the RCA document as soon as it is completed.

Read the full incident report →

Minor March 16, 2026

Github's incident can affect Cycode PR scanning

Detected by Pingoru
Mar 16, 2026, 03:14 PM UTC
Resolved
Mar 17, 2026, 09:03 AM UTC
Duration
17h 49m
Affected: EU EnvironmentAPI (EU Environment)Application/UI (EU Environment)US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 2 updates
  1. investigating Mar 16, 2026, 03:14 PM UTC

    https://www.githubstatus.com/incidents/2lh36qcrd7l6

  2. resolved Mar 17, 2026, 09:03 AM UTC

    Resolved

Read the full incident report →

Minor March 2, 2026

Slowness in CLI Secret Scans

Detected by Pingoru
Mar 02, 2026, 08:49 PM UTC
Resolved
Mar 02, 2026, 09:37 PM UTC
Duration
48m
Affected: US EnvironmentAPI (US Environment)
Timeline · 3 updates
  1. investigating Mar 02, 2026, 08:49 PM UTC

    We’re investigating reports of slowness in CLI Secret scans.

  2. monitoring Mar 02, 2026, 09:03 PM UTC

    A fix has been applied to address the slowness in CLI Secret Scans. We are continuing to monitor the situation.

  3. resolved Mar 02, 2026, 09:37 PM UTC

    The issue has been resolved. We will share the RCA document as soon as it is completed.

Read the full incident report →

Minor February 26, 2026

Delay in PR scans for Github Pull Requests

Detected by Pingoru
Feb 26, 2026, 04:23 PM UTC
Resolved
Feb 26, 2026, 05:41 PM UTC
Duration
1h 17m
Affected: US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 2 updates
  1. monitoring Feb 26, 2026, 04:23 PM UTC

    We identified delays in scanning GitHub pull requests. Service has been restored and we are continuing to monitor to confirm stability.

  2. resolved Feb 26, 2026, 05:41 PM UTC

    The issue has been resolved and scanning is operating normally. We will continue monitoring to ensure stability.

Read the full incident report →

Minor February 24, 2026

IaC PR Scanning Delays

Detected by Pingoru
Feb 24, 2026, 11:39 AM UTC
Resolved
Feb 24, 2026, 06:37 PM UTC
Duration
6h 58m
Affected: US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 3 updates
  1. investigating Feb 24, 2026, 11:39 AM UTC

    We are currently investigating delays in Infrastructure as Code (IaC) PR scanning. Some users may experience longer than expected wait times for scan results on pull/merge requests containing IaC changes.

  2. monitoring Feb 24, 2026, 12:23 PM UTC

    We have applied a workaround and the service is back processing the backlog. Scan results may still be delayed as the queue drains. We are actively monitoring and continuing to investigate the root cause.

  3. resolved Feb 24, 2026, 06:37 PM UTC

    The backlog has been fully processed and IaC PR scanning is operating normally. A fix has been deployed to prevent recurrence. We will continue monitoring.

Read the full incident report →

Minor February 23, 2026

Delay in risk score calculation and visibility of violations in the graph.

Detected by Pingoru
Feb 23, 2026, 02:47 PM UTC
Resolved
Feb 27, 2026, 12:00 PM UTC
Duration
3d 21h
Affected: US EnvironmentAPI (US Environment)Application/UI (US Environment)
Timeline · 3 updates
  1. investigating Feb 23, 2026, 02:47 PM UTC

    We are currently investigating the issue and will provide updates soon.

  2. monitoring Feb 25, 2026, 04:06 PM UTC

    Root cause identified and fix delivered. Processing and syncing are in progress, and completion is expected shortly. We’ll share a final update once fully resolved

  3. resolved Feb 27, 2026, 12:00 PM UTC

    The issue is fully resolved and all items have been processed. No further impact is expected.

Read the full incident report →