outages.live
Live

Blaxel

Blaxel is operational

Checked 2 min ago Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Blaxel status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Blaxel since Nov 3, 2026. The days before that show only what Blaxel published.

Incidents in 90 days

25

Days with an incident

21

Median duration

1 h 22 min

Longest incident

16 h

Components

8
Model API Operational
90 days agoNo incidentsToday
Agents Operational
90 days agoNo incidentsToday
MCP Operational
90 days agoNo incidentsToday
Jobs Operational
90 days agoNo incidentsToday
Sandboxes Operational
90 days agoNo incidentsToday
Previews Operational
90 days agoNo incidentsToday
Console Operational
90 days agoNo incidentsToday
Website Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Nov 3, 2026

Duration21 min02:16 to 02:37Workloads Unavailable on Older GenerationDegraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 30, 2026

Duration1 h 24 min20:02 to 21:26Drive mount and write failuresPartial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Duration45 min18:13 to 18:58Sandbox proxy unavailable on us-was-1Degraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 29, 2026

Duration11 h 59 min05:03 to 17:01Some sandboxes are unavailable in us-was-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 28, 2026

Duration3 h 24 min22:36 to 02:00Elevated sandbox creation failures in us-was-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Duration6 h 40 min17:45 to 00:25Increase in volume errorsPartial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Duration1 h 11 min06:20 to 07:31Increase in drive mounting errorsDegraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 19, 2026

Duration2 h 3 min19:28 to 21:31Elevated sandbox creation errors in us-pdx-1Degraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 16, 2026

Duration34 min15:07 to 15:42Increased workload unavailability on us-pdx-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 14, 2026

Duration14 min16:46 to 17:00Elevated agent proxy errors in eu-fra-1Degraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 10, 2026

Duration1 h 16 min19:06 to 20:22Elevated sandbox creation failures in us-was-1Notice

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 3, 2026

Duration1 h 22 min06:13 to 07:34Increased workload unavailability on us-pdx-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Duration1 h05:10 to 06:11Workload unavailability on us-was-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Oct 1, 2026

Duration2 h 28 min02:39 to 05:07Increased workload unavailability in us-was-1Major outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Sep 30, 2026

Duration42 min17:47 to 18:29Deployment failures on us-was-1Partial outage

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Sep 29, 2026

Duration36 min15:35 to 16:11Elevated error rates on sandbox creation in us-was-1Degraded

This incident has been resolved, and service is operating normally again. Thanks for your patience.

Duration6 h 21 min03:42 to 10:03Increased mount and connection errors with Agent Drives in us-was-1Partial outage

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=blaxel
Slack
/feed subscribe https://outages.cc/feed.xml?providers=blaxel

Go from tracking outages to fixing production issues with Polylane.

Try Polylane