Elevated Errors for B2 Cloud Storage in US East
B2 Cloud Storage uploads and downloads fail at elevated rates in the US East region. Backblaze applied a mitigation, and uploads and downloads now work normally. Backblaze monitors the incident and continues work to recover all services.
State
Mitigation-applied-and-monitoring
Started
Ongoing for
25 h 35 min
Worst impact
Partial outage
Timeline
8 updatesInvestigating
1 h 54 min 7%
Identified
51 min 3%
Mitigation-applied-and-monitoring
22 h 50 min 89%
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 were failing at elevated rates. Uploads and downloads were are affected, and some customers may have also seen slower responses. Backblaze applied mitigation and uploads and downloads are now working normally. The Operations teams are continuing to work on this incident to ensure all services are fully recovered.
Since about 10:00 UTC on November 6, some B2 Cloud Storage requests in our US East region were failing at elevated rates. Uploads and downloads were are affected, and some customers may have also seen slower responses. Backblaze applied mitigation and uploads and downloads are now working normally. The Operations teams are continuing to work on this incident to ensure all services are fully recovered.
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.
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.
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
9
Median duration
3 days
This incident
60% shorter than the median
Other Backblaze incidents
All incidentsBackblaze·Unable to login to EWC in production
Backblaze reports that customers cannot log in to the Enterprise Web Console, and organization accounts cannot create buckets. Organization Services APIs are unavailable. Backblaze resolved the incident after 18 hours and 30 minutes.
Backblaze·Customers in the EU region might be facing issues accessing some files
Some files are not available to customers in the EU region. Backblaze identified the issue and applied a fix. Backblaze continues to monitor the services and has completed additional cleanup.
Backblaze·Customers in the US east region might be facing issues with downloads
Backblaze reports download problems for some customers in the US east region. The issue is resolved. It lasted about 4 days and 14 hours.
Backblaze·EU Region High Upload Failures
Backblaze reports high upload failures in the EU region. The failures affect some customers in that region. Backblaze is investigating and states that some upload issues remain after earlier mitigation.
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.cc/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.cc/feed.xml?providers=backblaze/feed subscribe https://outages.cc/feed.xml?providers=backblazeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane