Cerebrium reported "Slow container image pulls in eu-north1" on its status page at 2026-09-08 15:36 UTC.

Cerebrium lists these components: Registry EU.

When did the incident start and end?

It started at 2026-09-08 15:36 UTC and ended at 2026-09-08 16:42 UTC. It lasted 1 h 6 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.

CerebriumIncident · 2026-09-08 15:36 UTC

Slow container image pulls in eu-north1

ResolvedOfficial update

The issue has been resolved.

The latest update from Cerebrium.

State

Resolved

Started

56 d ago

2026-09-08 15:36 UTC

Lasted

1 h 6 min

until 2026-09-08 16:42 UTC

Worst impact

Degraded

Timeline

2 updates

15:3615:5216:0916:2516:42

DegradedUpdate postedTimes in UTC

Degraded

1 h 6 min 100%

Updates

Times in UTC

As posted by Cerebrium

Resolved2026-09-08 16:42 UTC

The issue has been resolved.

Degraded2026-09-08 15:36 UTC

We're seeing elevated S3 latency in eu-north1, which is slowing container image pulls. New deploys and cold starts in that region are taking longer than usual. Inference is unaffected: apps with warm replicas are serving traffic, and other regions are running normally. We're currently investigating and will post an update shortly.

Affected components

Registry EU

Cerebrium in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 6 min

This incident

About the median

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

7 h 20 min

median 1 h 6 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.

Resolvedresolved 19 d ago

Cerebrium·Provider network outage: Nebius eu-north1

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

Resolvedresolved 62 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane