This happening to anyone else?
Feel free to post the results here and I'll see if anything obvious stands out.
In my case, I think the 100% packet loss on the intermediate frontiernet.net routers are because Frontier decided that they do not need to expose ICMP to end users going across the core. They only care about the edge routers where they hand off to other carriers (in this case, hop 9 going to Equinix / AWS)
PS C:\Users\guy> pathping sindome.org
Tracing route to sindome.org [18.217.131.27]
over a maximum of 30 hops:
0 DESKTOP-3U548DS [192.168.1.4]
1 192.168.1.1
2 >> deleted <<
3 74.36.196.185
4 ae2---0.cor02.bvtn.or.frontiernet.net [74.40.1.181]
5 ae0---0.cor01.bvtn.or.frontiernet.net [74.40.1.185]
6 ae4---0.cor01.sttl.wa.frontiernet.net [74.40.1.221]
7 ae3---0.cor02.enwd.co.frontiernet.net [74.40.2.58]
8 ae9---0.cor02.chcg.il.frontiernet.net [74.40.5.153]
9 ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.142]
10 equinix01-chi2.amazon.com [206.223.119.98]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-3U548DS [192.168.1.4]
0/ 100 = 0%
Tracing route to sindome.org [18.217.131.27]
over a maximum of 30 hops:
0 DESKTOP-7FSQS2G [192.168.0.19]
1 192.168.0.1
2 ---
3 cr1-rhe-b-be152.bb.as11404.net [174.127.183.20]
4 cr1-rhe-a-be-1.as11404.net [192.175.29.158]
5 cr1-che-b-be-2.as11404.net [192.175.29.161]
6 cr1-9greatoaks-hu-0-6-0-20-0.bb.as11404.net [192.175.28.108]
7 cr2-11greatoaks-te-0-0-0-4.bb.as11404.net [208.76.184.1]
8 72.21.221.200
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-7FSQS2G [192.168.0.19]
0/ 100 = 0%
What do you think about waddle's traceroute?
To me, it doesn't look like whatever as11404.net is, is getting anywhere near AWS.
Though I do see that they have a peering point in Equinix Chicago, which is where my trace showed sindome being located. (https://www.peeringdb.com/asn/11404)
Waddle,
I would send that trace to your ISP's tech support team. Just tell them that you are getting intermittent disconnects into AWS. I'm not a legitimate network guy, but it looks like a route advertisement issue.
Are you on Wave Broadband? If not, it looks like your ISP is purchasing transit from them.
After taking a deeper look at it, I think the routing is fine.
https://db-ip.com/all/72.21.221
Hop 8 is Amazon.
There's probably a bit of intermittent connectivity problems at hop 6 or 7. Just open a ticket with your ISP. They shouldn't need to know more than you are connecting to sindome.org on tcp/5555 and experiencing intermittent disconnects.
