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…”
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.
What changed
Struck in red is what Semaphore removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Docker Hub outage affecting image push/pulls in Semaphore
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-20 08:44 UTC
AddedResolved time#5
Before: not present
After: 2025-10-21 01:00 UTC
AddedAffected components#6
Before: not present
After: Semaphore
AddedUpdateidentified#7
Before: not present
After: 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.
AddedUpdateidentified#8
Before: not present
After: 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.
AddedUpdateidentified#9
Before: not present
After: 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.
AddedUpdateidentified#10
Before: not present
After: 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.
AddedUpdatemonitoring#11
Before: not present
After: Issues with image push/pulls seem to be resolved. We are still closely monitoring the situation.
AddedUpdateidentified#12
Before: not present
After: Image push/pulls seem to be affected again by the ongoing Docker Hub outage. We continue to monitor the situation.
AddedUpdateidentified#13
Before: not present
After: Image push/pulls seem to be affected again by the ongoing Docker Hub outage. We continue to monitor the situation.
AddedUpdateidentified#14
Before: not present
After: Image push/pulls seem to be affected by the ongoing Docker Hub outage. We keep monitoring the situation.
AddedUpdateidentified#15
Before: not present
After: Some image push/pulls seem to be affected by the ongoing Docker Hub outage. Our team is monitoring the situation.
AddedUpdateidentified#16
Before: not present
After: Image push/pulls may be affected by the ongoing Docker Hub outage. We continue to monitor the situation.
AddedUpdatemonitoring#17
Before: not present
After: Issues with image push/pulls seem to be resolved. We are still closely monitoring the situation.