Agent Drive storage maintenance (us-was-1)
We’ll be performing scheduled maintenance on Agent Drive storage in **us-was-1** during the scheduled window. Writes may experience brief interruptions during maintenance and can be safely retried. Reads and existing data will remain unaffected. We’ll share updates here as maintenance progresses.
The latest update from Blaxel.
State
Scheduled
Started
Ongoing for
5 h 30 min
Worst impact
Maintenance
Timeline
1 updateScheduled
5 h 30 min 100%
Updates
Times in UTCAs posted by Blaxel
We’ll be performing scheduled maintenance on Agent Drive storage in **us-was-1** during the scheduled window. Writes may experience brief interruptions during maintenance and can be safely retried. Reads and existing data will remain unaffected. We’ll share updates here as maintenance progresses.
Blaxel in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
25
Median duration
1 h 26 min
This incident
Not comparable
Other Blaxel incidents
All incidentsBlaxel·Elevated Sandbox Creation Failures
Blaxel reported elevated sandbox creation failures. Blaxel later reported that the incident is resolved. The outage lasted about 89 minutes.
Blaxel·Elevated errors on sandbox creation
Blaxel reported elevated errors on sandbox creation. Blaxel identified the cause, deployed a fix, and monitored recovery. The incident is resolved and lasted 14 minutes.
Blaxel·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, but existing workloads were unaffected. Blaxel resolved the incident, which lasted 159 minutes.
Blaxel·Increased Agent Drive Latency on us-was-1
Blaxel reported increased Agent Drive latency on us-was-1. Blaxel identified the cause and deployed a fix. Blaxel later reported that the incident is resolved, and the outage lasted about 3 hours and 32 minutes.
Blaxel·Drive mount and write failures
Blaxel reported drive mount and write failures. The provider identified the cause, deployed a fix, and monitored recovery. Blaxel says the incident is resolved and the service operates normally again. The outage lasted about 88 minutes.
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.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 "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.live/feed.xml?providers=blaxel/feed subscribe https://outages.live/feed.xml?providers=blaxelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane