Catalyst Cloud status history
Current state: operational — “All Systems Operational” per https://status.catalystcloud.nz (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Catalyst Cloud incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-19 02:37 UTC | OpenStack APIs not accessible from some domains | resolved | none | 7 min |
| 2026-08-17 03:16 UTC | Network interface issue with GPU hypervisor | resolved | minor | 3 h 08 min |
| 2026-08-12 19:53 UTC | Block storage performance degradation in nz-hlz-1 | resolved | minor | 30 min |
| 2026-07-30 00:21 UTC | C3-GPU networking issues | resolved | major | 19 h 54 min |
| 2026-07-27 21:57 UTC | Degraded networking performance in nz-por-1 | resolved | minor | 7 h 21 min |
| 2026-06-23 00:02 UTC | Object storage API outage | resolved | major | 21 min |
| 2026-06-03 05:01 UTC | Emergency network maintenance | resolved | major | 40 min |
| 2026-05-08 18:05 UTC | Porirua region outage | resolved | major | 15 h 15 min |
| 2026-05-07 04:03 UTC | Compute issue | resolved | minor | 53 min |
| 2026-04-15 04:12 UTC | Intermittent API failures in nz-por-1 | resolved | major | 1 h 12 min |
| 2026-03-13 04:40 UTC | Degraded compute and network api performance nz-por-1 | resolved | none | 5 h 10 min |
| 2026-03-04 08:00 UTC | API issues in nz-por-1 | resolved | none | 2 h 30 min |
| 2026-02-25 22:00 UTC | Storage latency issues for some instances in nz-hlz-1 | resolved | none | 0 min |
| 2026-02-20 19:59 UTC | Network transit issues in nz-hlz-1 | resolved | major | 50 min |
| 2026-02-20 19:50 UTC | Unable to create new database instances in nz-hlz-1 | resolved | minor | 56 min |
| 2026-02-05 02:00 UTC | Network issues in porirua | resolved | minor | 3 h 04 min |
| 2026-02-03 16:26 UTC | Block storage degraded in Hamilton | resolved | none | 41 min |
| 2026-01-29 01:06 UTC | CCKS cluster creation not completing | resolved | minor | 3 d 23 h |
| 2026-01-27 20:32 UTC | Block storage porirua api issues | resolved | none | 16 min |
| 2025-11-17 05:18 UTC | Unplanned maintenance of the Block storage service | resolved | maintenance | 2 h 10 min |
| 2025-09-16 21:52 UTC | Volume API errors in nz-por-1 | resolved | major | 29 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
}