cancel
Showing results for 
Search instead for 
Did you mean: 

bad pings

Community Veteran
Posts: 3,181
Thanks: 19
Fixes: 2
Registered: 31-07-2007

bad pings

Cant help if you dont help your self, do some ping traces to those servers.

Use DOS or any of the timetrial/freeware utilities.

From startbar: Run type cmd.exe
In the window that opens type: tracert server IP - this can be misleading so better to use one of the 2 utilities below

www.analogx.com/contents/download/network/htrace.htm freeware
http://www.visualware.com/visualroute/index.html lot more powerful but is 15 day trailware

So see if any Hops ping badly and or give packetloss.

Then we can see if its PN to blame or another provider.
Unvalued customer since 2001 funding cheap internet for others / DSL/Fibre house move 24 month regrade from 8th May 2017
8 REPLIES
N/A

bad pings

been getting really bad pings today between 80-100 all day.....usually i get about 35...my download speed is still fine...but pings are crap...........hope this aint the sign of things to come...just coz you have started new services(like make the cheaper ones crap forcing them to ugrade) or i am off......80-100 ping aint acceptable even on a cheap service and please dont tell me its the servers...they have been fine for the past 3 months
Community Veteran
Posts: 3,181
Thanks: 19
Fixes: 2
Registered: 31-07-2007

bad pings

1.pings to where
2. have you done any traces
3. if game servers are they at fault/busy
Unvalued customer since 2001 funding cheap internet for others / DSL/Fibre house move 24 month regrade from 8th May 2017
N/A

bad pings

ping pong.
does depend on general speed of the net.
N/A

bad pings

same again today pings dont start getting good untill about 10pm...i'll give it a week if no change nildram here i come and the servers are fine al my m8s on bt get great pings........its was great up untill they started the 1 and 2 meg services.....
N/A

bad pings

1,----,Timeout,n/a,----
2, 212.159.1.3,15ms,pth-se2.telehouse.core.plus.net,0%
3, 195.166.129.22,13ms,pth-gw0.telehouse.core.plus.net,0%
4, 195.66.226.12,16ms,linx-2.router.demon.net,0%
5, 195.173.72.54,14ms,tele-border-4-233.router.demon.net,0%
6, 194.159.176.113,15ms,tele-core-11-1-0-238.router.demon.net,0%
7, 194.217.238.254,45ms,ams3-border-1-at-1-2-3-102.router.demon.net,0%
8, 213.222.31.204,47ms,ams3-core-1-ge-0-0-0-0.router.nl.demon.net,0%
9, 213.222.31.222,47ms,ams1-access-1-at-1-2-1-0.router.nl.demon.net,0%
10, 195.11.247.144,55ms,games.router.nl.demon.net,0%
11, 195.11.243.42,60ms,power3.spellen.nl.demon.net,0%


1,----,Timeout,n/a,----
2, 212.159.1.3,18ms,pth-se2.telehouse.core.plus.net,0%
3, 195.166.129.22,14ms,pth-gw0.telehouse.core.plus.net,0%
4, 195.66.226.12,16ms,linx-2.router.demon.net,0%
5, 195.173.72.54,14ms,tele-border-4-233.router.demon.net,0%
6, 194.159.176.113,19ms,tele-core-11-1-0-238.router.demon.net,0%
7, 194.217.238.254,69ms,ams3-border-1-at-1-2-3-102.router.demon.net,0%
8, 213.222.31.204,58ms,ams3-core-1-ge-0-0-0-0.router.nl.demon.net,0%
9, 213.222.31.222,59ms,ams1-access-1-at-1-2-1-0.router.nl.demon.net,0%
10, 195.11.247.144,63ms,games.router.nl.demon.net,0%
11, 195.11.243.42,59ms,power3.spellen.nl.demon.net,0%


1,----,Timeout,n/a,----
2, 212.159.1.3,14ms,pth-se2.telehouse.core.plus.net,0%
3, 195.166.129.22,13ms,pth-gw0.telehouse.core.plus.net,0%
4, 195.66.226.12,14ms,linx-2.router.demon.net,0%
5, 195.173.72.54,15ms,tele-border-4-233.router.demon.net,0%
6, 194.159.176.113,17ms,tele-core-11-1-0-238.router.demon.net,0%
7, 194.217.238.254,61ms,ams3-border-1-at-1-2-3-102.router.demon.net,0%
8, 213.222.31.204,57ms,ams3-core-1-ge-0-0-0-0.router.nl.demon.net,0%
9, 213.222.31.222,58ms,ams1-access-1-at-1-2-1-0.router.nl.demon.net,0%
10, 195.11.247.144,58ms,games.router.nl.demon.net,0%
11, 195.11.243.42,55ms,power3.spellen.nl.demon.net,0%

3 diif port numbers...servers have been fine up untill this weekend i usually get about 35 ping...no-one else on the servers are having any probs just me......after about 10pm my ping drop to 35 again
Community Veteran
Posts: 3,181
Thanks: 19
Fixes: 2
Registered: 31-07-2007

bad pings

Well looks like its demon at fault, what your trace didnt show is packetloss as well.

namely this linx-2.router.demon.net hop is the start of the packetloss, which will get worse as it gets busy.

So mail demon about it hostmaster@DEMON.NET

Unvalued customer since 2001 funding cheap internet for others / DSL/Fibre house move 24 month regrade from 8th May 2017
N/A

bad pings

i dont really understand all that but all i know is other isps aint having this prob so if demon was at fault wouldn't other isps be affected aswell
N/A

bad pings

Not allways true.

The path your data travels accross the internet is called a router.

The device designed to pass trh traffic between each node in the route, is a router.

In the case of +net, the traffic has to pass through the demon routers, to get to the destination.

With other ISP's, it may not have to pass through demon (though, it is a possibility).

In adition to this, some ISPs have routing agreements. These mean that some ISPs give higher priority to trafic some some places, to other places.

Here is a traceroute form a BTO connection
Quote

traceroute to power3.spellen.nl.demon.net (195.11.243.42), 30 hops max, 38 byte packets
1 192.168.254.254 (192.168.254.254) 0.277 ms 0.258 ms 0.250 ms
2 bthg404-hg2.miltonkeynes.broadband.bt.net (217.35.193.201) 28.247 ms 28.680 ms 27.324 ms
3 217.35.193.130 (217.35.193.130) 29.526 ms 29.726 ms 29.534 ms
4 217.35.193.238 (217.35.193.23Cool 31.510 ms 31.197 ms 31.016 ms
5 inh2cs01-604.imsnet2.btopenworld.com (62.7.251.193) 30.024 ms 30.438 ms 29.291 ms
6 213.120.62.197 (213.120.62.197) 31.007 ms 30.931 ms 30.028 ms
7 core1-pos6-0.bletchley.ukcore.bt.net (194.72.31.33) 30.269 ms 29.943 ms 31.033 ms
8 core1-pos15-0.ilford.ukcore.bt.net (194.74.16.137) 78.071 ms 134.912 ms 199.321 ms
9 194.74.65.250 (194.74.65.250) 33.200 ms 33.413 ms 32.502 ms
10 linx-1.router.demon.net (195.66.224.12) 33.718 ms 32.644 ms 35.203 ms
11 lon1-border-1-225.router.demon.net (195.173.72.17) 32.494 ms 32.681 ms 33.703 ms
12 lon1-core-11-235.router.demon.net (194.159.176.125) 32.491 ms 32.655 ms 35.202 ms
13 ams3-border-1-at-1-2-0-3-101.router.demon.net (194.217.238.250) 67.734 ms 78.233 ms 78.821 ms
14 ams3-core-1-ge-0-0-0-0.router.nl.demon.net (213.222.31.204) 74.878 ms 76.248 ms 78.578 ms
15 ams1-access-1-at-1-2-1-0.router.nl.demon.net (213.222.31.222) 42.842 ms 45.217 ms 43.347 ms
16 games.router.nl.demon.net (195.11.247.144) 43.326 ms 42.490 ms 41.369 ms
17 power3.spellen.nl.demon.net (195.11.243.42) 41.846 ms 41.524 ms 43.172 ms


As you can see, my traffic does not pass through linx-2.router.demon.net

See as this is where you see packet loss, this is why I don't see it.