https://approjects-vendor-status-watch.static.hf.space/v/cycode.htmlIncidents from Cycode's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://status.cycode.comcycode:2026-09-13T10:36:50ZSun, 13 Sep 2026 10:36:50 +0000Resolved https://status.cycode.comcycode:2026-09-08T16:53:36ZTue, 08 Sep 2026 16:53:36 +0000MemoryDB metrics are stable, the processing lag has recovered, and the system is now fully operational.https://status.cycode.comcycode:2026-09-08T09:53:50ZTue, 08 Sep 2026 09:53:50 +0000The system is back to being fully operational.https://status.cycode.comcycode:2026-09-01T15:10:38ZTue, 01 Sep 2026 15:10:38 +0000GitHub component: Pull Requests Original GitHub incident: https://stspg.io/0xbhhq84v4mthttps://status.cycode.comcycode:2026-08-26T23:04:59ZWed, 26 Aug 2026 23:04:59 +0000GitHub component: Pull Requests Original GitHub incident: https://stspg.io/nrbwjftcz72dhttps://status.cycode.comcycode:2026-08-20T14:52:37ZThu, 20 Aug 2026 14:52:37 +0000The system is back to being fully operational.https://status.cycode.comcycode:2026-08-19T13:18:38ZWed, 19 Aug 2026 13:18:38 +0000**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 database entering a repeated restart cycle and not recovering automatically. This created a temporary slowdown in processing. Expected service behavior was restored after corrective actions, including replacement and increased capacity for the affected service. The provider is continuing to investigate why the service was unable to return to normal operation automatically. **2. Key Timeline (IDT)** • August 19, 2026, 16:10 IDT: We identified performance degradation affecting parts of the platform and pull request scanning. • August 19, 2026, 16:30 IDT: An initial corrective chttps://status.cycode.comcycode:2026-08-18T14:34:21ZTue, 18 Aug 2026 14:34:21 +0000 Some 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 cause, and fixed it. We're monitoring closely.https://status.cycode.comcycode:2026-08-17T13:44:06ZMon, 17 Aug 2026 13:44:06 +0000GitHub component: Git Operations, Webhooks, API Requests, Pull Requests Original GitHub incident: https://stspg.io/y1fl26l6wpzrhttps://status.cycode.comcycode:2026-08-14T13:41:27ZFri, 14 Aug 2026 13:41:27 +0000**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 experiencing elevated latency and errors because compute nodes were scheduled on a subnet that had exhausted its available IPs. This slowed PR secret scan processing and caused consumer lag to build up. To resolve the issue, we temporarily disabled the feature that produces new PR secret scans so the queue could drain. We also resolved the underlying infrastructure issue by moving nodes to subnets with available free IPs. **Customer Impact** Customers experienced delayed PR secret scans. Other scan types remained operational. **Root Cause** The secret scanner calls the AI modhttps://status.cycode.comcycode:2026-08-13T14:53:48ZThu, 13 Aug 2026 14:53:48 +0000GitHub component: Git Operations, Webhooks, Pull Requests Original GitHub incident: https://stspg.io/f0cgtdc0kqxghttps://status.cycode.comcycode:2026-08-12T16:25:59ZWed, 12 Aug 2026 16:25:59 +0000GitHub component: Pull Requests Original GitHub incident: https://stspg.io/ssd9z8l2g46vhttps://status.cycode.comcycode:2026-08-11T14:55:27ZTue, 11 Aug 2026 14:55:27 +0000GitHub component: API Requests Original GitHub incident: https://stspg.io/3xn46bst0bjhhttps://status.cycode.comcycode:2026-08-10T14:06:34ZMon, 10 Aug 2026 14:06:34 +0000**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 deployment the pods with newest image of the service attempted to create an index on a big table. The team has identified that the index creation took 7 minutes. However, during index creation pods were not responsive, and as a result, Kubernetes deemed them as unhealthy pods and attempted to retry those pods after 5 minutes. As a result, because the pod got killed before the index creation was fully completed, the database transaction was rolled back. Then, subsequent pods attempted to create the index again, dying after 5 minutes. This lead to the database being in unhealthyhttps://status.cycode.comcycode:2026-08-02T14:08:56ZSun, 02 Aug 2026 14:08:56 +0000The platform is now fully operational and processing normallyhttps://status.cycode.comcycode:2026-07-27T10:31:15ZMon, 27 Jul 2026 10:31:15 +0000**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 attempting to deploy the service. As a result, the service was partially down until the deployment was reverted. During this time, all scans were processed with lower than expected performance.https://status.cycode.comcycode:2026-07-27T03:56:45ZMon, 27 Jul 2026 03:56:45 +0000GitHub component: API Requests Original GitHub incident: https://stspg.io/vr201n49yl53https://status.cycode.comcycode:2026-07-24T19:40:50ZFri, 24 Jul 2026 19:40:50 +0000GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vjhttps://status.cycode.comcycode:2026-07-24T17:45:35ZFri, 24 Jul 2026 17:45:35 +0000The issue has been resolved, and we are continuing to monitor the situation.https://status.cycode.comcycode:2026-07-24T16:21:08ZFri, 24 Jul 2026 16:21:08 +0000GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53https://status.cycode.comcycode:2026-07-23T07:58:43ZThu, 23 Jul 2026 07:58:43 +0000GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84zhttps://status.cycode.comcycode:2026-07-16T18:56:47ZThu, 16 Jul 2026 18:56:47 +0000The incident has been resolved, and the platform is operating normally.https://status.cycode.comcycode:2026-07-15T17:22:05ZWed, 15 Jul 2026 17:22:05 +0000A fix has been applied and functionality is fully restored; we are continuing to monitor to ensure everything remains stable.https://status.cycode.comcycode:2026-07-14T16:12:50ZTue, 14 Jul 2026 16:12:50 +0000We’re continuing to monitor detection processing and the associated delays in violation status updates (including auto-resolution)https://status.cycode.comcycode:2026-07-13T08:47:48ZMon, 13 Jul 2026 08:47:48 +0000The 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, including the application interface and pull request (PR) scans. The issue was primarily caused by a processing system reaching its network and memory capacity limits, exacerbated by a high volume of automated activity from a single source. We have since upgraded the underlying infrastructure and implemented safeguards to prevent similar high-volume activity from impacting the system. The issue is now fully resolved, and all services have returned to expected performance levels. **Key Timeline (IDT)** • **July 13, 2026, 11:44 IDT**: Incident detected following reports of UI slownehttps://status.cycode.comcycode:2026-07-09T10:54:26ZThu, 09 Jul 2026 10:54:26 +0000Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.https://status.cycode.comcycode:2026-07-09T09:07:18ZThu, 09 Jul 2026 09:07:18 +0000The 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, customers using the Maestro service in the European production environment experienced a period of service unavailability. The issue began following a configuration update that inadvertently changed the service's regional routing. This caused the system to attempt connections through a network path that lacked the necessary permissions and to a region where specific processing models were unavailable. The issue has been fully resolved, and service has been restored to all affected customers. **Key Timeline (IDT)** • **July 9, 2026, 12:02 IDT:** The incident was identified ahttps://status.cycode.comcycode:2026-07-06T12:52:03ZMon, 06 Jul 2026 12:52:03 +0000AWS has confirmed that the issue has been fully mitigated and we are currently not observing any related issues.