Semaphore: Sporadic slow Docker push towards AWS ECR
Timeline of updates
- resolved
We are happy to report that the issue with slow pushes towards AWS ECR is resolved. With great help from the AWS networking team, we reached the conclusion that the cause was ISP to ISP congestion caused by a damaged fiber-optic cable. With the new routing in place, users shouldn’t experience any unexpectedly slow pushes to AWS ECR.
From Semaphore’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.semaphore.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Semaphore, started 2021-03-03 10:56 UTC, resolved after 51 d, 1 update(s).
- Title
- Sporadic slow Docker push towards AWS ECR
- Vendor
- Semaphore
- Date
- URL
- https://rewindex.com/company/semaphore/incidents/yv4f7bc8ts5l
Semaphore profileRecent Semaphore incidentsAll outages on March 3, 2021Semaphore in March 2021MarkdownJSON