GitHub Pull Request Service Incident
Timeline · 2 updates
- investigating May 06, 2026, 06:59 PM UTC
https://www.githubstatus.com/incidents/f5pb5d5mr9yh
- resolved May 06, 2026, 07:18 PM UTC
Resolved
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.
https://www.githubstatus.com/incidents/f5pb5d5mr9yh
Resolved
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.
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.
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.
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.
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.
We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.
The system is operating normally, and we are continuing to monitor closely.
The issue has been resolved. We will share the RCA document as soon as it is completed.
https://www.githubstatus.com/incidents/2lh36qcrd7l6
Resolved
We’re investigating reports of slowness in CLI Secret scans.
A fix has been applied to address the slowness in CLI Secret Scans. We are continuing to monitor the situation.
The issue has been resolved. We will share the RCA document as soon as it is completed.
We identified delays in scanning GitHub pull requests. Service has been restored and we are continuing to monitor to confirm stability.
The issue has been resolved and scanning is operating normally. We will continue monitoring to ensure stability.
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.
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.
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.
We are currently investigating the issue and will provide updates soon.
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
The issue is fully resolved and all items have been processed. No further impact is expected.