Cerebrium lists these components: Build Service.

When did the incident start and end?

It started at 2026-11-11 08:36 UTC and ended at 2026-11-11 12:53 UTC. It lasted 4 h 18 min.

How do I get alerts for Cerebrium?

Subscribe to the Cerebrium live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Cerebrium. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CerebriumIncident ·

Builds failing

Q: What happened?

Cerebrium reported "Builds failing" on its status page at 2026-11-11 08:36 UTC. Cerebrium reports that new builds failed across all regions on the Build Service. The incident is resolved. It lasted from 08:36 UTC to 12:53 UTC. Cerebrium states that any build submitted between 08:36 and 11:09 UTC should be re-run.

ResolvedOfficial update

Cerebrium reports that new builds failed across all regions on the Build Service. The incident is resolved. It lasted from 08:36 UTC to 12:53 UTC. Cerebrium states that any build submitted between 08:36 and 11:09 UTC should be re-run.

State

Resolved

Started

Lasted

4 h 18 min

Worst impact

Major outage

Timeline

2 updates

08:3609:4010:4411:4912:53

Major outageUpdate postedTimes in UTC

Downtime

4 h 18 min 100%

Updates

Times in UTC

As posted by Cerebrium

Resolved

The issue has been resolved and builds are completing normally again. Any build submitted between 08:36 and 11:09 UTC should be re-run. Running apps and inference traffic were not affected at any point.

Downtime

We are investigating an issue causing new builds to fail across all regions since approximately 08:36 UTC today. Running apps are not affected and continue to serve traffic normally. Inference API, Files and the Dashboard remain fully operational. No customer action is required. We will update this page as we restore the service.

Affected components

Build Service

Cerebrium in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 42 min

This incident

1.6× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 h 20 min

median 2 h 42 min

90 days agoToday

Other Cerebrium incidents

All incidents

Cerebrium·Nebius Clusters are unavailable

The issue with Nebius has been resolved and US and EU clusters are back online.

Resolved

Cerebrium·Slow container image pulls in eu-north1

The issue has been resolved.

Resolved

Cerebrium·Provider network outage: Nebius eu-north1

The issue has been resolved and the provider and region are stable again.

Resolved

Follow Cerebrium

Your coding agent knows when Cerebrium is down, and tells you when a failure is theirs, not yours. You can also get Cerebrium 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.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 "cerebrium" and tell me if Cerebrium 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.live/feed.xml?providers=cerebrium

Slack

/feed subscribe https://outages.live/feed.xml?providers=cerebrium

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane