cancel
Showing results for 
Search instead for 
Did you mean: 

routing problems over level3

alexfiennes
Newbie
Posts: 2
Registered: 21-08-2013

routing problems over level3

I'm getting connectivity problems to www.concrete5.org and running a traceroute to the server shows lots of weirdness going on once we get into level3:
[tt]
traceroute to concrete5.org (50.28.56.20), 64 hops max, 52 byte packets
1  192.168.2.1 (192.168.2.1)  1.476 ms  1.113 ms  1.046 ms
2  lo0-central10.pcl-ag04.plus.net (195.166.128.185)  48.198 ms  67.074 ms  76.158 ms
3  link-b-central10.pcl-gw02.plus.net (212.159.2.174)  43.477 ms  41.596 ms  41.493 ms
4  206.core.access.plus.net (212.159.0.206)  43.583 ms  41.161 ms  41.067 ms
5  ae2.pcl-cr01.plus.net (195.166.129.6)  42.163 ms  41.645 ms  42.131 ms
6  ae1.ptw-cr01.plus.net (195.166.129.0)  43.684 ms  41.531 ms  41.832 ms
7  217.163.45.181 (217.163.45.181)  42.252 ms
    te-4-2.car5.london1.level3.net (217.163.45.249)  43.114 ms
    217.163.45.181 (217.163.45.181)  41.331 ms
8  ae-52-52.csw2.london1.level3.net (4.69.139.120)  135.804 ms  131.442 ms  131.492 ms
9  ae-57-222.ebr2.london1.level3.net (4.69.153.133)  131.372 ms  130.716 ms
    ae-58-223.ebr2.london1.level3.net (4.69.153.137)  130.877 ms
