Wasabi status history
Current state: operational — “All Systems Operational” per https://status.wasabi.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Wasabi incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-14 00:00 UTC | Maintenance Activity Advisory for EU-WEST-1 | maintenance | maintenance | 2 d 12 h (approx.) |
| 2026-09-01 08:31 UTC | WACM reporting 0% storage utilization for subaccounts | resolved | minor | 2 h 05 min |
| 2026-08-31 00:00 UTC | Maintenance Activity Advisory for US-EAST-1 | maintenance | maintenance | 11 d 12 h (approx.) |
| 2026-08-25 23:46 UTC | System Errors in US-EAST-1 | resolved | minor | 2 h 51 min |
| 2026-08-04 07:30 UTC | System Errors in EU-CENTRAL-2 | resolved | major | 0 min |
| 2026-07-15 19:00 UTC | Intermittent Wasabi Console Access - Singapore (ap-southeast-1) | resolved | none | 0 min |
| 2026-07-04 17:45 UTC | Wasabi Management Console network errors | resolved | none | 0 min |
| 2026-06-28 14:00 UTC | System Errors in AP-NORTHEAST-2 | postmortem | minor | 10 h 15 min |
| 2026-06-24 15:00 UTC | System Errors in AP-NORTHEAST-1 | resolved | none | 10 h 15 min |
| 2026-05-27 06:39 UTC | Intermittent Network Error - Wasabi Console | postmortem | minor | 6 h 59 min |
| 2026-05-21 01:37 UTC | System Errors in AP-NORTHEAST-1 | postmortem | minor | 1 h 46 min |
| 2026-05-08 10:00 UTC | StorageQuotaExceeded error sent incorrectly on some accounts | resolved | none | 0 min |
| 2026-04-25 07:30 UTC | Wasabi Management Console timeout and network errors in us-east-1 | resolved | none | 0 min |
| 2026-03-24 19:30 UTC | System Errors in AP-NORTHEAST-1 | postmortem | none | 0 min |
| 2026-02-06 08:45 UTC | System Errors in US-WEST-1 Region | postmortem | major | 3 h 42 min |
| 2025-11-20 02:35 UTC | Wasabi Management Console errors | resolved | minor | 1 h 30 min |
| 2025-10-23 14:13 UTC | Login errors seen with Custom Cloud Console | resolved | minor | 46 min |
| 2025-09-19 11:00 UTC | System Errors in US-WEST-1 | resolved | none | 0 min |
| 2025-08-18 16:12 UTC | WACM Utilization Data updates may be delayed | resolved | minor | 47 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
}