

Ping Issues 18Th Feb
#1
Posted 18 February 2015 - 12:54 PM
#2
Posted 18 February 2015 - 01:02 PM
192.99.109.129
Then post your results here. Remember that if you use pingplotter to create a picture, use paint or something to obscure the first 2 hops just in case there's personally identifiable information there

#3
Posted 18 February 2015 - 01:22 PM
traceroute to 192.99.109.129 (192.99.109.129), 30 hops max, 60 byte packets 1 * * * 2 hos-tr4.juniper2.rz13.hetzner.de 213.239.224.97 de 0.179 ms hos-tr3.juniper2.rz13.hetzner.de 213.239.224.65 de 0.248 ms 0.243 ms 3 core21.hetzner.de 213.239.245.81 de 0.244 ms 0.224 ms core22.hetzner.de 213.239.245.121 de 0.219 ms 4 core11.hetzner.de 213.239.245.221 de 2.789 ms core12.hetzner.de 213.239.245.214 de 2.764 ms core11.hetzner.de 213.239.245.221 de 2.789 ms 5 juniper4.rz2.hetzner.de 213.239.245.26 de 2.785 ms 2.790 ms juniper4.rz2.hetzner.de 213.239.203.138 de 2.820 ms 6 r1nue2.core.init7.net 82.197.163.29 ch 2.908 ms 2.877 ms r1nue1.core.init7.net 77.109.135.101 ch 14.038 ms 7 r1ams1.core.init7.net 77.109.140.25 ch 25.673 ms 25.754 ms 25.858 ms 8 * * * 9 rbx-g1-a9.fr.eu 94.23.122.185 fr 22.613 ms 22.503 ms * 10 vac2-0-a9.fr.eu.vaccum 178.33.100.97 fr 9.083 ms vac1-0-a9.fr.eu.vaccum 178.33.100.149 fr 22.920 ms vac2-0-a9.fr.eu.vaccum 178.33.100.155 fr 11.380 ms 11 vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.493 ms 22.525 ms vac2-1-n7.fr.eu.firewall 178.33.100.98 fr 8.585 ms 12 vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.332 ms vac1-2-n7.fr.eu 91.121.215.9 fr 22.452 ms vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.332 ms 13 vac1-2-n7.fr.eu 91.121.215.9 fr 22.536 ms vac1-3-n7.fr.eu 91.121.215.13 fr 24.404 ms 24.879 ms 14 24.800 ms de 15 vac1-3-n7.fr.eu 91.121.215.13 fr 20.401 ms * * 16 * * * 17 * * * 18 * * * No reply for 3 hops. Assuming we reached firewall.
Seems like a lot of unnecessary jumping around France and Switzerland on the way to Canada. Not sure where I can go from there though...
Edited by William Mountbank, 18 February 2015 - 01:23 PM.
#4
Posted 18 February 2015 - 01:30 PM
William Mountbank, on 18 February 2015 - 01:22 PM, said:
traceroute to 192.99.109.129 (192.99.109.129), 30 hops max, 60 byte packets 1 * * * 2 hos-tr4.juniper2.rz13.hetzner.de 213.239.224.97 de 0.179 ms hos-tr3.juniper2.rz13.hetzner.de 213.239.224.65 de 0.248 ms 0.243 ms 3 core21.hetzner.de 213.239.245.81 de 0.244 ms 0.224 ms core22.hetzner.de 213.239.245.121 de 0.219 ms 4 core11.hetzner.de 213.239.245.221 de 2.789 ms core12.hetzner.de 213.239.245.214 de 2.764 ms core11.hetzner.de 213.239.245.221 de 2.789 ms 5 juniper4.rz2.hetzner.de 213.239.245.26 de 2.785 ms 2.790 ms juniper4.rz2.hetzner.de 213.239.203.138 de 2.820 ms 6 r1nue2.core.init7.net 82.197.163.29 ch 2.908 ms 2.877 ms r1nue1.core.init7.net 77.109.135.101 ch 14.038 ms 7 r1ams1.core.init7.net 77.109.140.25 ch 25.673 ms 25.754 ms 25.858 ms 8 * * * 9 rbx-g1-a9.fr.eu 94.23.122.185 fr 22.613 ms 22.503 ms * 10 vac2-0-a9.fr.eu.vaccum 178.33.100.97 fr 9.083 ms vac1-0-a9.fr.eu.vaccum 178.33.100.149 fr 22.920 ms vac2-0-a9.fr.eu.vaccum 178.33.100.155 fr 11.380 ms 11 vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.493 ms 22.525 ms vac2-1-n7.fr.eu.firewall 178.33.100.98 fr 8.585 ms 12 vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.332 ms vac1-2-n7.fr.eu 91.121.215.9 fr 22.452 ms vac1-1-n7.fr.eu.firewall 178.33.100.152 fr 22.332 ms 13 vac1-2-n7.fr.eu 91.121.215.9 fr 22.536 ms vac1-3-n7.fr.eu 91.121.215.13 fr 24.404 ms 24.879 ms 14 24.800 ms de 15 vac1-3-n7.fr.eu 91.121.215.13 fr 20.401 ms * * 16 * * * 17 * * * 18 * * * No reply for 3 hops. Assuming we reached firewall.
Seems like a lot of unnecessary jumping around France and Switzerland on the way to Canada. Not sure where I can go from there though...
Have you called your ISP? There might be some sort of an outage they're trying to route around.
Fierostetz, on 18 February 2015 - 01:28 PM, said:
Have you called your ISP? There might be some sort of an outage they're trying to route around.
You can always give pingzapper a try, at the top of the general forum there's a thread for time warner users, I've got a how-to for setting up pingzapper in there. You can use it an hour at a time for free - it disconnects and you can just reconnect - if there's some sort of temporary situation that could get you through the tough times. It would probably lower your ping overall even without network issues

