Vendor Status Watch

← all vendors

Wasabi status history

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

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

How long do Wasabi incidents last?

90 minmedian incident duration17 measured
10.2 h90th percentile1 in 10 ran longer
111 minmedian, major/critical only2 incidents

From 17 incidents with a vendor-posted start and resolve time. Longest on record: WACM Utilization Data updates may be delayed — 47.6 h (2025-08-18 16:12 UTC). Excluded, never estimated: 2 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 (19)

StartedIncidentStatusImpactDuration
2026-09-14 00:00 UTCMaintenance Activity Advisory for EU-WEST-1maintenancemaintenance2 d 12 h (approx.)
2026-09-01 08:31 UTCWACM reporting 0% storage utilization for subaccountsresolvedminor2 h 05 min
2026-08-31 00:00 UTCMaintenance Activity Advisory for US-EAST-1maintenancemaintenance11 d 12 h (approx.)
2026-08-25 23:46 UTCSystem Errors in US-EAST-1resolvedminor2 h 51 min
2026-08-04 07:30 UTCSystem Errors in EU-CENTRAL-2resolvedmajor0 min
2026-07-15 19:00 UTCIntermittent Wasabi Console Access - Singapore (ap-southeast-1)resolvednone0 min
2026-07-04 17:45 UTCWasabi Management Console network errorsresolvednone0 min
2026-06-28 14:00 UTCSystem Errors in AP-NORTHEAST-2postmortemminor10 h 15 min
2026-06-24 15:00 UTCSystem Errors in AP-NORTHEAST-1resolvednone10 h 15 min
2026-05-27 06:39 UTCIntermittent Network Error - Wasabi Consolepostmortemminor6 h 59 min
2026-05-21 01:37 UTCSystem Errors in AP-NORTHEAST-1postmortemminor1 h 46 min
2026-05-08 10:00 UTCStorageQuotaExceeded error sent incorrectly on some accountsresolvednone0 min
2026-04-25 07:30 UTCWasabi Management Console timeout and network errors in us-east-1resolvednone0 min
2026-03-24 19:30 UTCSystem Errors in AP-NORTHEAST-1postmortemnone0 min
2026-02-06 08:45 UTCSystem Errors in US-WEST-1 Regionpostmortemmajor3 h 42 min
2025-11-20 02:35 UTCWasabi Management Console errorsresolvedminor1 h 30 min
2025-10-23 14:13 UTCLogin errors seen with Custom Cloud Consoleresolvedminor46 min
2025-09-19 11:00 UTCSystem Errors in US-WEST-1resolvednone0 min
2025-08-18 16:12 UTCWACM Utilization Data updates may be delayedresolvedminor47 h 39 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 Wasabi with the template

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

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