Semaphore: Docker Hub outage affecting image push/pulls in Semaphore
AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents
Semaphore’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 33 min vs AWS’s own post)
“…cing an outage, which is affecting image push/pulls in CI. We are also monitoring broader AWS service issues, which could indirectly affect some users' workloads. Image push/pulls are still being affe…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
root --> before
h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
root --> h1
h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
root --> h4
later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
root --> later
p0["Twilio<br/>posted +15 min"]:::blames
root --> p0
k0["BigCommerce<br/>+2 h 46 min"]:::hop2
p0 -->|"blamed Twilio"| k0
p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
root -.-> p1
k1["Rootly<br/>+10 h 23 min"]:::hop2
p1 -->|"blamed Webflow"| k1
p2["Baseten<br/>posted +4 min"]:::blames
root --> p2
k2["Zed<br/>+26 h 20 min"]:::hop2
p2 -->|"blamed Baseten"| k2
me["Semaphore (this incident)<br/>posted +1 h 33 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Semaphore
Timeline of updates
- identified
Docker Hub is experiencing an outage, which is affecting image push/pulls in CI. We are also monitoring broader AWS service issues, which could indirectly affect some users' workloads.
- identified
Image push/pulls are still being affected by the Docker Hub outage. We are closely monitoring the situation. We are continuing to monitor broader AWS service issues, which could still indirectly affect some users' workloads.
- identified
We are continuing to monitor the situation: - Image push/pulls are still being affected by the Docker Hub outage. - Broader AWS service issues could still indirectly affect some users' workloads.
- identified
We are continuing to monitor the situation: - Image push/pulls are still being affected by the Docker Hub outage. - Broader AWS service issues could still indirectly affect some users' workloads.
- monitoring
Issues with image push/pulls seem to be resolved. We are still closely monitoring the situation.
- identified
Image push/pulls seem to be affected again by the ongoing Docker Hub outage. We continue to monitor the situation.
- identified
Image push/pulls seem to be affected again by the ongoing Docker Hub outage. We continue to monitor the situation.
- identified
Image push/pulls seem to be affected by the ongoing Docker Hub outage. We keep monitoring the situation.
- identified
Some image push/pulls seem to be affected by the ongoing Docker Hub outage. Our team is monitoring the situation.
- identified
Image push/pulls may be affected by the ongoing Docker Hub outage. We continue to monitor the situation.
- monitoring
Issues with image push/pulls seem to be resolved. We are still closely monitoring the situation.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:53 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
7f97d4d22b84d782…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).