Skip to main content
Wasabi logo

Is Wasabi Down?

No — Wasabi is up

Reachable from all 8 checked regions

Average response time: 348ms

Last checked · 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
260ms
Avg response, 30 days

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

30-day history

20-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: 100.00% uptime, 15 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 24 checks
Sep 4: 100.00% uptime, 22 checks
Sep 5: 100.00% uptime, 21 checks
Sep 6: 100.00% uptime, 31 checks
Sep 7: 100.00% uptime, 24 checks
Sep 8: 100.00% uptime, 24 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 24 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 39 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 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
168ms
DNS 23ms TCP 14ms TLS 24ms TTFB 91ms
arn
603ms
DNS 381ms TCP 1ms TLS 52ms TTFB 494ms
bom
203ms
DNS 134ms TCP 1ms TLS 9ms TTFB 184ms
cdg
225ms
DNS 88ms TCP 8ms TLS 25ms TTFB 185ms
dfw
608ms
DNS 357ms TCP 0ms TLS 56ms TTFB 486ms
ewr
386ms
DNS 289ms TCP 1ms TLS 20ms TTFB 355ms
fra
139ms
DNS 67ms TCP 1ms TLS 13ms TTFB 119ms
yyz
459ms
DNS 270ms TCP 12ms TLS 33ms TTFB 407ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
DigitalOcean
DigitalOcean
Cloudflare
Cloudflare
Hetzner
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 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required