routing to NL - ping times up and down?

[equk]

I'm not sure what's going on but the ping times to the NL seem very up and down atm.

Pinging servers at 120ms where on my old ISP I was getting 30ms.

Code Select Expand

traceroute to 194.109.69.90 (194.109.69.90), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  0.714 ms  0.697 ms  0.656 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  20.181 ms  21.531 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  19.377 ms  17.468 ms  19.989 ms
4  telehouse-gw.idnet.net (212.69.40.1)  19.917 ms  27.597 ms  17.909 ms
5  * lonap.he.net (193.203.5.128)  23.601 ms  23.442 ms
6  pos2-0.gsr12416.ams.he.net (216.66.24.158)  128.051 ms  131.960 ms  245.071 ms
7  154.41.66.216.in-addr.arpa (216.66.41.154)  127.982 ms  119.358 ms  119.890 ms
8  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  114.000 ms  115.452 ms  253.803 ms
9  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  121.998 ms  157.424 ms  113.886 ms
10  quake3-01.xs4all.nl (194.109.69.90)  118.213 ms  120.384 ms  117.646 ms


another NL IP pinging at 30ms?

Code Select Expand

traceroute to 85.12.35.148 (85.12.35.148), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  0.763 ms  0.682 ms  0.651 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  19.201 ms  19.935 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  18.395 ms  20.277 ms  19.970 ms
4  telehouse-gw.idnet.net (212.69.40.1)  20.036 ms  18.179 ms  19.937 ms
5  * redbus-gw-fa0-0-1003.idnet.net (212.69.63.1)  20.684 ms  20.217 ms
6  nikhef.openpeering.nl (195.69.144.189)  32.087 ms  46.859 ms  41.898 ms
7  openpeering.easy-ams.as34305.net (82.150.153.226)  34.097 ms  46.941 ms  55.938 ms
8  ge-3-1.edge-1.easy-ams.as34305.net (85.12.0.25)  44.299 ms  32.803 ms  37.800 ms
9  * hermes.truegaming.nl (85.12.35.148)  30.271 ms  30.638 ms

totally different routing? not sure what's going on, yesterday the pings to the top one were 50ms unstable. Very strange 

[maxping]

Read this thread mate it will explain all - http://www.idnetters.idnet.co.uk/forums/index.php?topic=450.0

[equk]

cool

the ping increase seems to be at he.net tho, not idnet. Not sure why the 2 NL IPs are routed slightly different

I'll wait and see if the ping goes back down and re-do a traceroute, it's almost as if the routing is changing dynamicly, some days it's good and others it's bad 

[equk]

hmm back down to 50ms now 

Code Select Expand

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  0.691 ms  0.691 ms  0.657 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  19.492 ms  19.509 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  19.665 ms  19.479 ms  20.045 ms
4  telehouse-gw.idnet.net (212.69.40.1)  21.892 ms  19.624 ms  20.266 ms
5  * lonap.he.net (193.203.5.128)  62.121 ms  65.820 ms
6  pos2-0.gsr12416.ams.he.net (216.66.24.158)  71.582 ms  65.724 ms  42.232 ms
7  154.41.66.216.in-addr.arpa (216.66.41.154)  29.721 ms  31.569 ms  30.019 ms
8  * 0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  50.569 ms  51.450 ms
9  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  53.984 ms  53.627 ms  49.868 ms
10  quake3-04.xs4all.nl (194.109.69.93)  50.294 ms  51.270 ms  48.182 ms

strange! 

still high in comparison to 30 also totally unstable  going from 50 to 80, netgraph looks like grass lol

[equk]

now suddenly the ping is 30ms and it's stable as I would expect 

Code Select Expand

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.264 ms  0.742 ms  0.651 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  20.825 ms  20.248 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.242 ms  18.683 ms  19.875 ms
4  telehouse-gw.idnet.net (212.69.40.1)  22.318 ms  20.573 ms  22.198 ms
5  * lonap.he.net (193.203.5.128)  101.393 ms  20.712 ms
6  pos2-0.gsr12416.ams.he.net (216.66.24.158)  28.025 ms  38.196 ms  29.385 ms
7  154.41.66.216.in-addr.arpa (216.66.41.154)  30.413 ms  30.560 ms *
8  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  29.993 ms  30.323 ms  36.020 ms
9  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  35.996 ms  28.901 ms  31.959 ms
10  quake3-04.xs4all.nl (194.109.69.93)  29.919 ms *  29.880 ms

[equk]

lol gone up to 80ms now

Code Select Expand

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.254 ms  0.754 ms  0.697 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  22.866 ms  22.654 ms  23.966 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  29.871 ms  23.959 ms
4  telehouse-gw.idnet.net (212.69.40.1)  24.141 ms  20.489 ms  19.951 ms
5  lonap.he.net (193.203.5.128)  22.074 ms  20.311 ms *
6  pos2-0.gsr12416.ams.he.net (216.66.24.158)  89.763 ms  88.077 ms  87.877 ms
7  154.41.66.216.in-addr.arpa (216.66.41.154)  90.276 ms  84.419 ms  81.917 ms
8  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  84.327 ms  88.457 ms  83.913 ms
9  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  86.036 ms  76.248 ms  79.904 ms
10  quake3-04.xs4all.nl (194.109.69.93)  80.376 ms  82.240 ms  81.985 ms

[maxping]

Mate we have a stickied ping problem thread already running here -

http://www.idnetters.idnet.co.uk/forums/index.php?topic=450.0

[Scott]

[MOD] Locked as OP has been pointed to more appropriate, stickied post on the subject[/MOD]