1 Answer
- Newest
- Most votes
- Most comments
0
We'll need to figure out first whether this issue is specific to your user's source and destination or something else. Can you please have them open http://ec2-reachability.amazonaws.com/ and report any red flag they see in there?
Also do you have some other exposed services in the same region your user could try?
answered 2 years ago
Relevant content
- Accepted Answerasked 9 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 2 years ago
- I host a website on an EC2 instance. How do I allow my users to connect on HTTP (80) or HTTPS (443)?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
We also have a non-production EC2 instance in the Indonesia region. My user cannot connect to that system, either.
Running the EC2 reachability test: my user reports that he cannot reach Singapore or Jakarta regions.
In case I didn’t mention it, my user has tried multiple browsers on a Macintosh, on Windows, and on a smartphone. All have failed.
Additional information: user in Milan reports additional info that points to the inability to connect specifically to his ISP, which happens to be the largest ISP providing services to a substantial portion of Italy. The problem seems specific to Telecom Italia (TIM) which provides both his wired connection and his wireless phone services in Milan. His wife has phone service from Vodaphone in Milan and had no problems connecting to our server.
My user sent me a screen shot of a traceroute from his system to our system public IP 54.169.6X.XX. After internal Telecom Italia RFC1989 private IP space, traffic emerges on public IP space and from there on to AWS public address space. The public address trail is this: 195.22.205.116 (TIM) 195.22.196.170 (TIM) 195.22.205.116 (OK, this is odd, going back to the same router)
52.93.11.191 (AWS address space from here down) 15.230.29.139 52.93.11.109 52.93.11.89 52.93.10.227
(and it's all * all the way down from here)