Is Wasabi Down?

No — Wasabi is up

Reachable from all 8 checked regions

Average response time: 370ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.wasabi.com

Wasabi uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

428ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 41 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

41-day clean streak

Sep 13 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

191ms

DNS 99ms TCP 8ms TLS 22ms TTFB 166ms

arn

541ms

DNS 342ms TCP 1ms TLS 56ms TTFB 444ms

cdg

502ms

DNS 92ms TCP 9ms TLS 24ms TTFB 462ms

dfw

584ms

DNS 386ms TCP 25ms TLS 29ms TTFB 484ms

sin

256ms

DNS 205ms TCP 1ms TLS 10ms TTFB 249ms

sjc

251ms

DNS 101ms TCP 1ms TLS 11ms TTFB 239ms

syd

254ms

DNS 192ms TCP 1ms TLS 9ms TTFB 244ms

yyz

386ms

DNS 245ms TCP 12ms TLS 26ms TTFB 335ms

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.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Wasabi goes down

This page refreshes every 6 hours. 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