Namespace incident
Subset of container image pulls from external registries failing
Resolved after 1 hour, on September 16, 2026.
The fix addressed the root cause and all images are being served correctly.
Update timeline
- investigating Sep 16, 2026, 08:15 PM UTC
We've received reports of a subset of container image pulls failing, the team is investigating.
- identified Sep 16, 2026, 08:30 PM UTC
Pulls from external registries go through a caching layer in our infrastructure, which is serving incorrect data for a small subset of images. A mitigation has been applied to restore correct behavior for failing images.
- identified Sep 16, 2026, 08:52 PM UTC
There is still a small set of images for which an incorrect response is served, we've identified the cause and are rolling out a fix.
- resolved Sep 16, 2026, 09:15 PM UTC
The fix addressed the root cause and all images are being served correctly.
- resolved Sep 16, 2026, 09:15 PM UTC
The fix addressed the root cause and all images are being served correctly.
Your product runs on more than Namespace
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services