outages.live
Live
Cerebrium logo

Cerebrium

Cerebrium 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 Cerebrium status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

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

Incidents in 90 days

3

Days with an incident

3

Median duration

1 h 6 min

Longest incident

7 h 20 min

Components

14

Landing Page

Cerebrium Landing Page Operational
90 days agoNo incidentsToday

Dashboard

Cerebrium Dashboard Operational
90 days agoNo incidentsToday

Builds

Build Service Operational
90 days agoNo incidentsToday
Build Service Maintenance Operational
90 days agoNo incidentsToday
Registry US Operational
90 days agoNo incidentsToday
Registry EU Operational
90 days ago1 day with an incidentToday

Inference API

US Operational
90 days ago1 day with an incidentToday
EU Operational
90 days ago2 days with an incidentToday
Global Routing Operational
90 days agoNo incidentsToday

Files & Volumes

Files US Operational
90 days agoNo incidentsToday
Files EU Operational
90 days agoNo incidentsToday

Metrics

Metrics (Global) Operational
90 days agoNo incidentsToday

Docs

Docs Operational
90 days agoNo incidentsToday

REST API

REST API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 15, 2026

Duration17 min17:34 to 17:51Nebius Clusters are unavailableDegraded

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

Sep 8, 2026

Duration1 h 6 min15:36 to 16:42Slow container image pulls in eu-north1Degraded

The issue has been resolved.

Sep 2, 2026

Duration7 h 20 min09:57 to 17:17Provider network outage: Nebius eu-north1Degraded

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

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.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 "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.cc/feed.xml?providers=cerebrium
Slack
/feed subscribe https://outages.cc/feed.xml?providers=cerebrium

Go from tracking outages to fixing production issues with Polylane.

Try Polylane