outages.live
Live
DockerMaintenance · 2026-11-02 22:37 UTC

Authentication tenant maintenance

MaintenanceOfficial update

We will be performing maintenance on our authentication tenant. No disruption is expected.

The latest update from Docker.

State

Scheduled

Started

1 h ago

2026-11-02 22:37 UTC

Ongoing for

1 h 18 min

Worst impact

Maintenance

Timeline

1 update
22:3722:5723:1623:3623:55
MaintenanceUpdate postedTimes in UTC

Scheduled

1 h 18 min 100%

Updates

Times in UTC

As posted by Docker

Scheduled2026-11-02 22:39 UTC

We will be performing maintenance on our authentication tenant. No disruption is expected.

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

Docker·Degraded performance and intermittent availability on Docker Hub

The incident has been resolved. Docker Hub is operating normally, and we have confirmed that response times and availability have returned to expected levels for all services.

Resolvedresolved 12 d ago

Docker·Hub Registry Authenticated Actions Failing

All functionality is restored on Hub Registry.

Resolvedresolved 24 d ago

Docker·Issues viewing newly pushed images and tags

Newly pushed images and tags are now processing and appearing normally. We have resolved the issue and confirmed that pushed tags were stored correctly and were not lost.

Resolvedresolved 49 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane