Live

Docker Build Cloud maintenance

MaintenanceOfficial update

We’re performing planned maintenance on Docker Build Cloud. Some builds may be interrupted or fail to start during this window. We’ll mark this complete when the work is finished.

The latest update from Docker.

State

Scheduled

Started

Ongoing for

1 h 13 min

Worst impact

Maintenance

Timeline

1 update
21:4121:5922:1722:3522:53
MaintenanceUpdate postedTimes in UTC

Scheduled

1 h 13 min 100%

Updates

Times in UTC

As posted by Docker

Scheduled

We’re performing planned maintenance on Docker Build Cloud. Some builds may be interrupted or fail to start during this window. We’ll mark this complete when the work is finished.

Docker in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

11 min

This incident

Not comparable

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

1 h 26 min
median 11 min
90 days agoToday

Other Docker incidents

All incidents

Follow Docker

Your coding agent knows when Docker is down, and tells you when a failure is theirs, not yours. You can also get Docker 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 "docker" and tell me if Docker 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=docker
Slack
/feed subscribe https://outages.cc/feed.xml?providers=docker

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane