# Semaphore: Network congestion on route to AWS ECR us-east region

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-11-06 16:51 UTC · Resolved: 2025-11-07 07:15 UTC · Duration: 14 h
- Updates: 18 · Affected components: Semaphore
- [Vendor status page: https://stspg.io/h48jkddh3hy8](https://stspg.io/h48jkddh3hy8)
- [Company: Semaphore](https://rewindex.com/company/semaphore.md)

## Timeline of updates

- **investigating** 2025-11-06 16:51 UTC: Operations towards the AWS US-East region might present some slowness. We are currently investigating this issue.
- **investigating** 2025-11-06 17:22 UTC: We are continuing to investigate this issue.
- **investigating** 2025-11-06 17:50 UTC: We are continuing to investigate this issue.
- **investigating** 2025-11-06 18:33 UTC: Some operations in the AWS US-East region may be experiencing slow performance. Our team is still investigating.
- **investigating** 2025-11-06 19:05 UTC: We are continuing to investigate this issue.
- **investigating** 2025-11-06 19:58 UTC: We are continuing to investigate this issue.
- **investigating** 2025-11-06 20:49 UTC: We have observed slight improvements in the operations towards the AWS US-East region. We are continuing to work on this issue.
- **investigating** 2025-11-06 21:02 UTC: Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue. We are continuing to monitor the AWS US-East region slowness.
- **investigating** 2025-11-06 21:40 UTC: Our team is still monitoring the AWS US-East region slowness. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-06 22:31 UTC: Performance in AWS US-East region is showing gradual recovery. Our team continues to monitor the situation.  Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-06 23:02 UTC: We are continuing to monitor the AWS US-East region slowness. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-06 23:30 UTC: We are continuing to  follow up the AWS US-East region slowness issue. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-07 00:03 UTC: Our team is following up the slight recovery in AWS US-East region. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-07 00:36 UTC: Our team is still monitoring the AWS US-East region performance. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-07 01:07 UTC: Increased network congestion detected in the AWS US-East region. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-07 01:48 UTC: We are continuing to monitor the AWS US-East region slowness. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **investigating** 2025-11-07 02:29 UTC: We are continuing to monitor the AWS US-East network congestion. Connections to us-west, ap-northeast, and GCP are performing normally. If your workflows are affected, pushing/pulling data to and from these regions should help mitigate the issue.
- **resolved** 2025-11-07 07:15 UTC: We have observed connection times recover and stay healthy for the affected regions.


---
Canonical: https://rewindex.com/company/semaphore/incidents/dg4dmyg1ngpy · Markdown: https://rewindex.com/company/semaphore/incidents/dg4dmyg1ngpy.md · JSON: https://rewindex.com/api/v1/companies/semaphore/incidents/dg4dmyg1ngpy · Generated 2026-10-20T03:13:22.148Z