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 100 (0%) |
Incidents, newest first
Minor February 23, 2026 Delay in risk score calculation and visibility of violations in the graph. 3d 21h US Environment, API (US Environment), Application/UI (US Environment)
Started Feb 23, 2026, 02:47 PM UTC· resolved Feb 27, 2026, 12:00 PM UTC
- 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.
Minor February 16, 2026 Legacy Token authentication failure after system authentication update 11h 38m EU Environment, API (EU Environment), Application/UI (EU Environment), US Environment and 2 more
Started Feb 16, 2026, 09:42 PM UTC· resolved Feb 17, 2026, 09:20 AM UTC
- 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.