Is Wasabi down right now?

No. As of 2026-10-10 07:19 UTC, Wasabi is up. This page reads the status again every 3 minutes.

Where does this status come from?

From Wasabi's own status page API at https://status.wasabi.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Wasabi's words.

Can I get an alert when Wasabi goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Wasabi reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/wasabi/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Wasabi status?

Fetch https://upbutler.com/status/wasabi/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"wasabi"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Wasabi's?

Add "wasabi" to the dependencies of your UpButler workspace. When one of your monitors fails while Wasabi has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Wasabi down?

Wasabi is up

Right now

No. No incidents reported.

Last checked 10 s ago (2026-10-10 07:19 UTC) from status.wasabi.com · every 180s

For agents

proceed

Proceed.

GET upbutler.com/status/wasabi/status.agent.json

MCP: upstream_status {"service":"wasabi"}

S3-compatible object storage per region.

What Wasabi says

Operational

Taken as is from Wasabi's own status page API. Incident titles and component names below are theirs.

Open status.wasabi.com

What UpButler measured

There is no keyless endpoint of Wasabi that says anything useful, so UpButler does not probe it. To check your own Wasabi account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Wasabi

Maintenance Activity Advisory for 15 October 2026 in EU-WEST-3 and EU-SOUTH-1scheduled maintenance
Starts 2026-10-15 11:00 UTC · EU-West-3 (London), EU-South-1 (Milan)
Wasabi Customers, We will be conducting essential system work in the EU-WEST-3 (London) and EU-SOUTH-1 (Milan) regions on Wednesday, October 15, 2026, at 11:00 AM UTC through Thursday, October 16, 2026, at 01:00 AM UTC (Wednesday, October 15, 2026, at 7:00 AM EDT through 9:00 PM EDT). During this activity, we expect that there will be no impact on service, but out of an abundance of caution we wanted to inform customers of this event. We understand the inconvenience this may cause and assure yo…
Maintenance Activity Advisory for 14 October 2026 in AP-NORTHEAST-1 and AP-NORTHEAST-2scheduled maintenance
Starts 2026-10-14 11:00 UTC · AP-Northeast-1 (Tokyo), AP-Northeast-2 (Osaka)
Wasabi Customers, We will be conducting essential system work in the AP-NORTHEAST-1 (Tokyo) and AP-NORTHEAST-2 (Osaka) regions on Wednesday, October 14, 2026, at 11:00 AM UTC through Thursday, October 15, 2026, at 01:00 AM UTC (Wednesday, October 14, 2026, at 7:00 AM EDT through 9:00 PM EDT). During this activity, we expect that there will be no impact on service, but out of an abundance of caution we wanted to inform customers of this event. We understand the inconvenience this may cause and a…
Maintenance Activity Advisory for EU-CENTRAL-2scheduled maintenance
Starts 2026-10-12 00:00 UTC · EU-Central-2 (Frankfurt)
Wasabi Customers, We will be conducting essential system work in the EU-CENTRAL-2 (Frankfurt) from Monday, October 12, 2026 through Friday, October 16, 2026. During this activity, we expect that there will be minimal impact on service. There is no action that you must take in preparation for this event. We recognize that this may impact your activity and wanted to make you aware of this upcoming event. To stay informed about the progress of this maintenance activity, please subscribe to status.…

Text written by Wasabi, shown unchanged.

Wasabi components

27 operational

US-Central-1 (Texas)Operational
US-East-1 (N. Virginia)Operational
US-East-1-Dell-OBS (N. Virginia)Operational
US-East-2 (N. Virginia)Operational
US-West-1 (Oregon)Operational
US-West-2 (San Jose)Operational
US-West-2-Dell-OBS (San Jose)Operational
CA-Central-1 (Toronto)Operational
EU-Central-1 (Amsterdam)Operational
EU-Central-2 (Frankfurt)Operational
EU-West-1 (London)Operational
EU-West-1-Dell-OBS (London)Operational
EU-West-2 (Paris)Operational
EU-West-3 (London)Operational
EU-South-1 (Milan)Operational
AP-Northeast-1 (Tokyo)Operational
AP-Northeast-2 (Osaka)Operational
AP-Southeast-1 (Singapore)Operational
AP-Southeast-2 (Sydney)Operational
Wasabi Account Control APIOperational
Wasabi Account Control Manager ConsoleOperational
Wasabi Custom Cloud ConsoleOperational
Wasabi Management ConsoleOperational
Wasabi.comOperational
Wasabi AiROperational
WACM Connect APIOperational
docs.wasabi.comOperational

Wasabi incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: no record
2026-09-28: no record
2026-09-29: no record
2026-09-30: no record
2026-10-01: no record
2026-10-02: no record
2026-10-03: no record
2026-10-04: no record
2026-10-05: no record
2026-10-06: minor incident
2026-10-07: no incident reported
2026-10-08: no incident reported
2026-10-09: no incident reported
2026-10-10: major incident

2026-07-132 of 5 days with an incidenttoday

Each bar is a day, coloured by the worst incident Wasabi reported. It is their incident record, not a measurement of uptime.

Incidents: 2; 1 major or critical
Typical time to resolve: —; median, needs 3 incidents
Nine in ten within: —; 90th percentile
Longest: 1 h 44 min; record since 2026-10-06

Started (UTC)	Incident	Impact	Lasted
2026-10-10 02:27	System Errors in AP-SOUTHEAST-1	major	1 h 44 min
2026-10-06 07:08	Intermittent Wasabi Console Access	minor	1 h 43 min

Get alerted when Wasabi goes down

No account. One email when Wasabi reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Wasabi as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Wasabi's current status in a README or an internal wiki. It updates by itself.

[![Wasabi status](https://upbutler.com/status/wasabi/badge.svg)](https://upbutler.com/status/wasabi)

Tell your outage from Wasabi's

Declare that your project depends on Wasabi. When one of your monitors fails while Wasabi has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - wasabi

Ask before you retry

curl -s https://upbutler.com/status/wasabi/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "wasabi",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Wasabi down right now?: No. As of 2026-10-10 07:19 UTC, Wasabi is up. This page reads the status again every 3 minutes.
Where does this status come from?: From Wasabi's own status page API at https://status.wasabi.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Wasabi's words.
Can I get an alert when Wasabi goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Wasabi reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/wasabi/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Wasabi status?: Fetch https://upbutler.com/status/wasabi/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"wasabi"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Wasabi's?: Add "wasabi" to the dependencies of your UpButler workspace. When one of your monitors fails while Wasabi has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Wasabi. Status and incident text belong to Wasabi and are read from their public status source; the probe result is UpButler's own measurement.