New account sign-ups temporarily unavailable in EU Central
New account sign-ups do not work in the EU Central region. Backblaze reports that the outage is resolved. The outage lasted about 40 hours.
State
Resolved
Started
Lasted
40 h
Worst impact
Major outage
Timeline
5 updatesInvestigating
2 h 45 min 7%
Resolved
37 h 15 min 93%
Updates
Times in UTCAs posted by Backblaze
New account sign-ups in the EU Central region are temporarily unavailable.
New account sign-ups in the EU Central region are temporarily unavailable. This status will be updated as the situation changes.
Currently, no customer impact, but if the upload rate doesn't drop in the next few hours all of 003 will be offline for days or weeks.
Backblaze in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
12
Median duration
3 days
This incident
48% shorter than the median
Other Backblaze incidents
All incidentsBackblaze·Elevated Errors for B2 Cloud Storage in US East
B2 Cloud Storage uploads and downloads in the US East region had elevated errors. Backblaze reported that the incident is resolved. It lasted from about 10:00 UTC on November 6 to November 9.
Backblaze·Unable to login to EWC in production
Backblaze customers cannot log in to the Enterprise Web Console, and organization accounts cannot create buckets. The Organization Services APIs are unavailable. Backblaze reports that the issue is resolved. The outage lasted about 18 hours and 30 minutes.
Backblaze·Customers in the EU region might be facing issues accessing some files
Backblaze customers in the EU region cannot access some files. Backblaze resolved the incident. It lasted from 5 November 2026 to 9 November 2026, about 4 days and 16 hours.
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