Vendor Status Watch

← all vendors

Cycode status history

Current state: operational — “All Systems Operational” per https://status.cycode.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

9incidents, last 30 days
28incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do Cycode incidents last?

100 minmedian incident duration27 measured
7.6 h90th percentile1 in 10 ran longer
median, major/critical onlynone posted

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)

StartedIncidentStatusImpactDuration
2026-09-13 10:36 UTCGitHub incident can affect Cycoderesolvedminor8 h 16 min
2026-09-08 16:53 UTCApplication and scanning degraded performanceresolvedminor32 min
2026-09-08 09:53 UTCApplication and scanning degraded performanceresolvedminor58 min
2026-09-01 15:10 UTCGitHub incident can affect Cycoderesolvedminor54 min
2026-08-26 23:04 UTCGitHub incident can affect Cycoderesolvedminor1 h 25 min
2026-08-20 14:52 UTCScan Performance Degredationresolvedminor1 h 44 min
2026-08-19 13:18 UTCPlatform and PR scans slownessresolvedminor4 h 47 min
2026-08-18 14:34 UTC Delayed GitHub PR status checksresolvedminor
2026-08-17 13:44 UTCGitHub incident can affect Cycoderesolvedminor7 h 37 min
2026-08-14 13:41 UTCDegraded performance in Secrets Pull Request scanningresolvedminor2 h 32 min
2026-08-13 14:53 UTCGitHub incident can affect Cycoderesolvedminor45 min
2026-08-12 16:25 UTCGitHub incident can affect Cycoderesolvedminor16 min
2026-08-11 14:55 UTCGitHub incident can affect Cycoderesolvedminor5 h 14 min
2026-08-10 14:06 UTCWe have noticed degraded performance in scanningresolvedminor1 h 39 min
2026-08-02 14:08 UTCWe’re investigating an issue causing older events to be reprocessedresolvedminor39 h 59 min
2026-07-27 10:31 UTCDegraded performance in scansresolvedminor1 h 26 min
2026-07-27 03:56 UTCGitHub incident can affect Cycoderesolvedminor15 min
2026-07-24 19:40 UTCGitHub incident can affect Cycoderesolvedminor45 min
2026-07-24 17:45 UTCDegraded performance in IaC Pull Request scansresolvedminor4 h 13 min
2026-07-24 16:21 UTCGitHub incident can affect Cycoderesolvedminor1 h 19 min
2026-07-23 07:58 UTCGitHub incident can affect Cycoderesolvedminor1 h 40 min
2026-07-16 18:56 UTCPlatform Slownessresolvedminor1 h 08 min
2026-07-15 17:22 UTCCycode CLI 3.17.1/2 Secrets scans failuresresolvedminor1 h 45 min
2026-07-14 16:12 UTCDelays in violations status updates in EUresolvedminor5 h 10 min
2026-07-13 08:47 UTCDegraded performanceresolvedminor3 h 48 min
2026-07-09 10:54 UTCInaccurate violation counts in some dashboards and panels.resolvedminor8 d 6 h
2026-07-09 09:07 UTCMaestro AI service disruptionresolvedminor1 h 32 min
2026-07-06 12:52 UTCInfrastructure Provisioning Delaysresolvedminor2 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
}