Cycode Outage History
Cycode is up right nowThere were 9 Cycode outages since February 16, 2026 totaling 145h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
Github's incident can affect Cycode PR scanning
Timeline · 2 updates
- investigating Mar 16, 2026, 03:14 PM UTC
https://www.githubstatus.com/incidents/2lh36qcrd7l6
- resolved Mar 17, 2026, 09:03 AM UTC
Resolved
Slowness in CLI Secret Scans
Timeline · 3 updates
- investigating Mar 02, 2026, 08:49 PM UTC
We’re investigating reports of slowness in CLI Secret scans.
- monitoring Mar 02, 2026, 09:03 PM UTC
A fix has been applied to address the slowness in CLI Secret Scans. We are continuing to monitor the situation.
- resolved Mar 02, 2026, 09:37 PM UTC
The issue has been resolved. We will share the RCA document as soon as it is completed.
Platform Slowness
Timeline · 3 updates
- investigating Mar 02, 2026, 08:19 PM UTC
We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.
- investigating Mar 02, 2026, 08:39 PM UTC
We have increased the replicas of our UI component. We are still checking for the root cause.
- resolved Mar 02, 2026, 09:26 PM UTC
The issue has been resolved. We will share the RCA document as soon as it is completed.
GitHub Pull Request Service Incident
Timeline · 3 updates
- investigating Mar 02, 2026, 08:15 PM UTC
An ongoing GitHub incident may affect pull request operations. We are monitoring the situation.
- investigating Mar 02, 2026, 09:27 PM UTC
https://www.githubstatus.com/incidents/vhpmx9vc93m0 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
- resolved Mar 03, 2026, 08:27 AM UTC
This incident has been resolved
Delay in PR scans for Github Pull Requests
Timeline · 2 updates
- monitoring Feb 26, 2026, 04:23 PM UTC
We identified delays in scanning GitHub pull requests. Service has been restored and we are continuing to monitor to confirm stability.
- resolved Feb 26, 2026, 05:41 PM UTC
The issue has been resolved and scanning is operating normally. We will continue monitoring to ensure stability.
IaC PR Scanning Delays
Timeline · 3 updates
- investigating Feb 24, 2026, 11:39 AM UTC
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.
- monitoring Feb 24, 2026, 12:23 PM UTC
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.
- resolved Feb 24, 2026, 06:37 PM UTC
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.
Delay in risk score calculation and visibility of violations in the graph.
Timeline · 3 updates
- investigating Feb 23, 2026, 02:47 PM UTC
We are currently investigating the issue and will provide updates soon.
- monitoring Feb 25, 2026, 04:06 PM UTC
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
- resolved Feb 27, 2026, 12:00 PM UTC
The issue is fully resolved and all items have been processed. No further impact is expected.
Legacy Token authentication failure after system authentication update
Timeline · 1 update
- investigating Feb 17, 2026, 02:25 PM UTC
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.
Looking to track Cycode downtime and outages?
Pingoru polls Cycode's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Cycode reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Cycode alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required