10  ae-42-42.ebr1.newyork1.level3.net (4.69.137.70)  146.644 ms
    ae-44-44.ebr1.newyork1.level3.net (4.69.137.7Cool  132.425 ms  130.319 ms
11  ae-4-4.ebr1.newyork2.level3.net (4.69.141.1Cool  130.845 ms
    4.69.201.46 (4.69.201.46)  131.199 ms
    4.69.201.42 (4.69.201.42)  131.177 ms
12  ae-1-100.ebr2.newyork2.level3.net (4.69.135.254)  131.229 ms  131.232 ms  131.544 ms
13  ae-2-2.ebr1.chicago1.level3.net (4.69.132.65)  131.628 ms  131.595 ms  136.898 ms
14  ae-6-6.ebr1.chicago2.level3.net (4.69.140.190)  133.023 ms  131.262 ms  131.784 ms
15  ae-104-3504.edge2.chicago2.level3.net (4.69.158.13)  132.003 ms
    ae-102-3502.edge2.chicago2.level3.net (4.69.158.5)  130.241 ms
    ae-104-3504.edge2.chicago2.level3.net (4.69.158.13)  132.081 ms
16  cwie-llc.edge2.chicago2.level3.net (4.59.29.82)  132.105 ms  288.338 ms  172.939 ms
17  lw-core4-te91.rtr.liquidweb.com (209.59.157.206)  140.021 ms  140.496 ms  141.783 ms
18  lw-dc3-dist15.rtr.liquidweb.com (69.167.128.201)  139.983 ms  139.750 ms  139.944 ms
[/tt]
and no packets are actually getting there or back from www. concrete5.org
I had the same problem last night, but it cleared up this morning.
I haven't found any other machines with this problem and I can connect to other parts of the net fine, and my speedtest is giving me 3.5Mb/s which is great, and I've tried rebooting the router etc etc.
I can route easily from my server (not via level 3) and access the site so I think that it is purely a routing problem.  Would anyone be seeing the same thing or have any suggestions?
6 REPLIES
Community Veteran
Posts: 5,111
Thanks: 465
Fixes: 17
Registered: 10-06-2010

Re: routing problems over level3

What you described as routing weirdness could be nothing more than there being multiple different routes, unfortunately the routes might have slightly different numbers of hops, and mix together rather awkwardly when traceroute tries to display them all. The site loaded fine for me.
[tt]# traceroute -q 5 -N 1 -T -p 80 www.concrete5.org
traceroute to www.concrete5.org (50.28.56.20), 30 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  2.079 ms  1.841 ms  1.818 ms  1.792 ms  1.790 ms
2  lo0-central10.ptn-ag04.plus.net (195.166.128.193)  24.891 ms  24.107 ms  24.523 ms  24.807 ms  24.827 ms
3  link-b-central10.ptn-gw02.plus.net (212.159.2.142)  23.841 ms  24.267 ms  25.249 ms  25.278 ms  24.473 ms
4  xe-10-1-0.ptw-cr02.plus.net (212.159.1.46)  24.792 ms  25.694 ms  26.080 ms  25.755 ms  29.665 ms
5  ae2.ptw-cr01.plus.net (195.166.129.4)  23.824 ms  24.468 ms  24.480 ms ae1.pcl-cr02.plus.net (195.166.129.3)  24.849 ms ae2.ptw-cr01.plus.net (195.166.129.4)  25.006 ms
6  te-4-2.car5.London1.Level3.net (217.163.45.249)  24.332 ms 217.163.45.181 (217.163.45.181)  25.389 ms ae2.pcl-cr01.plus.net (195.166.129.6)  24.556 ms  24.679 ms  25.879 ms
7  ae-52-52.csw2.London1.Level3.net (4.69.139.120)  114.127 ms xe-11-2-0.edge3.London2.Level3.net (212.187.201.213)  24.297 ms xe-11-1-0.edge3.London2.Level3.net (212.187.201.209)  24.404 ms xe-11-2-0.edge3.London2.Level3.net (212.187.201.213)  25.487 ms ae-52-52.csw2.London1.Level3.net (4.69.139.120)  114.695 ms
...
[/tt]
Hop 5 in the above is 1 of 2 Plusnet addresses, hop 6 has some Level3 IPs but also a Plusnet IP.
alexfiennes
Newbie
Posts: 2
Registered: 21-08-2013

Re: routing problems over level3

I'm still getting timeouts on all pings.
However about 30m ago traffic did start flowing with a ping time of about 140ms.  However, by the time that I had reloaded this thread to see if the traceroute had changed it had stopped working again and is still not working.
Community Veteran
Posts: 38,460
Thanks: 1,027
Fixes: 62
Registered: 15-06-2007

Re: routing problems over level3

It does look as though Level3 is playing up
Tracing route to concrete5.org [50.28.56.20]
over a maximum of 30 hops:
 1    82 ms    99 ms    99 ms  192.168.1.254
 2    33 ms    46 ms    32 ms  lo0-central10.pcl-ag02.plus.net [195.166.128.183]
 3    32 ms    34 ms    32 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.164]
 4    32 ms    34 ms    32 ms  196.core.access.plus.net [212.159.0.196]
 5    33 ms    32 ms    31 ms  xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
 6     *       32 ms    33 ms  ae-0-11.edge4.London2.Level3.net [4.69.200.126]
 7   122 ms   121 ms   122 ms  ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
 8   122 ms   121 ms   133 ms  vlan103.ebr2.London1.Level3.net [4.69.143.94]
 9   122 ms   122 ms   121 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
10   121 ms   121 ms   121 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
11   124 ms   121 ms   122 ms  ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]
12   122 ms   121 ms   122 ms  ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
13   122 ms   122 ms   122 ms  ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
14   122 ms   121 ms   121 ms  ae-102-3502.edge2.Chicago2.Level3.net [4.69.158.5]
15   274 ms   236 ms   208 ms  CWIE-LLC.edge2.Chicago2.Level3.net [4.59.29.82]
16   131 ms   130 ms   130 ms  lw-core4-te91.rtr.liquidweb.com [209.59.157.206]
17   131 ms   131 ms   130 ms  lw-dc3-dist15.rtr.liquidweb.com [69.167.128.201]
18   129 ms   128 ms   129 ms  community.concrete5.org [50.28.56.20]
Trace complete.
Pyrii
Grafter
Posts: 79
Registered: 06-06-2013

Re: routing problems over level3

It's strange that there's about 90ms added to the latency while still within London.
Community Veteran
Posts: 5,111
Thanks: 465
Fixes: 17
Registered: 10-06-2010

Re: routing problems over level3

And stranger that there's zero latency added while crossing the Atlantic to New York! Or perhaps there's just something odd about where the latency shows up on the traceroute.
Pyrii
Grafter
Posts: 79
Registered: 06-06-2013

Re: routing problems over level3

I can only assume they have server in new york specifically for receiving traffic from london.
Though a router in chicago has double the ping, but not the ones after, it's all very strange.