Backblaze Outage History

11 incidents recorded over the last 365 days, 10 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Backblaze status99.02% uptime history

Every Recorded Backblaze Incident

Backblaze incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 21, 2026EU Region Uploads FailingAll uploads are failing with the error Storage class not supported on this cluster: STANDARD36 minResolved
Aug 19, 2026Degraded Uploads in US East regionca005 users can't log in3h 0mResolved
Aug 19, 2026US West Core Services MaintenanceBackblaze will be investing in our infrastructure with routine, but extended, maintenance in the US West region. The expected duration of this maintenance is from 10:00-16:00 Pacific Time. Most customers will not…13h 47mResolved
Aug 17, 2026Intermittent upload and download errors in EU CentralSeveral customers affected including peta customers—Investigating
Aug 12, 2026CA East Core Services Maintenance - 8/12/2026Backblaze will be investing in our infrastructure with routine, but extended, maintenance in the CA East region. The expected duration of this maintenance is from 12:30-16:00 Pacific Time. Most customers will not see…4h 31mResolved
Aug 12, 2026US East Core Services Maintenance - 8/12/2026Backblaze will be investing in our infrastructure with routine, but extended, maintenance in the US East region. The expected duration of this maintenance is from 10:00-13:30 Pacific Time. Most customers will not see…4h 10mResolved
Jun 29, 2026IPv6 S3 VIPs are not being advertised in our CA-East regionSome customers with IPv6 addresses hard-coded for CA East may experience connectivity issues. Customers using DNS resolution are not affected and will continue to reach our service normally via IPv4836h 42mResolved
Jun 24, 2026Some customers in US West experiencing issues with login and accessing the web uiSome customers in US West will have issues logging in and using the Web UI963h 37mResolved
Jun 11, 2026Some Customers in US-East may be experiencing Upload FailuresSome customers experiencing upload failures7h 37mResolved
Jun 2, 2026Some users in US West may be experiencing issues with logging in.20 minResolved
Mar 31, 2026Some customers in US West might be experiencing upload issues.Some customers may notice slower file uploads due to delays in the system’s initial response. Files will still upload successfully, but the process may take longer than usual.2h 8mResolved

How to Read This Backblaze Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Backblaze acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Backblaze outage in this window ran 40d 3h, against a mean recovery of 7d 15h. If you depend on Backblaze in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.