Docker reported "Issues viewing newly pushed images and tags" on its status page at 2026-09-14 13:29 UTC.

Docker did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-14 13:29 UTC and ended at 2026-09-14 13:34 UTC. It lasted 5 min.

How do I get alerts for Docker?

Subscribe to the Docker 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 Docker. outages.live reads it every few minutes and keeps every update.

DockerIncident · 2026-09-14 13:29 UTC

Issues viewing newly pushed images and tags

ResolvedOfficial update

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.

The latest update from Docker.

State

Resolved

Started

48 d ago

2026-09-14 13:29 UTC

Lasted

5 min

until 2026-09-14 13:34 UTC

Worst impact

Partial outage

Timeline

2 updates

13:2913:3013:3213:3313:34

Partial outageUpdate postedTimes in UTC

Monitoring

5 min 100%

Updates

Times in UTC

As posted by Docker

Resolved2026-09-14 13:34 UTC

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.

Monitoring2026-09-14 13:29 UTC

We have restored processing for newly pushed images and tags and are monitoring recovery. Pushed tags were stored correctly and have not been lost.

Docker in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

11 min

This incident

48% shorter than the median

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 11 d ago

Docker·Hub Registry Authenticated Actions Failing

All functionality is restored on Hub Registry.

Resolvedresolved 23 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.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