Drive mount and write failures
Blaxel reports drive mount and write failures. The incident started at 07:27 UTC on 3 November 2026. Blaxel deployed a fix and now monitors the systems to confirm recovery.
State
Monitoring
Started
1 h ago
2026-11-03 07:27 UTC
Ongoing for
1 h 23 min
Worst impact
Partial outage
Timeline
2 updatesIdentified
1 h 21 min 98%
Monitoring
2 min 2%
Updates
Times in UTCAs posted by Blaxel
A fix has been deployed, and we’re monitoring to confirm recovery. A small amount of residual impact may persist while systems stabilize.
We’ve identified the cause and are working on a fix. Some users may continue to experience degraded performance while we resolve the issue. We’ll share another update as soon as possible.
Blaxel in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
21
Median duration
1 h 22 min
This incident
About the median
Other Blaxel incidents
All incidentsBlaxel·Workloads Unavailable on Older Generation
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Blaxel·Drive mount and write failures
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Blaxel·Sandbox proxy unavailable on us-was-1
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Blaxel·Some sandboxes are unavailable in us-was-1
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Blaxel·Elevated sandbox creation failures in us-was-1
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Follow Blaxel
Your coding agent knows when Blaxel is down, and tells you when a failure is theirs, not yours. You can also get Blaxel 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 "blaxel" and tell me if Blaxel 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=blaxel/feed subscribe https://outages.cc/feed.xml?providers=blaxelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane