Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)April 1, 2026 · 01:54 IDT Resolved
Resolved
<hr>March 31, 2026 · 22:23 IDT Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/ml7wplmxbt5l">https://www.githubstatus.com/incidents/ml7wplmxbt5l</a>

Github's incident can affect Cycode PR scanning

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 24, 2026 · 23:00 IST Resolved
Resolved
<hr>March 24, 2026 · 22:41 IST Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/kp06czybl7dw">https://www.githubstatus.com/incidents/kp06czybl7dw</a>

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.

Infrastructure Upgrades

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 17, 2026 · 11:03 IST Resolved
Resolved
<hr>March 16, 2026 · 17:14 IST Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/2lh36qcrd7l6">https://www.githubstatus.com/incidents/2lh36qcrd7l6</a>

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 - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 9, 2026 · 22:41 IST Resolved
The GitHub incident was resolved.
<hr>March 9, 2026 · 17:57 IST Issue
<a target="_blank" href="https://www.githubstatus.com/incidents/7k92rcz4f1zq">https://www.githubstatus.com/incidents/7k92rcz4f1zq</a>

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)March 6, 2026 · 13:51 IST Resolved
The GitHub incident was resolved. 
<hr>March 5, 2026 · 18:57 IST Issue
GitHub is currently experiencing an incident that may affect pull request operations. We are monitoring the situation. 
<a target="_blank" href="https://www.githubstatus.com/incidents/g5gnt5l5hf56">https://www.githubstatus.com/incidents/g5gnt5l5hf56</a>

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.

GitHub Pull Request Service Incident

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.

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

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)February 17, 2026 · 16:25 IST Issue
Summary 
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. Tokens issued after the update were not affected. The issue was caused by the removal of a process that allowed continued use of these older tokens. The problem was identified overnight and resolved the following morning.

Key Timeline (IDT) 
February 16, 2026, 23:42 IDT: First reports of authentication failures with legacy tokens. 
February 17, 2026, 11:20 IDT: Corrective update deployed to restore access for affected customers.

Root Cause 
A process that enabled older tokens to work with the updated authentication system was mistakenly removed during a recent update. This led to authentication failures for customers still using these legacy tokens.

Actions Taken 
Restored the process that allows older tokens to be used for authentication.Deployed a corrective update to resolve the issue.

Action Items 
Add tests to ensure all authentication scenarios are covered.Implement integration tests to verify continued support for older tokens.Improve validation procedures to detect similar issues before deployment.

Legacy Token authentication failure after system authentication update

Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)February 11, 2026 · 17:00 IST Scheduled
We are upgrading our infrastructure to improve performance and stability. Intermittent disruptions may occur during the maintenance window.

Infrastructure Upgrade

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment)January 29, 2026 · 17:34 IST Post-mortem
Summary 
Between January 14 and January 25, 2026, customers experienced significant delays and failures in Software Composition Analysis (SCA) scans, particularly those involving dependency restoration. The issue resulted in SCA scans being blocked or taking much longer than usual to complete, while other scan types were largely unaffected. The root cause was traced to a process that repeatedly retried failed dependency restoration requests, leading to a backlog of messages and duplicate processing. This created a bottleneck, causing new SCA scan requests to be delayed or time out. The issue was resolved by updating the processing logic, increasing processing capacity, and clearing the backlog. SCA scan performance has since returned to normal.

Key Timeline (IDT)

January 14, 2026, 19:00 IDT: First alerts received about failing SCA scans and timeouts. 
January 15, 2026, 10:00 IDT: Significant increase in failed lock creation requests observed. 
January 16–21, 2026: Investigation revealed repeated retries and message duplication causing a backlog. 
January 22, 2026, 18:00 IDT: Updates deployed to improve processing and prevent duplicate retries. 
January 23, 2026, 09:00 IDT: Backlog began to clear; SCA scan performance improved. 
January 25, 2026, 09:00 IDT: Incident closed after confirming normal scan processing and backlog resolution.

Root Cause 
The incident was triggered by a process responsible for handling dependency restoration in SCA scans. When a restoration request failed or timed out, the process retried the request multiple times, resulting in a large volume of duplicate messages. This overwhelmed the processing system, causing a backlog and delays for new SCA scan requests. The issue was exacerbated by multiple processing units running the same retry logic in parallel, further increasing message duplication.

Actions Taken
<ol>
 <li>
Increased processing capacity to handle the backlog of requests. </li>
 <li>
Updated the retry logic to prevent duplicate processing of failed requests. </li>
 <li>
Cleared the backlog of duplicate messages. </li>
 <li>
Monitored system performance to ensure normal operation resumed. </li>
</ol>

Action Items
<ol>
 <li>
Refactor the restoration retry process to ensure only a single instance handles retries. </li>
 <li>
Add safeguards to prevent duplicate message processing. </li>
 <li>
