Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 24, 2026 · 12:25 IDT Scheduled
We will be performing scheduled infrastructure upgrades this Sunday. 
No downtime is expected during this maintenance window. However, users may experience intermittent disruptions or temporary performance degradation while the upgrades are in progress.

Infrastructure Upgrades

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 22, 2026 · 11:29 IDT Issue
We are seeing latency in SCA scans. On demand scans may take longer time to complete. Pull request scans are not affected.

Slow SCA scans

Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 16, 2026 · 22:00 IDT Scheduled
We will be performing scheduled infrastructure upgrades this Sunday. 
No downtime is expected during this maintenance window. However, users may experience intermittent disruptions or temporary performance degradation while the upgrades are in progress.

Minor incident - US Environment, Application/UI (US Environment)May 14, 2026 · 22:10 IDT Update
The underlying issue has been resolved. New PRs and manually retriggered PR scans will now work correctly — statuses should report back to GitHub as expected.

For the PRs that were affected during the incident window, we’re investigating whether there’s a way to retrigger those scans automatically on our side. We’re not yet sure if that will be possible, so in the meantime the safest path is to manually retrigger any affected PR scans from your end.
<hr>May 14, 2026 · 21:42 IDT Issue
We are currently investigating an issue where PR scans for customers using the Cycode broker are completing on our side but remaining in a “Waiting” status on the SCM.

Initial investigation points to an availability issue with our broker server. Our engineering team is actively working on a fix and will post an update shortly.

PR Scans Stuck in "Waiting" Status

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 11, 2026 · 18:16 IDT Resolved
Resolved
<hr>May 11, 2026 · 17:41 IDT Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/81b05nqkhylj">https://www.githubstatus.com/incidents/81b05nqkhylj</a>

GitHub incident — may affect PR scans.

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)May 10, 2026 · 18:29 IDT Issue
We identified an issue that caused some GitLab integrations to become invalid between 8 May, 20:00 and 9 May, 01:00. Affected integrations need to be reconnected to resume working.

We are working with our infrastructure provider to investigate the root cause and to put safeguards in place to prevent this from happening again.

We will share an update as soon as we have more information. 
We have identified the affected customers and will be reaching out to them directly with next steps. If you have not been contacted, your integration is not affected.

GitLab Integration — Connection Issue [US]

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 6, 2026 · 22:18 IDT Resolved
Resolved
<hr>May 6, 2026 · 21:59 IDT Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/f5pb5d5mr9yh">https://www.githubstatus.com/incidents/f5pb5d5mr9yh</a>

GitHub Pull Request Service Incident

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment)May 18, 2026 · 10:30 IDT Post-mortem
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 caused by a configuration update that included an invalid setting, which prevented the EU analytics data service from operating normally. The service was restored the same evening, and we confirmed no data was lost.

Key Timeline (IDT)

May 5, 2026, 16:51 IDT – A configuration update was deployed to the EU production environment. 
May 5, 2026, 19:06 IDT – Monitoring detected availability issues and alerts were triggered. 
May 5, 2026, 19:23 IDT – Investigation began. 
May 5, 2026, 19:36 IDT – The invalid configuration was identified and confirmed as the cause. 
May 5, 2026, 19:40 IDT – A controlled recovery approach was planned to ensure data integrity throughout remediation. 
May 5, 2026, 19:50 IDT – Additional safeguards and validation steps were performed prior to remediation, including recovery validation in a non-production environment. 
May 5, 2026, 21:45 IDT – A safe recovery procedure was confirmed. 
May 5, 2026, 22:05 IDT – Production service was recovered and data accessibility was confirmed.

Root Cause

A configuration update introduced an invalid resource value. While the change initially appeared to apply successfully, it caused repeated failures in the automated update process responsible for keeping the service healthy. After continuing to fail, the process removed the running service components associated with the EU analytics service, leading to service unavailability for customers until restoration was completed.

Actions Taken
<ul>
 <li>
Investigated alerts and isolated the problematic configuration change. </li>
 <li>
Performed additional safeguards and validation steps prior to remediation. </li>
 <li>
