Vendor Status Watch

← all vendors

Cloudsigma status history

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

10incidents, last 30 days
16incidents, last 90 days
58incidents on record
Incidents per week, last 12 weeks:

How long do Cloudsigma incidents last?

2.3 hmedian incident duration53 measured
11.9 h90th percentile1 in 10 ran longer
87 minmedian, major/critical only15 incidents

From 53 incidents with a vendor-posted start and resolve time. Longest on record: [MNL2] Payment Issues — 43.1 days (2025-09-16 07:08 UTC). Excluded, never estimated: 4 scheduled maintenance, 1 resolution inferred by us. 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 (58)

StartedIncidentStatusImpactDuration
2026-09-15 11:00 UTC[TYO] Emergency API Server Maintenancemaintenancemaintenance25 h 28 min (approx.)
2026-09-15 07:00 UTC[PER] Storage Cluster Maintenance - Stage 2maintenancemaintenance29 h 28 min (approx.)
2026-09-14 12:00 UTC[PER] Storage Cluster Maintenance - Stage 1maintenancemaintenance24 h 28 min (approx.)
2026-09-11 13:50 UTC[ZRH] Degraded API Performanceresolvedminor1 h 33 min
2026-09-08 12:00 UTC[MNL2] Hardware Maintenancemaintenancemaintenance24 h 30 min (approx.)
2026-09-08 06:45 UTC[ZRH][GVA] Network Issueresolvedminor8 h 54 min
2026-09-07 14:11 UTC[ZRH][GVA] Network outageresolvedmajor1 h 27 min
2026-09-04 04:39 UTC[GVA] Inaccessible PaaS Panelinvestigatingminor3 h 34 min (approx.)
2026-09-03 09:12 UTC[MNL2][CRK] Connectivity Issuesresolvedminor26 h 56 min
2026-08-31 12:38 UTC[CRK] Inaccessible PaaS Panelresolvedminor2 h 30 min
2026-08-06 19:48 UTC[CAI] Unavailable WebAppresolvedmajor2 h 56 min
2026-07-30 20:12 UTC[MNL] Network Issueresolvedminor33 min
2026-07-30 20:12 UTC[MNL] Network Issueresolvedminor33 min
2026-07-21 02:28 UTC[CAI] Unavailable WebAppresolvedmajor41 min
2026-07-18 18:14 UTC[DUB] Unavailable hostsresolvedminor6 h 13 min
2026-07-09 19:56 UTC[MNL2] Degraded Network Performanceresolvedminor1 h 19 min
2026-06-14 12:41 UTC[MNL] Web VNC unavailableresolvedminor30 h 25 min
2026-06-05 00:25 UTC[MTY] Unavailable hostsresolvedminor2 h 00 min
2026-06-02 20:46 UTC[FRA] API Degraded Performanceresolvedminor2 h 20 min
2026-05-27 16:28 UTC[FRA] Inaccessible PaaS Panelsresolvedminor15 min
2026-05-24 12:44 UTC[RUH] Degraded Network Performanceresolvedminor4 h 34 min
2026-05-24 09:57 UTC[RUH] Network Issuesresolvedmajor52 min
2026-05-17 17:28 UTC[MTY] Unavailable hostsresolvedminor3 h 32 min
2026-04-29 06:14 UTC[RUH] WebApp Issueresolvedminor5 h 56 min
2026-04-28 05:27 UTC[RUH] Degraded API Performanceresolvedminor10 h 26 min
2026-04-27 09:35 UTC[RUH] Degraded API Performanceresolvedminor2 h 19 min
2026-04-27 09:27 UTC[ZRH] Degraded API Performanceresolvedminor24 min
2026-04-15 06:28 UTC[GVA][ZRH] Degraded API Performanceresolvedminor7 h 28 min
2026-04-13 16:04 UTC[MNL] Network Issueresolvedmajor3 h 09 min
2026-04-09 23:32 UTC[CAI] Unavailable WebAppresolvedmajor2 min
2026-04-09 23:32 UTC[CAI] Unavailable WebAppresolvedmajor1 h 25 min
2026-04-01 23:27 UTC[CAI] Unavailable WebAppresolvedmajor59 min
2026-04-01 17:17 UTC[CAI] Unavailable WebAppresolvedmajor3 h 59 min
2026-03-20 13:02 UTC[RUH] Degraded API Performanceresolvedminor4 h 47 min
2026-03-16 23:34 UTC[MTY] Network Issuesresolvedminor11 h 52 min
2026-03-16 11:51 UTC[MTY] Inaccessible PaaS Panelsresolvedminor4 h 26 min
2026-03-07 12:41 UTC[MNL] API Degraded Performanceresolvedminor6 d 8 h
2026-02-19 16:45 UTC[HNL] Inaccessible WebApp Interfaceresolvedminor22 min
2026-02-17 09:28 UTC[ZRH] API Degraded Performanceresolvedminor6 d 12 h
2026-02-17 00:28 UTC[ZRH] Unavailable hostsresolvedminor6 h 11 min
2026-01-30 15:17 UTC[ADB] Network Issuesresolvedcritical1 h 54 min
2026-01-30 09:37 UTC[ADB] Network Issuesresolvedcritical3 h 27 min
2026-01-27 20:08 UTC[ADB] Network Issuesresolvedmajor48 min
2026-01-04 10:28 UTC[HNL] Inaccessible WebApp Interfaceresolvedminor16 min
2025-12-08 11:09 UTC[HNL] Inaccessible WebApp Interfaceresolvednone14 min
2025-11-26 00:08 UTC[MTY] Degraded Network Performanceresolvedminor4 h 15 min
2025-11-20 17:46 UTC[HNL] Inaccessible WebApp Interfaceresolvedminor26 min
2025-11-18 12:06 UTC[ALL] Cloudflare Global Network issuesresolvedmajor6 h 05 min
2025-10-31 06:31 UTC[WDC] Degraded Network Performanceresolvedminor47 min
2025-10-27 09:24 UTC[MNL] Degraded Network Performanceresolvedminor1 h 37 min
2025-10-19 11:59 UTC[CAI] Unavailable WebAppresolvedminor1 h 23 min
2025-10-16 00:11 UTC[MTY] Unavailable WebAppresolvedminor2 h 30 min
2025-10-06 01:53 UTC[ADB] Unavailable WebAppresolvedmajor1 h 07 min
2025-09-30 00:46 UTC[FRA] Unavailable WebAppresolvedminor55 min
2025-09-17 20:09 UTC[RUH] Unavailable Drivesresolvedminor1 h 07 min
2025-09-16 07:08 UTC[MNL2] Payment Issuesresolvedminor43 d 3 h
2025-09-13 05:22 UTC[MNL2] Inaccessible WebApp Interfaceresolvedmajor1 h 28 min
2025-09-12 09:57 UTC[ZRH] [GVA] Unavailable Drivesresolvedminor3 h 03 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 Cloudsigma with the template

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

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