Is Wasabi Down?

No — Wasabi is up

Wasabi's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 364 ms

Right now

The verdict is the worse of these two. How we decide

Wasabi's status page

status.wasabi.com · read 3 minutes ago · checked every 3 minutes

Operational

Wasabi's components, as its status page reports them
Component	Status
Wasabi Account Control API	Operational
Wasabi Account Control Manager Console	Operational
Wasabi Custom Cloud Console	Operational
Wasabi Management Console	Operational
Wasabi.com the service itself	Operational
Wasabi AiR	Operational
WACM Connect API	Operational
docs.wasabi.com	Operational

19 locations All operational

Open their status page

FlareWarden checks

wasabi.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 364 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 89 ms
Chicago reachable, 685 ms
San Jose reachable, 678 ms
Singapore reachable, 249 ms
Stockholm reachable, 502 ms
Sydney reachable, 134 ms
Tokyo reachable, 180 ms
Toronto reachable, 398 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	32 ms	4 ms	15 ms	70 ms
Chicago	593 ms	1 ms	23 ms	647 ms
San Jose	637 ms	2 ms	9 ms	668 ms
Singapore	214 ms	2 ms	8 ms	239 ms
Stockholm	317 ms	1 ms	53 ms	410 ms
Sydney	99 ms	1 ms	8 ms	125 ms
Tokyo	126 ms	1 ms	10 ms	169 ms
Toronto	288 ms	11 ms	25 ms	357 ms

We check that wasabi.com loads, not every feature behind it. Test it yourself

History

Incidents Wasabi reported

Since Oct 22, 15 days · from status.wasabi.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Wasabi website availability

Measured by FlareWarden · wasabi.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 384ms

Last 30 days

66-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of wasabi.com from multiple regions every 6 hours. Wasabi's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 66 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Wasabi does

Wasabi is an object storage provider with an S3-compatible API, sold mainly on flat pricing with no egress or request fees. Backup software, media archives and surveillance recorders write to it as a drop-in replacement for Amazon S3. Every bucket lives in exactly one named storage region chosen when it was created.

What an outage looks like

Backup jobs and sync tools fail with S3 API errors or timeouts against one endpoint while other jobs continue, because Wasabi reports each storage region as its own component. The management console is tracked separately from storage, so administrators can lose the web console while applications keep reading and writing buckets normally, and the reverse also happens.

What to do about it

Open status.wasabi.com and find the region your bucket is in rather than the summary. Wasabi lists its regions individually, including US-Central-1 in Texas, US-East-1 and US-East-2 in Northern Virginia, US-West-1 in Oregon, EU-Central-1 in Amsterdam, EU-West-1 in London and AP-Northeast-1 in Tokyo. The Management Console, Account Control API and Wasabi.com are separate entries again.

Is it down for everyone, or just you?

If this page says Wasabi is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

AWS

DigitalOcean

Cloudflare

Hetzner

Wasabi outage FAQ

Wasabi says operational but my backups are failing. Why?

Read the region rather than the headline. Wasabi reports every storage region as its own component, so a bucket in EU-Central-1 can be unreachable while every other region is fine and the overall page looks healthy. Find the endpoint your backup software is configured against, match it to the region entry, and check that specific one.

Can I still access my data if the Wasabi console is down?

Often yes. The Wasabi Management Console, the Account Control Manager Console and the Account Control API are components separate from the storage regions themselves. An incident confined to the console means you cannot browse buckets or manage users through the web interface, while S3 API traffic from backup software and applications continues against the same buckets.

Which region is my bucket in?

The endpoint hostname your software uses names the region, and a bucket cannot move between regions after creation. Check the endpoint configured in your backup tool or SDK, then find that region on the status page. If you use several buckets created at different times, they may sit in different regions and be affected independently.

Does a Wasabi outage affect Amazon S3 or my other storage?

No. Wasabi runs its own infrastructure and is unrelated to Amazon S3 beyond sharing an API shape. Software written against S3 can point at either, which is the whole appeal, but an incident at one says nothing about the other. If you replicate across both, an outage at Wasabi should leave the Amazon copy readable.

Will my backup software retry after a Wasabi outage?

That depends on your backup tool, not on Wasabi, and Wasabi does not publish client retry behaviour. Most backup products retry a failed job on their next scheduled run rather than immediately. Check the job history in your own software once the region recovers, and confirm the most recent successful backup rather than assuming the schedule caught up.

How we measure this

We request Wasabi's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Wasabi publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Wasabi itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Wasabi goes down

We check Wasabi every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required