Vendor Status Watch

← all vendors

Catalyst Cloud status history

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

1incidents, last 30 days
6incidents, last 90 days
21incidents on record
Incidents per week, last 12 weeks:

How long do Catalyst Cloud incidents last?

54 minmedian incident duration20 measured
15.2 h90th percentile1 in 10 ran longer
50 minmedian, major/critical only7 incidents

From 20 incidents with a vendor-posted start and resolve time. Longest on record: CCKS cluster creation not completing — 4.0 days (2026-01-29 01:06 UTC). Excluded, never estimated: 1 scheduled maintenance. 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 (21)

StartedIncidentStatusImpactDuration
2026-08-19 02:37 UTCOpenStack APIs not accessible from some domainsresolvednone7 min
2026-08-17 03:16 UTCNetwork interface issue with GPU hypervisorresolvedminor3 h 08 min
2026-08-12 19:53 UTCBlock storage performance degradation in nz-hlz-1resolvedminor30 min
2026-07-30 00:21 UTCC3-GPU networking issuesresolvedmajor19 h 54 min
2026-07-27 21:57 UTCDegraded networking performance in nz-por-1resolvedminor7 h 21 min
2026-06-23 00:02 UTCObject storage API outageresolvedmajor21 min
2026-06-03 05:01 UTCEmergency network maintenanceresolvedmajor40 min
2026-05-08 18:05 UTCPorirua region outageresolvedmajor15 h 15 min
2026-05-07 04:03 UTCCompute issueresolvedminor53 min
2026-04-15 04:12 UTCIntermittent API failures in nz-por-1resolvedmajor1 h 12 min
2026-03-13 04:40 UTCDegraded compute and network api performance nz-por-1resolvednone5 h 10 min
2026-03-04 08:00 UTCAPI issues in nz-por-1resolvednone2 h 30 min
2026-02-25 22:00 UTCStorage latency issues for some instances in nz-hlz-1resolvednone0 min
2026-02-20 19:59 UTCNetwork transit issues in nz-hlz-1resolvedmajor50 min
2026-02-20 19:50 UTCUnable to create new database instances in nz-hlz-1resolvedminor56 min
2026-02-05 02:00 UTCNetwork issues in poriruaresolvedminor3 h 04 min
2026-02-03 16:26 UTCBlock storage degraded in Hamiltonresolvednone41 min
2026-01-29 01:06 UTCCCKS cluster creation not completingresolvedminor3 d 23 h
2026-01-27 20:32 UTCBlock storage porirua api issuesresolvednone16 min
2025-11-17 05:18 UTCUnplanned maintenance of the Block storage serviceresolvedmaintenance2 h 10 min
2025-09-16 21:52 UTCVolume API errors in nz-por-1resolvedmajor29 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 Catalyst Cloud with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "catalyst-cloud"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}