Elevated Errors for B2 Cloud Storage in US East
Backblaze reports failures in some B2 Cloud Storage requests in the US East region. Uploads and downloads are affected, and some Backblaze services that depend on this region may be affected too. Backblaze is investigating the issue and reports that data already stored is not affected.
State
Investigating
Started
Ongoing for
1 h 37 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 37 min 100%
Updates
Times in UTCAs posted by Backblaze
Since about 10:00 UTC on November 6, some B2 Cloud Storage requests in our US East region have been failing at elevated rates. Uploads and downloads are affected, and some customers may also see slower responses. Some Backblaze services that depend on this region may be affected too. Our engineers are working to restore full service. Data already stored is not affected. We will post another update within 60 minutes.
We continue to investigate an issue causing some B2 Cloud Storage uploads to fail. Our team is working to restore normal operation. We will provide updates as more information becomes available.
Cluster 005 Cassandra disk space issues causing upload failures and Cooper task processing errors
We continue to investigate an issue causing some B2 Cloud Storage uploads to fail. Our team is working to restore normal operation. We will provide updates as more information becomes available.
Backblaze in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
8
Median duration
5 days
This incident
99% shorter than the median
Other Backblaze incidents
All incidentsBackblaze·Unable to login to EWC in production
Backblaze cannot log in customers to the Enterprise Web Console. Bucket creation for organization accounts also does not work, because all Organization Services APIs are unavailable. Backblaze applied a mitigation and monitors the service. Permission recovery is in progress.
Backblaze·Customers in the EU region might be facing issues accessing some files
Backblaze reports that some customer files in the EU region may be temporarily unavailable. Backblaze identified the issue and applied a fix. Backblaze continues to monitor services and prepares further checks to verify recovery.
Backblaze·Customers in the US east region might be facing issues with downloads
Backblaze reports that downloads did not work for some customers in the US east region. Backblaze later reported that service returned to normal and stayed stable. Backblaze resolved the incident on 3 November 2026, after 4 days and 14 hours.
Backblaze·EU Region High Upload Failures
Backblaze reports high upload failures in the EU region. Some customers continue to have upload problems. Backblaze is investigating and will give more information when it is available.
Follow Backblaze
Your coding agent knows when Backblaze is down, and tells you when a failure is theirs, not yours. You can also get Backblaze incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "backblaze" and tell me if Backblaze has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=backblaze/feed subscribe https://outages.live/feed.xml?providers=backblazeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane