AWS Edge Location EG CA Stopped Working

While AWS doesn't officially report an outage for the specific edge location you mentioned (EG CA), temporary disruptions or routing issues can occur that affect specific regions or edge locations. In this case, it sounds like there may have been a backbone link failure causing traffic to be redirected, resulting in increased latency from 4ms to 50ms.

The duration of such incidents can vary significantly depending on the root cause and complexity of the issue. Typically, AWS works to resolve these types of problems as quickly as possible, often within a few hours. However, without an official report from AWS, it's difficult to provide a precise timeline for resolution.

In situations like this, AWS may reroute traffic through alternative paths to maintain service, which can explain the redirection you're experiencing. This failover mechanism helps maintain connectivity, albeit with increased latency.

For the most up-to-date information on service status and estimated resolution times, it's best to check the AWS Service Health Dashboard or contact AWS Support directly. They can provide more specific information about the issue affecting your region and any ongoing efforts to resolve it.

In the meantime, if low latency is critical for your application, you might consider temporarily routing your traffic through an alternative edge location or region until the issue is resolved. However, keep in mind that this may require configuration changes on your end.

Remember that while AWS strives for high availability and low latency across its global network, occasional disruptions can occur due to various factors, including network issues, hardware failures, or maintenance activities.
Sources
AWS services down for 15 minutes? | AWS re:Post
AWS global accelerator suddenly got high ping | AWS re:Post