Validated recovery steps in a non-production environment before applying them in production. </li>
 <li>
Restored service by safely reattaching existing storage and returning processing to normal operation. </li>
 <li>
Confirmed service availability and verified that data remained intact. </li>
</ul>

Action Items
<ul>
 <li>
Add stronger pre-deployment validation to catch malformed configuration values before rollout. </li>
 <li>
Improve monitoring and alerting to detect repeated update failures and destructive actions earlier. </li>
 <li>
Implement safeguards to prevent automated update workflows from removing stateful resources for this analytics service during invalid update scenarios. </li>
 <li>
Improve operational logging and visibility to speed up diagnosis during similar events. </li>
 <li>
Expand and regularly validate backup/restore coverage for the affected analytics stateful components. </li>
</ul>
<hr>May 5, 2026 · 23:18 IDT Resolved
The issue has been resolved, and all services are now operating normally. 
A detailed RCA will be provided soon.
<hr>May 5, 2026 · 20:48 IDT Issue
We are currently experiencing a service disruption affecting our EU environment.

What’s impacted:
<ul>
 <li>
Custom Dashboards are temporarily unavailable </li>
 <li>
Some filtering capabilities on the Violations page may be slower than usual </li>
</ul>

Current status: 
Our team has identified the issue and is actively working to restore full functionality. All data remains safe.

Next update: 
We will continue to share updates as we make progress.

Partial Service Disruption in EU Environment

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 5, 2026 · 14:53 IDT Issue
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.

GitLab Webhook Processing Failure Due to Time Format Change

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment)April 28, 2026 · 16:38 IDT Issue
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.

Short service interruption

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)May 6, 2026 · 14:10 IDT Issue
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.

Unprocessed Push Events

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment)April 20, 2026 · 18:57 IDT Issue
Between 17:57 and 18:12, 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.

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)April 14, 2026 · 23:50 IDT Issue
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.

Slow CLI scans

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)April 14, 2026 · 16:46 IDT 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.

Slow Pull request and CLI scans

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)April 28, 2026 · 17:18 IDT Issue
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 findings, including duplicates and false positives, appearing in the product. The issue was caused by a recent update to the branch-scanning control logic that did not correctly apply customers’ branch configuration during that period. The scanning behavior was corrected on April 14, 2026, and the incident was fully resolved on April 27, 2026 after the unintended findings were removed.

Key Timeline (IDT)
<ul>
 <li>
April 10, 2026, 09:33 IDT — A production update introduced incorrect handling of branch-scanning configuration for some SAST events. </li>
 <li>
April 14, 2026, 13:48 IDT — A subsequent update restored expected enforcement of configured branch-scanning rules. </li>
 <li>
April 21, 2026, 19:00 IDT — Customer reports alerted us to unexpected SAST findings on non-configured branches. </li>
 <li>
April 22, 2026, 13:52 IDT — Root cause identified; scope assessment initiated. </li>
 <li>
April 23, 2026, 18:13 IDT — Impact analysis tooling executed to identify affected data and tenants. </li>
 <li>
April 27, 2026, 14:30 IDT — Cleanup completed; unintended findings removed and incident fully remediated. </li>
</ul>

Root Cause 
A product update introduced an issue in the branch-scanning configuration check, causing the system to create SAST scans for branches outside of customer-defined scanning rules for a limited period (April 10–14). These extra scans produced unintended findings, which became visible to customers as additional or duplicate items.

Actions Taken
<ol>
 <li>
Restored correct enforcement of customers’ configured branch-scanning rules. </li>
 <li>
Assessed the scope of the impact across affected environments. </li>
 <li>
Removed unintended SAST findings created for non-configured branches. </li>
 <li>
Confirmed expected behavior after cleanup. </li>
</ol>

Action Items
<ol>
 <li>
Improve validation and safeguards around branch-scanning configuration checks during updates. </li>
 <li>
Enhance monitoring to detect unexpected increases in scan volume or findings. </li>
 <li>
Strengthen release checks for feature-gated behavior to prevent similar regressions. </li>
</ol>

Increase SAST violations

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)March 24, 2026 · 21:29 IST Resolved
The issue has been resolved. We will share the RCA document as soon as it is completed.
<hr>March 24, 2026 · 18:28 IST Monitoring
The system is operating normally, and we are continuing to monitor closely.
<hr>March 24, 2026 · 17:47 IST Issue
We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.

Platform Slowness

Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 19, 2026 · 18:17 IST Scheduled
We will be performing scheduled infrastructure upgrades this Sunday. 
No downtime is expected during this maintenance window. However, users may experience intermittent disruptions or temporary performance degradation while the upgrades are in progress.

Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 12, 2026 · 17:58 IST Scheduled
We will be performing scheduled infrastructure upgrades this Sunday. 
No downtime is expected during this maintenance window. However, users may experience intermittent disruptions or temporary performance degradation while the upgrades are in progress.

Minor incident - US Environment, API (US Environment)March 2, 2026 · 23:37 IST Resolved
The issue has been resolved. We will share the RCA document as soon as it is completed.
<hr>March 2, 2026 · 23:03 IST Monitoring
A fix has been applied to address the slowness in CLI Secret Scans. We are continuing to monitor the situation.
<hr>March 2, 2026 · 22:49 IST Investigating
We’re investigating reports of slowness in CLI Secret scans.

Slowness in CLI Secret Scans

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)March 2, 2026 · 23:26 IST Resolved
The issue has been resolved. We will share the RCA document as soon as it is completed.
<hr>March 2, 2026 · 22:39 IST Update
We have increased the replicas of our UI component. We are still checking for the root cause. 
<hr>March 2, 2026 · 22:19 IST Issue
We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 3, 2026 · 10:27 IST Resolved
This incident has been resolved
<hr>March 2, 2026 · 23:27 IST Update
<a target="_blank" href="https://www.githubstatus.com/incidents/vhpmx9vc93m0">https://www.githubstatus.com/incidents/vhpmx9vc93m0</a> 
Update - We’re deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes. 
Mar 02, 2026 - 21:04 UTC
<hr>March 2, 2026 · 22:15 IST Issue
An ongoing GitHub incident may affect pull request operations. We are monitoring the situation.

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)February 26, 2026 · 19:41 IST Resolved
The issue has been resolved and scanning is operating normally. 
We will continue monitoring to ensure stability.
<hr>February 26, 2026 · 18:23 IST Monitoring
We identified delays in scanning GitHub pull requests. 
Service has been restored and we are continuing to monitor to confirm stability.

Delay in PR scans for Github Pull Requests

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)February 24, 2026 · 20:37 IST Resolved
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.
<hr>February 24, 2026 · 14:23 IST Monitoring
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.
<hr>February 24, 2026 · 13:39 IST Issue
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.

IaC PR Scanning Delays

Minor incident - US Environment, API (US Environment), Application/UI (US Environment)February 27, 2026 · 14:00 IST Resolved
The issue is fully resolved and all items have been processed. No further impact is expected.
<hr>February 25, 2026 · 18:06 IST Monitoring
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
<hr>February 23, 2026 · 16:47 IST Issue
We are currently investigating the issue and will provide updates soon.

Is Cycode down?

Cycode status is DEGRADED

Components with issues

Lastest published events

Infrastructure Upgrades

Slow SCA scans

Partial Service Disruption in EU Environment

Cycode Services, Components and Regions

Recent Cycode events

Infrastructure Upgrades

Slow SCA scans

Infrastructure Upgrades

PR Scans Stuck in "Waiting" Status

GitHub incident — may affect PR scans.

GitLab Integration — Connection Issue [US]

Get your FREE account now,
5 monitors included!

Is Cycode down?

Cycode status is DEGRADED

Components with issues

Lastest published events

Infrastructure Upgrades

Slow SCA scans

Partial Service Disruption in EU Environment

Cycode Services, Components and Regions

Recent Cycode events

Infrastructure Upgrades

Slow SCA scans

Infrastructure Upgrades

PR Scans Stuck in "Waiting" Status

GitHub incident — may affect PR scans.

GitLab Integration — Connection Issue [US]

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!