Cycode Outage History
Cycode is up right nowPingoru has recorded 52 incidents for Cycode: 52 in the last 12 months and 22 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 114 of 720 (16%) |
| May 2026 | 3 | 16 of 744 (2%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 9 | 398 of 744 (54%) |
| August 2026 | 11 | 182 of 744 (25%) |
| September 2026 | 5 | 12 of 720 (2%) |
| October 2026 | 6 | 15 of 744 (2%) |
| November 2026 | 1 | 0 of 99 (0%) |
Incidents, newest first
Minor July 24, 2026 GitHub incident can affect Cycode 45m
Started Jul 24, 2026, 07:40 PM UTC· resolved Jul 24, 2026, 08:26 PM UTC
- investigating Jul 24, 2026, 07:40 PM UTC
GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj
- investigating Jul 24, 2026, 07:47 PM UTC
GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj
- investigating Jul 24, 2026, 07:49 PM UTC
GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj
- monitoring Jul 24, 2026, 08:06 PM UTC
GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj
- resolved Jul 24, 2026, 08:26 PM UTC
GitHub component: Pull Requests Original GitHub incident: https://stspg.io/sm1tp7kfm4vj
Minor July 24, 2026 Degraded performance in IaC Pull Request scans 4h 13m
Started Jul 24, 2026, 05:45 PM UTC· resolved Jul 24, 2026, 09:58 PM UTC
- investigating Jul 24, 2026, 05:45 PM UTC
We have noticed degraded performance in IaC Pull Request scans. We are troubleshooting the issue.
- identified Jul 24, 2026, 06:54 PM UTC
We have identified the root cause of the slownesses and are putting countermeasures in place.
- monitoring Jul 24, 2026, 08:35 PM UTC
The lag that led to slownesses is almost over. We are monitoring the situation.
- resolved Jul 24, 2026, 09:58 PM UTC
The issue has been resolved, and we are continuing to monitor the situation.
Minor July 24, 2026 GitHub incident can affect Cycode 1h 19m
Started Jul 24, 2026, 04:21 PM UTC· resolved Jul 24, 2026, 05:40 PM UTC
- investigating Jul 24, 2026, 04:21 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:23 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:25 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:26 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:31 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:33 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:43 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:46 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 04:49 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 05:20 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- investigating Jul 24, 2026, 05:35 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
- resolved Jul 24, 2026, 05:40 PM UTC
GitHub component: API Requests, Pull Requests Original GitHub incident: https://stspg.io/j5c80shxqm53
Minor July 23, 2026 GitHub incident can affect Cycode 1h 40m
Started Jul 23, 2026, 07:58 AM UTC· resolved Jul 23, 2026, 09:39 AM UTC
- investigating Jul 23, 2026, 07:58 AM UTC
GitHub component: Webhooks Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 08:29 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 08:37 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 09:22 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 09:26 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 09:27 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- investigating Jul 23, 2026, 09:32 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
- resolved Jul 23, 2026, 09:39 AM UTC
GitHub component: Webhooks, Pull Requests Original GitHub incident: https://stspg.io/syhr80rth84z
Minor July 16, 2026 Platform Slowness 1h 8m
Started Jul 16, 2026, 06:56 PM UTC· resolved Jul 16, 2026, 08:05 PM UTC
- monitoring Jul 16, 2026, 06:56 PM UTC
At 1:41 PM EDT, we identified an issue causing elevated error rates during request processing in the Platform UI. The issue was mitigated promptly, and the platform is currently operating normally. Our team continues to actively monitor the platform to ensure service stability.
- resolved Jul 16, 2026, 08:05 PM UTC
The incident has been resolved, and the platform is operating normally.
Minor July 9, 2026 Inaccurate violation counts in some dashboards and panels. 8d 6h
Started Jul 09, 2026, 10:54 AM UTC· resolved Jul 17, 2026, 04:58 PM UTC
- monitoring Jul 09, 2026, 10:54 AM UTC
We’ve identified an issue that may cause inaccurate violation counts in some product dashboards and custom dashboard panels that rely on violation data (not all dashboards are affected). We’ve already begun corrective work, but it will take time to fully complete, and you may see counts change as data is corrected. We’ll share another update once the fix has finished running and data accuracy is fully restored.
- monitoring Jul 12, 2026, 03:09 PM UTC
We have made significant progress in correcting the inaccurate violation counts affecting some product and custom dashboards. • Current Status: The fix has successfully completed for the vast majority of accounts, and full data accuracy has been restored. • Next Steps: We are actively resolving the issue for the small number of remaining affected accounts.
- resolved Jul 17, 2026, 04:58 PM UTC
Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.
Minor July 5, 2026 Issues with Violations and Custom Dashboards (Prod-US) 12d 9h
Started Jul 05, 2026, 07:30 AM UTC· resolved Jul 17, 2026, 04:56 PM UTC
- investigating Jul 05, 2026, 07:30 AM UTC
Investigating - Issues with Violations and Custom Dashboards (Prod-US) We are currently investigating an issue in our Prod-US environment where violations are failing to load. As a result, custom dashboard panels that rely on violation data may also fail to render or display errors. Our engineering team is actively looking into the root cause, and we will provide updates here as we learn more. We apologize for the inconvenience.
- monitoring Jul 05, 2026, 08:13 AM UTC
A fix has been deployed for the issues affecting violations and custom dashboards in Prod-US. We are actively monitoring the environment to ensure services are fully restored.
- monitoring Jul 05, 2026, 09:42 AM UTC
The core issue has been resolved, and violations and custom dashboards should now be working as normal. Our team is actively monitoring the data sync to resolve any remaining discrepancies with newer violations. We will provide a final update once the sync is complete.
- monitoring Jul 05, 2026, 11:44 AM UTC
We are continuing to monitor the data synchronization process for new violations in the UI. While functionality has been restored, it may take up to 6 hours for all recent data to fully catch up and reflect accurately. We will provide a final update once the synchronization is complete.
- resolved Jul 05, 2026, 06:54 PM UTC
The data synchronization is complete, and all recent violations have successfully populated in the UI. Violations and custom dashboards are functioning normally, and the incident is fully resolved. We appreciate your patience as we worked to restore full service.
- resolved Jul 17, 2026, 04:56 PM UTC
Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.
Minor May 6, 2026 GitHub Pull Request Service Incident 19m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started May 06, 2026, 06:59 PM UTC· resolved May 06, 2026, 07:18 PM UTC
- investigating May 06, 2026, 06:59 PM UTC
https://www.githubstatus.com/incidents/f5pb5d5mr9yh
- resolved May 06, 2026, 07:18 PM UTC
Resolved
Minor May 5, 2026 Partial Service Disruption in EU Environment 2h 30m EU Environment, API (EU Environment), Application/UI (EU Environment)
Started May 05, 2026, 05:48 PM UTC· resolved May 05, 2026, 08:19 PM UTC
- investigating May 05, 2026, 05:48 PM UTC
We are currently experiencing a service disruption affecting our EU environment. What’s impacted: Custom Dashboards are temporarily unavailable Some filtering capabilities on the Violations page may be slower than usual 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.
- resolved May 05, 2026, 08:18 PM UTC
The issue has been resolved, and all services are now operating normally. A detailed RCA will be provided soon.
- investigating May 18, 2026, 07:30 AM UTC
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 Investigated alerts and isolated the problematic configuration change. Performed additional safeguards and validation steps prior to remediation. Validated recovery steps in a non-production environment before applying them in production. Restored service by safely reattaching existing storage and returning processing to normal operation. Confirmed service availability and verified that data remained intact. Action Items Add stronger pre-deployment validation to catch malformed configuration values before rollout. Improve monitoring and alerting to detect repeated update failures and destructive actions earlier. Implement safeguards to prevent automated update workflows from removing stateful resources for this analytics service during invalid update scenarios. Improve operational logging and visibility to speed up diagnosis during similar events. Expand and regularly validate backup/restore coverage for the affected analytics stateful components.
Minor May 4, 2026 GitLab Webhook Processing Failure Due to Time Format Change 13h EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started May 04, 2026, 09:00 PM UTC· resolved May 05, 2026, 10:00 AM UTC
- investigating May 05, 2026, 11:53 AM UTC
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.
Minor April 28, 2026 Short service interruption 52m EU Environment, API (EU Environment), Application/UI (EU Environment)
Started Apr 28, 2026, 12:38 PM UTC· resolved Apr 28, 2026, 01:30 PM UTC
- investigating Apr 28, 2026, 01:38 PM UTC
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.
Minor April 27, 2026 Unprocessed Push Events 12h EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Apr 27, 2026, 09:00 PM UTC· resolved Apr 28, 2026, 09:00 AM UTC
- investigating May 06, 2026, 11:10 AM UTC
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.
Minor April 20, 2026 Short service interruption 15m EU Environment, API (EU Environment), Application/UI (EU Environment)
Started Apr 20, 2026, 02:57 PM UTC· resolved Apr 20, 2026, 03:12 PM UTC
- investigating Apr 20, 2026, 03:57 PM UTC
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 April 14, 2026 Slow CLI scans 2h EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Apr 14, 2026, 09:30 AM UTC· resolved Apr 14, 2026, 11:30 AM UTC
- investigating Apr 14, 2026, 08:50 PM UTC
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.
Minor April 13, 2026 Slow Pull request and CLI scans 22h 10m US Environment, API (US Environment), Application/UI (US Environment)
Started Apr 13, 2026, 01:20 PM UTC· resolved Apr 14, 2026, 11:30 AM UTC
- investigating Apr 14, 2026, 01:46 PM UTC
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.
Minor April 10, 2026 Increase SAST violations 4d 4h EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Apr 10, 2026, 06:30 AM UTC· resolved Apr 14, 2026, 10:48 AM UTC
- investigating Apr 28, 2026, 02:18 PM UTC
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) April 10, 2026, 09:33 IDT — A production update introduced incorrect handling of branch-scanning configuration for some SAST events. April 14, 2026, 13:48 IDT — A subsequent update restored expected enforcement of configured branch-scanning rules. April 21, 2026, 19:00 IDT — Customer reports alerted us to unexpected SAST findings on non-configured branches. April 22, 2026, 13:52 IDT — Root cause identified; scope assessment initiated. April 23, 2026, 18:13 IDT — Impact analysis tooling executed to identify affected data and tenants. April 27, 2026, 14:30 IDT — Cleanup completed; unintended findings removed and incident fully remediated. 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 Restored correct enforcement of customers’ configured branch-scanning rules. Assessed the scope of the impact across affected environments. Removed unintended SAST findings created for non-configured branches. Confirmed expected behavior after cleanup. Action Items Improve validation and safeguards around branch-scanning configuration checks during updates. Enhance monitoring to detect unexpected increases in scan volume or findings. Strengthen release checks for feature-gated behavior to prevent similar regressions.
Minor March 24, 2026 Platform Slowness 3h 42m US Environment, API (US Environment), Application/UI (US Environment)
Started Mar 24, 2026, 03:47 PM UTC· resolved Mar 24, 2026, 07:29 PM UTC
- investigating Mar 24, 2026, 03:47 PM UTC
We are currently experiencing slowness in the Cycode Platform (US). Users may notice increased response times.
- monitoring Mar 24, 2026, 04:28 PM UTC
The system is operating normally, and we are continuing to monitor closely.
- resolved Mar 24, 2026, 07:29 PM UTC
The issue has been resolved. We will share the RCA document as soon as it is completed.
Minor March 16, 2026 Github's incident can affect Cycode PR scanning 17h 49m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Mar 16, 2026, 03:14 PM UTC· resolved Mar 17, 2026, 09:03 AM UTC
- investigating Mar 16, 2026, 03:14 PM UTC
https://www.githubstatus.com/incidents/2lh36qcrd7l6
- resolved Mar 17, 2026, 09:03 AM UTC
Resolved
Minor March 9, 2026 Github's incident can affect Cycode PR scanning 4h 44m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Mar 09, 2026, 03:57 PM UTC· resolved Mar 09, 2026, 08:41 PM UTC
- investigating Mar 09, 2026, 03:57 PM UTC
https://www.githubstatus.com/incidents/7k92rcz4f1zq
- resolved Mar 09, 2026, 08:41 PM UTC
The GitHub incident was resolved.
Minor March 5, 2026 Github's incident can affect Cycode PR scanning 18h 53m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Mar 05, 2026, 04:57 PM UTC· resolved Mar 06, 2026, 11:51 AM UTC
- investigating Mar 05, 2026, 04:57 PM UTC
GitHub is currently experiencing an incident that may affect pull request operations. We are monitoring the situation. https://www.githubstatus.com/incidents/g5gnt5l5hf56
- resolved Mar 06, 2026, 11:51 AM UTC
The GitHub incident was resolved.
Minor March 2, 2026 Slowness in CLI Secret Scans 48m US Environment, API (US Environment)
Started Mar 02, 2026, 08:49 PM UTC· resolved Mar 02, 2026, 09:37 PM UTC
- 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.
Minor March 2, 2026 Platform Slowness 1h 7m US Environment, API (US Environment), Application/UI (US Environment)
Started Mar 02, 2026, 08:19 PM UTC· resolved Mar 02, 2026, 09:26 PM UTC
- 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.
Minor March 2, 2026 GitHub Pull Request Service Incident 12h 12m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Mar 02, 2026, 08:15 PM UTC· resolved Mar 03, 2026, 08:27 AM UTC
- 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
Minor February 26, 2026 Delay in PR scans for Github Pull Requests 1h 17m US Environment, API (US Environment), Application/UI (US Environment)
Started Feb 26, 2026, 04:23 PM UTC· resolved Feb 26, 2026, 05:41 PM UTC
- 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.
Minor February 24, 2026 IaC PR Scanning Delays 6h 58m US Environment, API (US Environment), Application/UI (US Environment)
Started Feb 24, 2026, 11:39 AM UTC· resolved Feb 24, 2026, 06:37 PM UTC
- 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.