Give that a shot and post back! I also recommend contacting your ISP still just in case.
#5
Posted 18 February 2015 - 01:32 PM
Fierostetz, on 18 February 2015 - 01:28 PM, said:
Have you called your ISP? There might be some sort of an outage they're trying to route around.
No, it's too late for the service times here, so their lines are closed. But thanks very much for the help anyway! I'll have to check tomorrow and see what it's like, but I think you might be right that it's some kind of problem with my ISP.
#6
Posted 18 February 2015 - 04:45 PM
William Mountbank, on 18 February 2015 - 01:32 PM, said:
No, it's too late for the service times here, so their lines are closed. But thanks very much for the help anyway! I'll have to check tomorrow and see what it's like, but I think you might be right that it's some kind of problem with my ISP.
If you try pingzapper, you can chose entry points that might allow you to route around trouble spots. It's been really popular in the other thread. Either way, have a good night! If you get more information, post back here - I'll subscribe so I remember to check in.
Mods - can you move this to the support forum?
#7
Posted 20 February 2015 - 02:29 PM
Fierostetz, on 18 February 2015 - 04:45 PM, said:
If you try pingzapper, you can chose entry points that might allow you to route around trouble spots. It's been really popular in the other thread. Either way, have a good night! If you get more information, post back here - I'll subscribe so I remember to check in.
Mods - can you move this to the support forum?
Update: I finally got a chance to test, and it seems like this was just an ISP thing, as my ping is now normal. Interesting that I've never had this since the old 15K baud days of dialup.
Anyway, thanks for your kind help and prompting Fierostetz, although I still have to try pingzapper!
#8
Posted 22 February 2015 - 06:21 PM
William Mountbank, on 20 February 2015 - 02:29 PM, said:
Update: I finally got a chance to test, and it seems like this was just an ISP thing, as my ping is now normal. Interesting that I've never had this since the old 15K baud days of dialup.
Anyway, thanks for your kind help and prompting Fierostetz, although I still have to try pingzapper!
no problem -glhf!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users