Is Backblaze down right now?

No. Our checks are finding no problems with Backblaze right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Backblaze continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are backup not completing, files won't sync, cloud saves not loading, upload failing, API errors, can't connect and can't log in. Those are the options the report button offers for Backblaze, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Backblaze specifically, Backblaze has separate systems for personal computer backup, B2 API availability, and account authentication, each of which can fail independently. A user's backup client may be blocked by their ISP or firewall while B2 API remains operational for other users. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Backblaze, try uploading a test file directly to B2 via the web dashboard or API, and check your backup client logs for specific error codes. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Backblaze's side. Specifically: do not repeatedly trigger backup jobs or retry uploads in rapid succession, as this can queue thousands of requests that will all execute when service returns, overwhelming your connection and delaying recovery of your actual data. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Backblaze does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe backblaze.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Backblaze says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.backblaze.com, and it is linked further up this page. That is Backblaze's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Backblaze or backblaze.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Backblaze's own support, not us.