- Newest
- Most votes
- Most comments
Perhaps this was a time boxed issue. I can reach 3.16.93.245 on port 443 from in us-east-2 and externally via the internet.
We tested the connectivity using mtr, and it has about 67% of loss after entering the AWS network, it starts from 108.166.248.72 further.
answered a year ago
These issues are often due to cross-region network latency, temporary congestion, or AWS infrastructure problems, rather than local configuration errors. Transfers between distant regions can be affected by network conditions and may result in timeouts or slow performance. I recommend checking the AWS Service Health Dashboard for ongoing incidents and monitoring network performance in the affected region for any network issues.
You're experiencing network connectivity issues between Central Europe and the AWS us-east-2 region, which could be caused by several factors:
-
Routing or BGP Issues: There might be Border Gateway Protocol (BGP) routing problems between your ISP in Central Europe and AWS. This can cause traffic to be incorrectly routed or dropped for certain paths.
-
Network Latency: Geographic distance between Central Europe and us-east-2 (Ohio) naturally introduces latency. This latency can be exacerbated by temporary network congestion or routing changes.
-
ISP-specific Problems: Your specific Internet Service Provider might be experiencing issues with their connectivity to AWS regions.
-
Packet Loss: Network issues along the route could be causing packet loss, which would require retransmission and slow down your connections.
To troubleshoot this issue:
-
Run traceroute or MTR tests to identify where the connection is failing or experiencing high latency.
-
Test connectivity from different networks or locations to determine if the issue is specific to your network.
-
Check if using a different DNS server helps (like Google's 8.8.8.8 or Cloudflare's 1.1.1.1).
-
Consider temporarily using a different AWS region that might have better connectivity from your location.
-
If possible, test with a different ISP to see if the issue persists.
If the problem continues, it would be worth contacting AWS Support as they can investigate potential networking issues between their infrastructure and your region. They might be able to identify if there are any known routing or peering issues affecting connectivity between Central Europe and us-east-2.
Sources
Higher network latency since 1st of May | AWS re:Post
Troubleshooting network connection issues - AWS Data Transfer Terminal
Very strange connectivity issues with my EC2 | AWS re:Post
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
Apparently, exactly this was the issue. The sad thing is that you cannot report it to the technical support, so they can reroute the traffic over some more stable links. And it looks like AWS monitoring methods are slow, or non-existent. So the only thing left is to wait for the things to resolve itself. Appalling for the service provider of this magnitude.