Semaphore: Network congestion on route to AWS ECR us-east region
Affected components: Semaphore
Timeline of updates
- investigating
Operations towards the AWS US-East region might present some slowness. We are currently investigating this issue.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- investigating
Some operations in the AWS US-East region may be experiencing slow performance. Our team is still investigating.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- investigating
We have observed slight improvements in the operations towards the AWS US-East region. We are continuing to work on this issue.
- investigating
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
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
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
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
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
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
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
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
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
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
We have observed connection times recover and stay healthy for the affected regions.
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
02a21c30fc17c4a0…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).