Is Wasabi down?

Last checked 1m ago
Current status
Wasabi is up

No incidents right now.

Official status page: https://status.wasabi.com · Polled every 5 minutes · 26 components tracked

Wasabi is operational right now. Last checked 1m ago; the most recent incident resolved 12d ago.

Real-time Wasabi status, recent outages, and incident history — pulled directly from Wasabi's official status page at https://status.wasabi.com every 5 minutes. Pingoru tracks 26 Wasabi services and has captured 16 incidents in the last 90 days (99.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Wasabi reports a new incident — free for 5 monitors, no credit card.

Users who monitor Wasabi also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud Linode View all 6,000+ providers
Wasabi uptime 99.76% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 5m
    Started Sep 01, 2026, 08:31 AM UTC · Resolved Sep 01, 2026, 10:36 AM UTC
    Wasabi Account Control Manager Console
    Timeline · 2 updates
    • investigating · Sep 01, 2026, 08:31 AM UTC

      We are currently investigating an issue with WACM reporting 0% storage utilization for subaccounts instead of the actual value

    • resolved · Sep 01, 2026, 10:36 AM UTC

      Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact [email protected] if you continue to see any problem related to this incident.

    Latest: Issue affecting WACM storage utilization data has been resolved. Data synchronization was completed and WACM should now present the correct values. Please contact [email protected]

  2. Resolved 2h 51m
    Started Aug 25, 2026, 11:46 PM UTC · Resolved Aug 26, 2026, 02:37 AM UTC
    US-East-1 (N. Virginia)
    Timeline · 3 updates
    • investigating · Aug 25, 2026, 11:46 PM UTC

      We are currently investigating issues happening in US-EAST-1 region that are impacting some of the PUT (Upload) api calls.

    • monitoring · Aug 26, 2026, 01:09 AM UTC

      Our team has identified the issue and fixed it. At the moment everything is back to normal and we will continue to monitor before we mark this event as resolved.

    • resolved · Aug 26, 2026, 02:37 AM UTC

      The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infrastructure issue on our backend. Our team identified the cause and applied a fix. Service has been fully restored. We apologize for any inconvenience.

    Latest: The issue has been resolved. Earlier today, some customers in our US-EAST-1 region may have experienced elevated latency or errors on storage PUT requests due to an internal infras…

  3. Resolved
    Started Aug 04, 2026, 02:20 PM UTC · Resolved Aug 04, 2026, 07:30 AM UTC
    Timeline · 1 update
    • resolved · Aug 04, 2026, 02:21 PM UTC

      On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastructure. Wasabi’s Operations Team was alerted by our automated monitoring systems to a drop on our ingestion traffic and started investigating. The updated was rolled back and services were fully restored on the region by 08:03 UTC.

    Latest: On 4 August 2026 from 07:36 UTC to 08:03 UTC, Wasabi S3 services in our Frankfurt (eu-central-2) region were unavailable due to a recent software update to our frontend infrastruct…

  4. Resolved
    Started Jul 15, 2026, 08:50 PM UTC · Resolved Jul 15, 2026, 07:00 PM UTC
    Timeline · 1 update
    • resolved · Jul 15, 2026, 08:50 PM UTC

      Between 2026-07-15 19:24 UTC and 20:26 UTC, a subset of customers experienced issues accessing the Wasabi Management Console when their requests were geo-routed through the Singapore console endpoint. Some affected customers also reported difficulty accessing bucket information through the Console. The incident occurred during the rollout of a new content delivery configuration for the Singapore console endpoint. Following deployment, some traffic routed through the new path experienced connectivity issues. Once the issue was identified, Wasabi rolled back the DNS changes, restoring the previous routing. Service recovered as DNS changes propagated globally. Following this incident, Wasabi is reviewing the deployment and validation process for regional console routing changes to improve pre-deployment testing, reduce customer impact during future rollouts, and strengthen monitoring of regional traffic after deployment.

    Latest: Between 2026-07-15 19:24 UTC and 20:26 UTC, a subset of customers experienced issues accessing the Wasabi Management Console when their requests were geo-routed through the Singapo…

  5. Resolved
    Started Jul 04, 2026, 05:45 PM UTC · Resolved Jul 04, 2026, 05:45 PM UTC
    Timeline · 1 update
    • resolved · Jul 09, 2026, 08:11 PM UTC

      On 4 July 2026, from 16:09 UTC to 17:37 UTC, customers experienced network error messages when accessing the Wasabi Management Console. Wasabi’s Operations team identified the issue and took action to restore service stability by rerouting traffic load. Wasabi Management Console functionality was fully restored by 17:37 UTC.  For any questions, please reach out to [email protected].

    Latest: On 4 July 2026, from 16:09 UTC to 17:37 UTC, customers experienced network error messages when accessing the Wasabi Management Console. Wasabi’s Operations team identified the issu…

See the full Wasabi outage history

2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Wasabi outage history →

Or sign up free to get alerts when Wasabi breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 7 incidents View full outage history →