Increased Agent Drive Latency on us-was-1
Blaxel reports increased Agent Drive latency on us-was-1. Blaxel identified the cause, deployed a fix, and monitored recovery. Blaxel states that the incident is resolved, and it lasted 3 hours and 32 minutes.
State
Resolved
Started
Lasted
3 h 32 min
Worst impact
Partial outage
Timeline
4 updatesIdentified
2 h 15 min 64%
Monitoring
1 h 16 min 36%
Updates
Times in UTCAs posted by Blaxel
This incident has been resolved, and service is operating normally again. Thanks for your patience.
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.
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
28
Days with an incident
23
Median duration
1 h 26 min
This incident
2.5× the median
Other Blaxel incidents
All incidentsBlaxel·Elevated Creation Errors in eu-lon-1 Region
Blaxel reported elevated creation errors in the eu-lon-1 region. Some users could not create new workloads in that region, and existing workloads were not affected. Blaxel says the incident is resolved and the service operates normally again. The incident lasted about 2 hours and 40 minutes.
Blaxel·Drive mount and write failures
Blaxel reported drive mount and write failures. The incident affected some users and caused degraded performance. Blaxel identified the cause and deployed a fix. Blaxel monitored the systems for recovery. The incident is resolved. It lasted about 88 minutes.
Blaxel·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.
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