|
Ticket ID: SIXXS #606517 Ticket Status: User PoP: nlede01 - BIT BV (Ede)
minor routing problem
![[be]](/s/countries/be.gif) Shadow Hawkins on Monday, 12 November 2007 13:46:37
I am experiencing quite high ipv4 pings (90ms vs 10 ms) to nlede01 without an obvious reason from one host while another one works nicely. If I should contact my ISP instead, please let me know.
/usr/sbin/traceroute nlede01.sixxs.net
traceroute to nlede01.sixxs.net (193.109.122.244), 30 hops max, 38 byte packets
1 ar0.kangaroot.net (62.213.204.202) 1.402 ms 0.481 ms 0.477 ms
2 br1-ar0.bru1.kangaroot.net (62.213.203.81) 0.236 ms 0.212 ms 0.216 ms
3 ae0-69.bru20.ip.tiscali.net (213.200.69.121) 0.404 ms 0.438 ms 0.434 ms
4 so-0-1-0.ams11.ip.tiscali.net (213.200.81.106) 4.266 ms 5.164 ms 5.939 ms
5 rt-dc2-ias-csg01.nl.kpn.net (193.172.66.237) 6.462 ms 6.481 ms 6.554 ms
6 195.190.227.223 (195.190.227.223) 8.940 ms 6.556 ms 6.662 ms
7 asd-s4-rou-1001.NL.eurorings.net (134.222.230.222) 7.150 ms 7.101 ms 7.133 ms
8 kpn-1402.xe-0-0-0.jun1.galilei.network.bit.nl (134.222.97.186) 9.301 ms 8.580 ms 8.787 ms
9 jun1.kelvin.network.bit.nl (213.136.31.6) 90.533 ms 91.999 ms 90.285 ms
10 nlede01.sixxs.net (193.109.122.244) 93.564 ms 96.355 ms 90.420 ms
traceroute to nlede01.sixxs.net (193.109.122.244), 30 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 0.807 ms 0.538 ms 0.482 ms
2 88.197.131.254 (88.197.131.254) 6.228 ms 6.658 ms 6.524 ms
3 195.95.4.25 (195.95.4.25) 6.617 ms 6.640 ms 6.585 ms
4 194.119.228.161 (194.119.228.161) 9.738 ms 11.476 ms 7.359 ms
5 194.119.226.18 (194.119.226.18) 7.808 ms 7.882 ms 8.054 ms
6 zvtm-s1-rou-1042.BE.KPNQwest.net (134.222.101.237) 7.638 ms 8.002 ms 15.751 ms
7 zvtm-s1-rou-1041.BE.eurorings.net (134.222.231.253) 8.671 ms 11.403 ms 7.867 ms
8 asd2-rou-1021.NL.eurorings.net (134.222.231.185) 11.284 ms 11.737 ms 11.517 ms
9 asd-s4-rou-1001.NL.eurorings.net (134.222.230.206) 12.956 ms 12.938 ms 12.842 ms
10 kpn-1402.xe-0-0-0.jun1.galilei.network.bit.nl (134.222.97.186) 17.139 ms 15.590 ms 16.427 ms
11 jun1.kelvin.network.bit.nl (213.136.31.6) 16.445 ms 16.794 ms 15.949 ms
12 nlede01.sixxs.net (193.109.122.244) 16.488 ms 18.162 ms 19.960 ms
minor routing problem
Shadow Hawkins on Monday, 12 November 2007 13:53:07
The problem seems to have started on Thursday november 8th at 12u00. See the statistics of tunnel 5628.
minor routing problem
Ask your ISP to peer at AMS-IX again or at least to keep traffic in Europe instead of only allowing traffic to go over Cogent as a transit, which ships it from .nl to .uk to the us and then gblx in brussles.
minor routing problem
Shadow Hawkins on Wednesday, 21 November 2007 14:48:08
Hi,
I'm PL2100-RIPE from the ISP where adriaans tunnel terminates. We are using tiscali as one of our transits, a traceroute from our network to the pop gives:
traceroute to 193.109.122.244 (193.109.122.244), 30 hops max, 38 byte packets
1 62.213.203.189 (62.213.203.189) 0.734 ms 0.653 ms 0.646 ms
2 br1-ar0.bru1.kangaroot.net (62.213.203.81) 0.355 ms 0.301 ms 0.291 ms
3 ae0-69.bru20.ip.tiscali.net (213.200.69.121) 0.556 ms 0.717 ms 0.563 ms
4 so-0-1-0.ams11.ip.tiscali.net (213.200.81.106) 4.410 ms 5.144 ms 4.441 ms
5 rt-dc2-ias-csg01.nl.kpn.net (193.172.66.237) 6.590 ms 6.512 ms 6.759 ms
6 * * *
7 asd-s4-rou-1001.NL.eurorings.net (134.222.230.222) 12.382 ms 12.638 ms 12.534 ms
8 kpn-1402.xe-0-0-0.jun1.galilei.network.bit.nl (134.222.97.186) 8.170 ms 10.406 ms 8.626 ms
9 jun1.kelvin.network.bit.nl (213.136.31.6) 91.560 ms 90.455 ms 90.015 ms
10 nlede01.sixxs.net (193.109.122.244) 85.788 ms 85.698 ms 89.246 ms
As you can see, the high latency starts at hop 9, which is in the bit network. Am I correct to assume the problem lies in the bit network?
minor routing problem
Am I correct to assume the problem lies in the bit network?
No, as packets travel two ways.
From the nlede01 PoP to the first hop you provided (as you forgot to mention the source address you traced from:
traceroute to 62.213.203.189 (62.213.203.189), 30 hops max, 40 byte packets
1 sixxs-gw.network.bit.nl (193.109.122.241) 1.450 ms 1.396 ms 1.365 ms
2 1.xe-0-0-0.jun1.kelvin.network.bit.nl (213.136.31.2) 0.254 ms 1.344 ms 0.559 ms
3 149.6.128.57 (149.6.128.57) 12.282 ms 11.850 ms 11.403 ms
4 t2-4.ccr01.ams03.atlas.cogentco.com (130.117.3.105) 90.865 ms 92.077 ms 91.128 ms
5 t3-1.mpd02.lon01.atlas.cogentco.com (130.117.1.38) 84.372 ms 91.049 ms 86.078 ms
6 t4-3.mpd03.jfk02.atlas.cogentco.com (130.117.1.105) 78.174 ms 78.359 ms 78.017 ms
7 v3492.mpd01.jfk05.atlas.cogentco.com (154.54.7.14) 81.299 ms 81.678 ms 80.240 ms
8 gblx.jfk05.atlas.cogentco.com (154.54.11.138) 80.810 ms 79.251 ms 80.908 ms
9 Kangaroot-BVBA.gi2-0.403.ar1.BRU1.gblx.net (64.208.205.118) 83.899 ms 83.626 ms 83.607 ms
10 ar0-br0.bru1.kangaroot.net (62.213.203.74) 84.842 ms 85.104 ms 83.882 ms
See also distributed traceroute to get that information yourself.
Looks a lot like transit provider messups to me.
minor routing problem
Shadow Hawkins on Thursday, 22 November 2007 12:56:13
Uhm, I see no link here? Accidental reply on the wrong ticket?
minor routing problem
Shadow Hawkins on Friday, 14 December 2007 00:19:24
Seems to be a lot better now since about two weeks.
State change: user
The state of this ticket has been changed to user
|
![[ch]](/s/countries/ch.gif)
on Monday, 12 November 2007 17:16:46
Posting is only allowed when you are