Cycode Outage History

65 incidents recorded over the last 365 days, 65 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Cycode status69.87% uptime history

Every Recorded Cycode Incident

Cycode incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 20, 2026Scan Performance DegredationSummary **Problem:** We observed a delay in processing status updates for GitHub checks due to a backlog in our event processing system. **Impact:** A small number of pull requests (PRs) experienced delays in status…1h 44mResolved
Aug 19, 2026Platform and PR scans slowness**1. Summary** On August 19, 2026, some customers experienced slower page loading and data display, as well as delays when starting or completing pull request scans. The disruption was caused by a managed memory…4h 47mResolved
Aug 18, 2026GitLab incident can affect CycodeGitLab component: Website, API, Git Operations, CI/CD Original GitLab incident: <https://status.gitlab.com/>23h 16mResolved
Aug 18, 2026 Delayed GitHub PR status checksSome GitHub pull request status checks in the EU region were delayed by up to 30 minutes before completing. No checks were lost and no action is needed - delayed checks completed automatically. We identified the…-363 minResolved
Aug 18, 2026Delayed GitHub PR status checksSome GitHub pull request status checks in the EU region were delayed by up to 30 minutes before completing. No checks were lost and no action is needed - delayed checks completed automatically. We identified the…-258 minResolved
Aug 17, 2026GitHub incident can affect CycodeGitHub component: Git Operations, Webhooks, API Requests, Pull Requests Original GitHub incident: https://stspg.io/y1fl26l6wpzr7h 37mResolved
Aug 14, 2026Degraded performance in Secrets Pull Request scanning**Summary** PR secret scans experienced processing lag, causing delays in processing pull requests. The issue was caused by timeouts when calling the model validation service. The model validation service was…2h 32mResolved
Aug 13, 2026GitHub incident can affect CycodeGitHub component: Git Operations, Webhooks, Pull Requests Original GitHub incident: https://stspg.io/f0cgtdc0kqxg45 minResolved
Aug 12, 2026GitHub incident can affect CycodeGitHub component: Pull Requests Original GitHub incident: https://stspg.io/ssd9z8l2g46v16 minResolved
Aug 11, 2026GitHub incident can affect CycodeGitHub component: API Requests Original GitHub incident: https://stspg.io/3xn46bst0bjh5h 14mResolved
Aug 10, 2026We have noticed degraded performance in scanning**Root Cause** The incident was caused by a deployment of one service that ran a database index creation. The team has identified an issue with the way we perform index creations as database migrations. During a…1h 39mResolved
Aug 2, 2026We’re investigating an issue causing older events to be reprocessedThe platform is now fully operational and processing normally39h 59mResolved
Jul 27, 2026Infrastructure upgradeMaintenance has started172h 6mResolved
Jul 27, 2026Degraded performance in scans**Root Cause** The incident was caused by a deployment of one service that ran a database migration. The team has identified that this migration contained faulty code and as a result lead to database overload when…1h 26mResolved
Jul 27, 2026GitHub incident can affect CycodeGitHub component: API Requests Original GitHub incident: https://stspg.io/vr201n49yl5315 minResolved
Jul 24, 2026GitHub incident can affect CycodeGitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj45 minResolved
Jul 24, 2026Degraded performance in IaC Pull Request scansThe issue has been resolved, and we are continuing to monitor the situation.4h 13mResolved
Jul 24, 2026GitHub incident can affect CycodeGitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm531h 19mResolved
Jul 23, 2026GitHub incident can affect CycodeGitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z1h 40mResolved
Jul 20, 2026Infrastructure upgradeMaintenance has started348h 22mResolved
Jul 16, 2026Platform SlownessThe incident has been resolved, and the platform is operating normally.1h 8mResolved
Jul 15, 2026Cycode CLI 3.17.1/2 Secrets scans failuresA fix has been applied and functionality is fully restored; we are continuing to monitor to ensure everything remains stable.1h 45mResolved
Jul 14, 2026Delays in violations status updates in EUWe’re continuing to monitor detection processing and the associated delays in violation status updates (including auto-resolution)5h 10mResolved
Jul 13, 2026Degraded performanceThe system is now fully operational. There should be no more degraded performance. **Summary** We observed a period of slowness and intermittent timeouts affecting various system functions in the EU region…3h 48mResolved
Jul 9, 2026Inaccurate violation counts in some dashboards and panels.Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.198h 4mResolved
Jul 9, 2026Maestro AI service disruptionThe issue affecting Maestro AI services has been resolved. Maestro Risk Explorability, Risk AI Remediation, Maestro Remediation, and Graph AI are now available and operating normally. **Summary** On July 9, 2026…1h 32mResolved
Jul 6, 2026Infrastructure Provisioning DelaysAWS has confirmed that the issue has been fully mitigated and we are currently not observing any related issues.2h 16mResolved
Jul 5, 2026Issues with Violations and Custom Dashboards (Prod-US)Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.11h 23mResolved
Jun 22, 2026SAST, SCA and Secret scans slowness**Summary** During the incident, customers experienced significant delays and temporary disruptions across SAST, SCA, CCA, and Secret repository scans and push events. The issue was caused by a surge in reachability…27h 47mResolved
Jun 18, 2026Workflow Database UpgradeMaintenance has started1115h 57mResolved
Jun 17, 2026Slow SAST PR scansThe issue was resolved. The system is fully stable now40 minResolved
Jun 11, 2026Degraded performance in on demand scans**Summary** During the incident, customers experienced delays and temporary disruptions in on demand scans. The issue was caused by a number of redundant SCA scans as well as unoptimized reachability scans. As a result…24h 14mResolved
Jun 11, 2026Unprocessed Push Event# Summary Between April 14 and April 28, 2026, a processing issue occurred within our scanning workflow that prevented a subset of code update events from being fully processed. As a result, some security findings may…-63361 minResolved
Jun 11, 2026GitLab Incident May Impact Cycode Integrationshttps://status.gitlab.com/1284h 18mResolved
Jun 10, 2026Slow SAST scansThe incident has been resolved. We will provide the RCA shortly.-18941 minResolved
Jun 10, 2026GitHub PR Delays**Summary** Between 16:00 and 17:30 UTC on May 28, we observed an issue where integration connections were intermittently reported as invalid. During this period, the processing of pull requests was paused until…-18962 minResolved
Jun 10, 2026GitHub Authentication Incident Affecting Cycode GitHub Integrations**Summary** On June 10, 2026, customers may have experienced intermittent issues with their GitHub integrations due to an external authentication incident on GitHub's side. This resulted in some integrations temporarily…51 minResolved
Jun 10, 2026Degraded performance in SAST PR scans**Summary** On June 10, 2026, customers may have experienced slowness in SAST Pull Request scanning. The root cause has been identified in insufficient processing capacity in one of the services used in SAST Pull…-59 minResolved
Jun 8, 2026Degraded performance in on demand scans**Summary** During the incident, customers experienced delays and temporary disruptions in scans. The issue was caused by a degraded performance of a process responsible for starting the scans. This means that the…49h 34mResolved
Jun 8, 2026Github incident can affect pr scanninghttps://www.githubstatus.com/incidents/m7n7sm0sr1pz1356h 17mResolved
Jun 2, 2026Slow SCA scans**Summary** Between May 15 and May 28, 2026, a processing delay was identified affecting dependency update workflows for several large accounts. During this period, customers may have experienced significant lag in the…-7201 minResolved
Jun 2, 2026PR Scans Stuck in "Waiting" StatusResolved-26874 minResolved
Jun 2, 2026GitLab Integration — Connection Issue [US]**Summary** On May 8, 2026, a temporary issue within our internal processing system interrupted the routine renewal of GitLab access credentials for a subset of integrations. This caused affected integrations to stop…-35234 minResolved
Jun 1, 2026Partial Service Disruption in EU Environment **Summary** On May 5, 2026, customers in the EU region experienced issues with Custom Dashboards not loading as expected, and some filtering/grouping actions were slower than usual on the Violations page. The issue was…-38881 minResolved
Jun 1, 2026GitHub PR Delays-5934 minResolved
Jun 1, 2026Slow SAST scans-5761 minResolved
Jun 1, 2026Slow SCA scansSummary Between May 15 and May 28, 2026, a processing delay was identified affecting dependency update workflows for several large accounts. During this period, customers may have experienced significant lag in the…-14401 minResolved
May 11, 2026GitLab Webhook Processing Failure Due to Time Format ChangeA fix supporting both the old and new formats was deployed at 13:00 IST.-8885 minResolved
May 3, 2026Short service interruptionThe incident has been resolved.-18638 minResolved
May 3, 2026Short service interruptionThe incident has been resolved.-7219 minResolved
May 3, 2026Slow CLI scansThe incident has been resolved.-27463 minResolved
May 3, 2026Slow Pull request and CLI scans**Summary** Customers may have experienced general slowness when performing CLI scans across all scan types. This issue was caused by a bug in a newly introduced feature that impacted the efficiency of the scan…-28608 minResolved
May 3, 2026Increase SAST violations**Summary** Between April 10 and April 14, 2026, some customers saw SAST scans and findings generated for branches that were not included in their configured branch-scanning settings. This resulted in unexpected…-27496 minResolved
May 3, 2026Platform SlownessThe issue has been resolved-57204 minResolved
May 3, 2026Slowness in CLI Secret ScansThe issue has been resolved. We will share the RCA document as soon as it is completed.-88701 minResolved
May 3, 2026Legacy Token authentication failure after system authentication updateSummary Between February 16 and 17, 2026, some customers using older API tokens experienced authentication failures. These tokens, originally created before a recent system update, could not be used to access services…-107846 minResolved
May 3, 2026Platform SlownessThe issue has been resolved. We will share the RCA document as soon as it is completed.-88691 minResolved
May 3, 2026Delay in PR scans for Github Pull RequestsThe issue has been resolved and scanning is operating normally. We will continue monitoring to ensure stability.-94673 minResolved
May 3, 2026IaC PR Scanning Delays-97494 minResolved
May 3, 2026Delay in risk score calculation and visibility of violations in the graph.-93569 minResolved
May 3, 2026Delays in CLI, PushEvents and Repositories Scans (SAST, Container and SCA)-430230 minResolved
May 3, 2026Repository Detections Has Been Auto Resolve Upon Branch Deletion-450671 minResolved
Feb 1, 2026Slowness and Incorrect Data on Inventory, Discovery and Reports Pages-414571 minResolved
Feb 1, 2026Degraded Performance in SCA Scans-10626 minResolved
Feb 1, 2026Delayed SAST PR-27692 minResolved

How to Read This Cycode Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cycode acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Cycode outage in this window ran 56d 12h, against a mean recovery of 5d 18h. If you depend on Cycode in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.