Cycode status history
Current state: operational — “All Systems Operational” per https://status.cycode.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Cycode incidents last?
From 27 incidents with a vendor-posted start and resolve time. Longest on record: Inaccurate violation counts in some dashboards and panels. — 8.3 days (2026-07-09 10:54 UTC). Excluded, never estimated: 1 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (28)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-13 10:36 UTC | GitHub incident can affect Cycode | resolved | minor | 8 h 16 min |
| 2026-09-08 16:53 UTC | Application and scanning degraded performance | resolved | minor | 32 min |
| 2026-09-08 09:53 UTC | Application and scanning degraded performance | resolved | minor | 58 min |
| 2026-09-01 15:10 UTC | GitHub incident can affect Cycode | resolved | minor | 54 min |
| 2026-08-26 23:04 UTC | GitHub incident can affect Cycode | resolved | minor | 1 h 25 min |
| 2026-08-20 14:52 UTC | Scan Performance Degredation | resolved | minor | 1 h 44 min |
| 2026-08-19 13:18 UTC | Platform and PR scans slowness | resolved | minor | 4 h 47 min |
| 2026-08-18 14:34 UTC | Delayed GitHub PR status checks | resolved | minor | — |
| 2026-08-17 13:44 UTC | GitHub incident can affect Cycode | resolved | minor | 7 h 37 min |
| 2026-08-14 13:41 UTC | Degraded performance in Secrets Pull Request scanning | resolved | minor | 2 h 32 min |
| 2026-08-13 14:53 UTC | GitHub incident can affect Cycode | resolved | minor | 45 min |
| 2026-08-12 16:25 UTC | GitHub incident can affect Cycode | resolved | minor | 16 min |
| 2026-08-11 14:55 UTC | GitHub incident can affect Cycode | resolved | minor | 5 h 14 min |
| 2026-08-10 14:06 UTC | We have noticed degraded performance in scanning | resolved | minor | 1 h 39 min |
| 2026-08-02 14:08 UTC | We’re investigating an issue causing older events to be reprocessed | resolved | minor | 39 h 59 min |
| 2026-07-27 10:31 UTC | Degraded performance in scans | resolved | minor | 1 h 26 min |
| 2026-07-27 03:56 UTC | GitHub incident can affect Cycode | resolved | minor | 15 min |
| 2026-07-24 19:40 UTC | GitHub incident can affect Cycode | resolved | minor | 45 min |
| 2026-07-24 17:45 UTC | Degraded performance in IaC Pull Request scans | resolved | minor | 4 h 13 min |
| 2026-07-24 16:21 UTC | GitHub incident can affect Cycode | resolved | minor | 1 h 19 min |
| 2026-07-23 07:58 UTC | GitHub incident can affect Cycode | resolved | minor | 1 h 40 min |
| 2026-07-16 18:56 UTC | Platform Slowness | resolved | minor | 1 h 08 min |
| 2026-07-15 17:22 UTC | Cycode CLI 3.17.1/2 Secrets scans failures | resolved | minor | 1 h 45 min |
| 2026-07-14 16:12 UTC | Delays in violations status updates in EU | resolved | minor | 5 h 10 min |
| 2026-07-13 08:47 UTC | Degraded performance | resolved | minor | 3 h 48 min |
| 2026-07-09 10:54 UTC | Inaccurate violation counts in some dashboards and panels. | resolved | minor | 8 d 6 h |
| 2026-07-09 09:07 UTC | Maestro AI service disruption | resolved | minor | 1 h 32 min |
| 2026-07-06 12:52 UTC | Infrastructure Provisioning Delays | resolved | minor | 2 h 16 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Cycode with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"cycode"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}