Network issues to certain servers (German servers)
I saw another post recently about issues with connecting to Germany. My average ping to Germany based servers was always 120-130 which is perfectly fine for me. (I need to connect to a specific AWS (amazon server) based in EU, Germany for work). I tried everything on my end, multiple PC's, refresh signals, restarting modem (ARRIS SB6190), and restarting router. I tried hardwiring directly to my modem to ensure it wasnt my router and recieved the same issue. Finally, I tried one last thing. I ran the same tests but with a VPN. The moment I used the VPN, everything was fixed and there were no more packets being lost along with normalized ping below 130ms. This has been happening on and off for weeks now. Any helpful suggestions or fixes? I really would hate having to switch ISP as this is desperately needed. If you need any other information, I will check this post ASAP with any info needed.
https://i.imgur.com/cb0MFW2.png (list of IP's with issues)
https://i.imgur.com/uGr7iEF.png(CMD pinging IPs)
https://i.imgur.com/PODukw2.png (Ping of all AWS servers to show German servers are impossible to connect to, compared to other servers.)
Tracing route to ec2-3-120-0-0.eu-central-1.compute.amazonaws.com [18.104.22.168]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 11 ms 9 ms 22.214.171.124
3 11 ms 18 ms 9 ms 126.96.36.199
4 10 ms 10 ms 8 ms 188.8.131.52
5 11 ms 10 ms 9 ms 184.108.40.206
6 11 ms 11 ms 10 ms lag-8.ear1.Miami1.Level3.net [220.127.116.11]
7 * * * Request timed out.
8 122 ms 121 ms 121 ms 18.104.22.168
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 177 ms 161 ms 162 ms 22.214.171.124
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 171 ms 154 ms 159 ms ec2-3-120-0-0.eu-central-1.compute.amazonaws.com [126.96.36.199]
That's just one tracert example, usually they are MUCH worse and its for every IP listed in the image links I posted, sometimes reaching 170, 200, 500+ pings. During each of these times when it acts up most, nothing else is wrong with the connection everywhere else. And its only with comcast that this is happening.
As I stated earlier, using any VPN always fixes the issue, meaning the issue is NOT on Amazon Server's end. Its an issue with comcast. I hope this is urgently fixed, as this is an urgent matter.
(I saw another customer post similar issues as me https://forums.xfinity.com/t5/Your-Home-Network/Accessing-some-sites-in-Germany-is-slow/td-p/3287229 whether its related or not, it clearly is an issue affecting work. If there's an employee who can look into this that would be great, as the call reps keep insisting refresh signals and such, even with all my independant testing/results/proofs.)
Edit: A 3rd party network technician told me only a higher up would be able to fix this. Since the issue is fixed via VPN, its a specific routing issue or an internal issue with ISP itself. In other words, nothing from my end will fix it and only comcast can fix this.
Also here is a picture of realtime chart to show what happens on hops PLEASE view this specifically as well. https://i.imgur.com/HESGDIo.png