Backblaze
Backblaze is reporting partial outage
Customers in the US east region might be facing issues with downloads
Backblaze reports that downloads do not work for some customers in the US east region. Backblaze applied a mitigation and now monitors the service. The service has returned to normal and remains stable.
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.
History
Incidents in 90 days
2
Days with an incident
3
Median duration
No data
Longest incident
No data
Components
4No incident in the last 90 days.
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=backblazeGo from tracking outages to fixing production issues with Polylane.
Try Polylane