Improve monitoring and alerting for abnormal retry or backlog patterns. </li>
 <li>
Review and optimize dependency restoration workflows to prevent similar issues in the future </li>
</ol>
<hr>January 25, 2026 · 08:56 IST Resolved
Resolved: The issue impacting SCA scan result ingestion has been fully mitigated and service performance has returned to normal. Backlogged events have been processed, and SCA scan results are now being ingested and reflected in the system as expected.
<hr>January 22, 2026 · 17:56 IST Update
Mitigations have been applied to reduce the impact and restore performance, and the system is now recovering. However, there is still a backlog of queued events to process, which may continue to delay ingestion and availability of SCA scan results until processing catches up.
<hr>January 22, 2026 · 11:43 IST Issue
We are experiencing degraded performance in the SCA scanning pipeline, which may cause delays in scan result ingestion and availability for some repositories.

Degraded Performance in SCA Scans

Scheduled maintenance - EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment, API (US Environment), Application/UI (US Environment)January 18, 2026 · 10:48 IST Scheduled
Some temporary impact to custom dashboards may occur during the maintenance window.

Metabase Updates

Minor incident - EU Environment, API (EU Environment), Application/UI (EU Environment)January 13, 2026 · 12:27 IST Post-mortem
Summary 
Between January 8 and January 9, 2026, customers in the EU region experienced delays in SAST (Static Application Security Testing) pull request scans and pre-receive hook scans. 
 These delays resulted in slower feedback for developers and, in some cases, led customers to temporarily disable automated scans. 
The issue was caused by a significant increase in container scanning activity, which introduced processing slowdowns in the shared scanning workflow. 
 On January 8, the underlying infrastructure was strengthened to align with the US environment; however, this change alone was insufficient to handle the increased load. 
 On January 9, the issue was fully resolved by increasing the number of processing replicas, alongside improved monitoring and scaling adjustments. Service levels have since returned to normal, and ongoing monitoring confirms continued stability.

Key Timeline (IDT) 
January 8, 2026, 10:00 IDT: Initial reports of slow SAST scan processing in the EU region 
January 8, 2026, 11:00–14:00 IDT: Increased delays observed in pull request and pre-receive hook scans 
January 8, 2026: Infrastructure resources strengthened to align with the US environment; improvement observed but insufficient under continued load 
January 9, 2026, 10:00–13:00 IDT: Recurrence of scan delays; some customers temporarily disabled automated scans 
January 9, 2026, 14:30 IDT: Additional processing replicas added; monitoring and scaling enhanced 
January 9, 2026, 15:30 IDT: Scan processing times returned to normal 
January 10, 2026, 11:00 IDT: Continued monitoring confirmed system stability

Root Cause 
A sudden and significant increase in container scanning activity, primarily driven by new customer integrations, exceeded existing processing capacity. 
 Although infrastructure resources were increased on January 8, the approach focused on strengthening individual nodes and did not sufficiently address the concurrency requirements. 
 The shared processing path across multiple scan types caused the elevated load to impact SAST pull request and pre-receive hook scans.

Actions Taken
<ol>
 <li>
Strengthened processing infrastructure on January 8 to align with the US environment </li>
 <li>
Increased the number of processing replicas on January 9 to better handle concurrent scan volumes </li>
 <li>
Improved monitoring and alerting to better detect scan latency issues </li>
 <li>
Adjusted scaling strategies to respond more effectively to traffic spikes </li>
 <li>
Continued close monitoring to ensure service stability </li>
</ol>

Action Items
<ol>
 <li>
Improve separation between scan processing paths to prevent one scan type from impacting others </li>
 <li>
Enhance monitoring and alerting for early detection of scan delays </li>
 <li>
Review and optimize scaling strategies, with clearer guidelines on when to scale vertically versus horizontally </li>
</ol>
<hr>January 13, 2026 · 12:21 IST Issue
Delays in SAST pull request and pre-receive hook scans in the EU region due to insufficient processing capacity under increased scan load.

Is Cycode down?

Cycode status is UP

Lastest published events

Github's incident can affect Cycode PR scanning

Github's incident can affect Cycode PR scanning

Platform Slowness

Cycode Services, Components and Regions

Recent Cycode events

Github's incident can affect Cycode PR scanning

Github's incident can affect Cycode PR scanning

Platform Slowness

Infrastructure Upgrades

Github's incident can affect Cycode PR scanning

Infrastructure Upgrades

Get your FREE account now,
5 monitors included!

Is Cycode down?

Cycode status is UP

Lastest published events

Github's incident can affect Cycode PR scanning

Github's incident can affect Cycode PR scanning

Platform Slowness

Cycode Services, Components and Regions

Recent Cycode events

Github's incident can affect Cycode PR scanning

Github's incident can affect Cycode PR scanning

Platform Slowness

Infrastructure Upgrades

Github's incident can affect Cycode PR scanning

Infrastructure Upgrades

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!