Kitz Forum
Internet => Web Browsing & Email => Topic started by: kitz on May 27, 2014, 09:12:15 PM
-
Can someone do me a favour please and post some tracerts to kitz.co.uk - especially if youre not on Plusnet.
I can normally reach my server in about 15ms, but for some reason I seem to be bouncing all round london, over to Paris, and back to the UK.. causing additional latency of up to 90ms.
As far as I can see the issue isnt with my server and its a routing issue at .gin.ntt (Global IP Networks)... so Im not sure if this is even ISP related nor how to get it fixed.
-----
Im trying to do some pretty heavy server upgrades today and trying transferring lots & lots of data, but after working on the server all day, its now really beginning to do my head in.. especially when I still have lots to do. I pay premium for UK hosting for a reason, and Im now at the point when Im seriously not amused. :'(
-
from a server hosted in the US:
[root@ks4004018 ~]# traceroute kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 142.4.212.252 (142.4.212.252) 2.093 ms * *
2 bhs-g1-6k.qc.ca (198.27.73.17) 2.914 ms 3.282 ms 3.280 ms
3 * * 198.27.73.204 (198.27.73.204) 10.453 ms
4 * * *
5 * * *
6 eqx1.routers.eqx.misp.co.uk (195.66.225.228) 83.618 ms 87.152 ms 87.465 ms
7 91.198.165.74 (91.198.165.74) 85.313 ms 85.279 ms 85.302 ms
8 bit-tech2.servers.rbl-mer.misp.co.uk (91.198.165.69) 86.149 ms 81.557 ms 81.545 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
another US server (different provider)
[root@ayk ~]# traceroute kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 216-158-74-1.static.webnx.com (216.158.74.1) 0.573 ms 0.559 ms 0.533 ms
2 100-42-223-57.static.webnx.com (100.42.223.57) 0.730 ms 0.948 ms 0.933 ms
3 100-42-223-145.static.webnx.com (100.42.223.145) 0.654 ms 0.656 ms 0.872 ms
4 ae3.er4.lax112.us.above.net (208.184.5.177) 0.375 ms 0.371 ms 0.360 ms
5 ae10.cr2.lax112.us.above.net (64.125.21.113) 3.260 ms 3.250 ms 0.548 ms
6 ae12.mpr1.lax12.us.above.net (64.125.21.174) 0.486 ms 0.350 ms 0.338 ms
7 ntt-zayo.lax12.us.above.net (64.125.12.158) 1.142 ms 1.137 ms 1.183 ms
8 ae-6.r21.lsanca03.us.bb.gin.ntt.net (129.250.5.69) 0.600 ms 0.808 ms 0.766 ms
9 ae-2.r20.asbnva02.us.bb.gin.ntt.net (129.250.3.54) 67.666 ms 67.800 ms 73.781 ms
10 ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5) 107.896 ms 93.117 ms 107.843 ms
11 * * ae-2.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.145) 147.867 ms
12 ae-2.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.159) 164.794 ms 158.929 ms 170.516 ms
13 ae-2.r03.londen01.uk.bb.gin.ntt.net (129.250.3.8) 179.059 ms 170.487 ms 164.739 ms
14 62.73.179.150 (62.73.179.150) 174.353 ms 167.923 ms 171.661 ms
15 91.198.165.76 (91.198.165.76) 170.067 ms 172.732 ms 163.201 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Plusnet:
C:\Users\loonylion>tracert kitz.co.uk
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms smoothwall [10.0.0.10]
2 24 ms 24 ms 23 ms lo0.10.central10.ptw-bng01.plus.net [195.166.128
.170]
3 24 ms 23 ms 24 ms irb.10.ptw-cr02.plus.net [84.93.249.2]
4 24 ms 24 ms 24 ms ae1.pcl-cr02.plus.net [195.166.129.3]
5 24 ms 24 ms 24 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 24 ms 23 ms 24 ms xe-11-1-0.edge3.London2.Level3.net [212.187.201.
209]
7 30 ms 32 ms 32 ms vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202
.177]
8 32 ms 31 ms 30 ms ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
9 33 ms 30 ms 31 ms ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
10 31 ms 31 ms 31 ms ae-1-60.edge4.Paris1.Level3.net [4.69.168.7]
11 33 ms * 41 ms NTT-level3-2x10G.Paris.Level3.net [4.68.63.118]
12 60 ms 58 ms 53 ms ae-4.r04.parsfr01.fr.bb.gin.ntt.net [129.250.4.1
17]
13 33 ms 34 ms 35 ms ae-3.r20.parsfr01.fr.bb.gin.ntt.net [129.250.6.1
76]
14 43 ms 44 ms 33 ms as-2.r23.londen03.uk.bb.gin.ntt.net [129.250.5.8
]
15 34 ms 38 ms 36 ms ae-2.r02.londen01.uk.bb.gin.ntt.net [129.250.3.1
]
16 51 ms 39 ms 52 ms ae-1.r03.londen01.uk.bb.gin.ntt.net [129.250.3.3
7]
17 54 ms 79 ms 67 ms 62.73.179.150
18 36 ms 34 ms 44 ms 62.73.179.150
19 53 ms 62 ms 54 ms 91.198.165.76
20 51 ms 47 ms 38 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Trace complete.
Looks like Level3 have a routing issue here.
-
I cant suss it out, someone else on pn coming off at pcl (london central) to Level3 is fine.
Im on ptn-ag02 and Im bouncing all round london, paris and back again :/
| 1 | | 192.168.1.1 | ZyXEL.Home | ... | | 0 | x | (private use) |
| 2 | | 195.166.128.191 | lo0-central10.ptn-ag02.plus.net | ?(United Kingdom) | * | 30 | -x-- | Core Loopback Addresses |
| 3 | | 212.159.2.134 | link-b-central10.ptn-gw02.plus.net | ?London, UK | * | 15 | x | Access LAN |
| 4 | | 212.159.0.114 | xe-1-2-0.ptw-cr02.plus.net | ?London, UK | * | 15 | x--- | Access LAN |
| 5 | | 195.166.129.4 | ae2.ptw-cr01.plus.net | ?(United Kingdom) | * | 16 | x | Core Loopback Addresses |
| 6 | | 195.166.129.1 | ae1.pcl-cr01.plus.net | ?(United Kingdom) | * | 15 | x | Core Loopback Addresses |
| 7 | | 212.187.201.213 | xe-11-2-0.edge3.London2.Level3.net | London, UK | * | 16 | x- | Level 3 serial links |
| 8 | | 4.69.202.177 | vl-3201-ve-128.ebr2.London2.Level3.net | London, UK | * | 22 | x | 4.69.202.0 |
| 9 | | 4.69.159.86 | ae-42-42.ebr1.Paris1.Level3.net | Paris, France | +01:00 | 22 | x | 4.69.159.0 |
| 10 | | 4.69.161.90 | ae-91-91.csw4.Paris1.Level3.net | Paris, France | +01:00 | 22 | x | 4.69.161.0 |
| 11 | | 4.69.168.199 | ae-4-90.edge4.Paris1.Level3.net | Paris, France | +01:00 | 22 | x | 4.69.168.0 |
| 12 | | 4.68.63.118 | NTT-level3-2x10G.Paris.Level3.net | Paris, France | +01:00 | 88 | --x-- | 4.68.63.0 |
| 13 | | 129.250.5.136 | ae-0.r20.parsfr01.fr.bb.gin.ntt.net | | | 86 | --x- | 129.250.5.0 |
| 14 | | 129.250.5.8 | as-2.r23.londen03.uk.bb.gin.ntt.net | | | 86 | --x- | 129.250.5.0 |
| 15 | | 129.250.5.41 | ae-2.r02.londen03.uk.bb.gin.ntt.net | | | 84 | -x- | 129.250.5.0 |
| 16 | | 129.250.3.1 | ae-2.r02.londen01.uk.bb.gin.ntt.net | | | 85 | -x- | 129.250.3.0 |
| 17 | | 129.250.3.37 | ae-1.r03.londen01.uk.bb.gin.ntt.net | | | 86 | -x- | 129.250.3.0 |
| 18 | | 62.73.179.150 | - | ?(United Kingdom) | * | 84 | -x- | Verio UK london01 |
| 19 | | 91.198.165.76 | - | | | 85 | -x- | 91.198.165.0 |
| 20 | | 185.24.98.37 | kitz.co.uk | - | | 88 | -x- | 185.24.98.0 |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to kitz.co.uk, average = 88ms, min = 77ms, max = 98ms -- 27-May-2014 20:57:39
-
From BSE, Suffolk, first by name and then by IPv4 address --
[Duo2 ~]$ traceroute kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 AP (192.168.1.254) 0.390 ms 0.482 ms 0.565 ms
2 host-92-24-176-1.ppp.as43234.net (92.24.176.1) 22.156 ms 23.510 ms 24.352 ms
3 host-78-151-230-45.as13285.net (78.151.230.45) 28.740 ms 28.905 ms 29.601 ms
4 host-78-151-230-24.as13285.net (78.151.230.24) 31.433 ms 32.096 ms host-78-151-230-4.as13285.net (78.151.230.4) 33.008 ms
5 host-78-144-1-24.as13285.net (78.144.1.24) 37.143 ms host-78-144-1-32.as13285.net (78.144.1.32) 37.852 ms host-78-144-1-34.as13285.net (78.144.1.34) 35.106 ms
6 xe-10-2-0-scr010.sov.as13285.net (78.144.0.216) 34.994 ms host-78-144-10-209.as13285.net (78.144.10.209) 37.498 ms host-78-144-0-135.as13285.net (78.144.0.135) 37.482 ms
7 195.66.237.228 (195.66.237.228) 64.328 ms 197.078 ms 26.886 ms
8 91.198.165.76 (91.198.165.76) 28.437 ms 28.398 ms 31.702 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Duo2 ~]$
[Duo2 ~]$ traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 AP (192.168.1.254) 0.495 ms 0.399 ms 0.327 ms
2 host-92-24-176-1.ppp.as43234.net (92.24.176.1) 21.381 ms 22.660 ms 23.009 ms
3 host-78-151-230-45.as13285.net (78.151.230.45) 27.481 ms 28.249 ms 29.521 ms
4 host-78-151-230-12.as13285.net (78.151.230.12) 29.569 ms host-78-151-230-44.as13285.net (78.151.230.44) 33.294 ms host-78-151-230-16.as13285.net (78.151.230.16) 30.619 ms
5 host-78-144-1-42.as13285.net (78.144.1.42) 32.484 ms host-78-144-1-12.as13285.net (78.144.1.12) 32.205 ms host-78-144-1-22.as13285.net (78.144.1.22) 36.204 ms
6 host-78-144-0-121.as13285.net (78.144.0.121) 33.219 ms host-78-144-10-203.as13285.net (78.144.10.203) 36.115 ms host-78-144-0-135.as13285.net (78.144.0.135) 36.366 ms
7 195.66.237.228 (195.66.237.228) 40.088 ms 26.075 ms 26.664 ms
8 91.198.165.76 (91.198.165.76) 28.060 ms 29.807 ms 29.683 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Duo2 ~]$
Now from SW Wales, first by name and then by IPv4 address --
[Quad ~]$ traceroute kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 40 byte packets
1 192.168.0.100 (192.168.0.100) 1.991 ms 2.280 ms 3.275 ms
2 85-210-250-37.dynamic.dsl.as9105.com (85.210.250.37) 41.103 ms 42.189 ms 43.399 ms
3 85.210.255.2 (85.210.255.2) 43.710 ms 44.510 ms 44.901 ms
4 host-78-151-228-82.as13285.net (78.151.228.82) 46.765 ms host-78-151-228-88.as13285.net (78.151.228.88) 47.323 ms host-78-151-228-82.as13285.net (78.151.228.82) 47.915 ms
5 host-78-144-11-127.as13285.net (78.144.11.127) 49.657 ms host-78-144-11-117.as13285.net (78.144.11.117) 50.212 ms host-78-144-11-103.as13285.net (78.144.11.103) 51.584 ms
6 eqx1.routers.eqx.misp.co.uk (195.66.225.228) 54.062 ms 54.638 ms 55.137 ms
7 91.198.165.74 (91.198.165.74) 56.377 ms 41.941 ms 40.607 ms
8 bit-tech2.servers.rbl-mer.misp.co.uk (91.198.165.69) 49.033 ms 49.187 ms 49.499 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Quad ~]$
[Quad ~]$ traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 40 byte packets
1 192.168.0.100 (192.168.0.100) 1.146 ms 1.397 ms 1.982 ms
2 85-210-250-37.dynamic.dsl.as9105.com (85.210.250.37) 38.983 ms 39.379 ms 40.052 ms
3 85.210.255.2 (85.210.255.2) 42.450 ms 42.674 ms 42.988 ms
4 host-78-151-228-66.as13285.net (78.151.228.66) 45.704 ms host-78-151-228-92.as13285.net (78.151.228.92) 46.110 ms host-78-151-228-88.as13285.net (78.151.228.88) 47.829 ms
5 host-78-144-11-125.as13285.net (78.144.11.125) 54.858 ms host-78-144-11-103.as13285.net (78.144.11.103) 49.799 ms host-78-144-11-131.as13285.net (78.144.11.131) 50.970 ms
6 eqx1.routers.eqx.misp.co.uk (195.66.225.228) 52.010 ms 52.372 ms 52.911 ms
7 91.198.165.74 (91.198.165.74) 54.729 ms 40.711 ms 41.492 ms
8 bit-tech2.servers.rbl-mer.misp.co.uk (91.198.165.69) 42.856 ms 41.023 ms 41.315 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Quad ~]$
Finally from the state of New Jersey, USA, first by name and then by IPv4 address --
[Build64R6 ~]$ traceroute kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 10.40.22.1 (10.40.22.1) 0.210 ms 0.160 ms 0.142 ms
2 173.63.208.1 (173.63.208.1) 4.091 ms 4.890 ms 5.897 ms
3 G0-3-3-1.NWRKNJ-LCR-21.verizon-gni.net (130.81.177.194) 8.020 ms 8.007 ms 7.990 ms
4 130.81.199.14 (130.81.199.14) 6.706 ms ae0-0.NWRK-BB-RTR1.verizon-gni.net (130.81.209.154) 6.501 ms ae1-0.NWRK-BB-RTR1.verizon-gni.net (130.81.209.146) 7.493 ms
5 * * *
6 0.ae1.BR2.NYC4.ALTER.NET (140.222.229.91) 10.104 ms 10.586 ms 10.538 ms
7 204.255.168.114 (204.255.168.114) 47.678 ms 44.080 ms 204.255.168.110 (204.255.168.110) 42.947 ms
8 be2060.ccr21.jfk02.atlas.cogentco.com (154.54.31.9) 41.864 ms be2063.mpd22.jfk02.atlas.cogentco.com (154.54.47.57) 40.565 ms be2060.ccr21.jfk02.atlas.cogentco.com (154.54.31.9) 40.856 ms
9 be2349.mpd21.lon13.atlas.cogentco.com (154.54.30.178) 114.168 ms be2350.mpd22.lon13.atlas.cogentco.com (154.54.30.186) 110.963 ms be2348.ccr22.lon13.atlas.cogentco.com (154.54.30.170) 111.122 ms
10 be2317.ccr22.lon01.atlas.cogentco.com (154.54.73.178) 111.823 ms be2315.ccr22.lon01.atlas.cogentco.com (154.54.73.110) 111.465 ms be2317.ccr22.lon01.atlas.cogentco.com (154.54.73.178) 112.124 ms
11 te3-8.ccr01.lon10.atlas.cogentco.com (154.54.75.66) 111.856 ms 112.369 ms te3-2.ccr01.lon10.atlas.cogentco.com (130.117.51.178) 111.947 ms
12 te3-2.ccr01.lon15.atlas.cogentco.com (154.54.57.234) 228.190 ms 228.186 ms 227.783 ms
13 te3-2.ccr01.lon14.atlas.cogentco.com (154.54.58.49) 113.318 ms 112.910 ms 112.991 ms
14 te0-6-0-3.rcr21.lhr01.atlas.cogentco.com (130.117.51.185) 112.139 ms 113.849 ms 111.816 ms
15 149.6.8.226 (149.6.8.226) 85.881 ms 86.743 ms 86.800 ms
16 91.198.165.76 (91.198.165.76) 97.611 ms 97.343 ms 96.945 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Build64R6 ~]$
[Build64R6 ~]$ traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 10.40.22.1 (10.40.22.1) 0.174 ms 0.137 ms 0.181 ms
2 173.63.208.1 (173.63.208.1) 1.823 ms 2.187 ms 2.683 ms
3 G0-3-3-1.NWRKNJ-LCR-21.verizon-gni.net (130.81.177.194) 8.685 ms 8.572 ms 8.557 ms
4 ae0-0.NWRK-BB-RTR1.verizon-gni.net (130.81.209.154) 21.459 ms 6.727 ms ae1-0.NWRK-BB-RTR1.verizon-gni.net (130.81.209.146) 8.062 ms
5 * * *
6 * * *
7 204.255.168.114 (204.255.168.114) 46.648 ms 45.917 ms 46.359 ms
8 be2061.ccr22.jfk02.atlas.cogentco.com (154.54.3.69) 46.714 ms be2060.ccr21.jfk02.atlas.cogentco.com (154.54.31.9) 41.767 ms be2063.mpd22.jfk02.atlas.cogentco.com (154.54.47.57) 40.499 ms
9 be2348.ccr22.lon13.atlas.cogentco.com (154.54.30.170) 111.508 ms be2350.mpd22.lon13.atlas.cogentco.com (154.54.30.186) 111.734 ms be2348.ccr22.lon13.atlas.cogentco.com (154.54.30.170) 111.906 ms
10 be2316.ccr21.lon01.atlas.cogentco.com (154.54.73.114) 113.952 ms 113.763 ms be2317.ccr22.lon01.atlas.cogentco.com (154.54.73.178) 111.106 ms
11 te3-8.ccr01.lon10.atlas.cogentco.com (154.54.75.66) 111.071 ms te3-2.ccr01.lon10.atlas.cogentco.com (130.117.51.178) 112.702 ms te3-8.ccr01.lon10.atlas.cogentco.com (154.54.75.66) 113.095 ms
12 te3-2.ccr01.lon15.atlas.cogentco.com (154.54.57.234) 111.070 ms 111.043 ms 110.434 ms
13 te3-2.ccr01.lon14.atlas.cogentco.com (154.54.58.49) 112.786 ms 112.730 ms 112.473 ms
14 te0-6-0-3.rcr21.lhr01.atlas.cogentco.com (130.117.51.185) 110.943 ms 111.726 ms 111.036 ms
15 149.6.8.226 (149.6.8.226) 87.172 ms 86.256 ms 85.590 ms
16 91.198.165.76 (91.198.165.76) 102.457 ms 101.914 ms 102.548 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[Build64R6 ~]$
So "whois" 91.198.165.76 ?
[Duo2 ~]$ whois 91.198.165.76
[Querying whois.ripe.net]
[whois.ripe.net]
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '91.198.165.0 - 91.198.165.255'
% Abuse contact for '91.198.165.0 - 91.198.165.255' is 'sales@tsohost.co.uk'
inetnum: 91.198.165.0 - 91.198.165.255
netname: UKWEBHOSTING2
descr: UK Webhosting Ltd
country: GB
org: ORG-UWL3-RIPE
admin-c: AS8089-RIPE
tech-c: UWLN1-RIPE
status: ASSIGNED PI
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
mnt-by: UKWEBHOSTING-MNT
mnt-routes: UKWEBHOSTING-MNT
mnt-domains: UKWEBHOSTING-MNT
source: RIPE # Filtered
organisation: ORG-UWL3-RIPE
org-name: UK Webhosting Ltd
org-type: LIR
address: UK Webhosting Ltd
address: Adam Smith
address: St Andrew's House, St Mary's Walk
address: SL6 1QZ Maidenhead
address: UNITED KINGDOM
phone: +441628200161
fax-no: +441628200161
abuse-c: AR17974-RIPE
mnt-ref: UKWEBHOSTING-MNT
mnt-ref: RIPE-NCC-HM-MNT
mnt-by: RIPE-NCC-HM-MNT
source: RIPE # Filtered
role: UK Webhosting Ltd - NOC
address: 4th Floor, 215 Marsh Wall, London, E14 9FJ
admin-c: AS8089-RIPE
tech-c: AS8089-RIPE
nic-hdl: UWLN1-RIPE
mnt-by: UKWEBHOSTING-MNT
source: RIPE # Filtered
person: Adam Smith
address: UK Webhosting Ltd
address: St Andrew's House
address: St Mary's Walk
address: Maidenhead
address: SL6 1QZ
phone: +44 1628 200161
nic-hdl: AS8089-RIPE
mnt-by: UKWEBHOSTING-MNT
source: RIPE # Filtered
% Information related to '91.198.165.0/24AS198047'
route: 91.198.165.0/24
descr: 91.198
origin: AS198047
mnt-by: UKWEBHOSTING-MNT
source: RIPE # Filtered
% Information related to '91.198.165.0/24AS35732'
route: 91.198.165.0/24
descr: UK WEB PI
origin: AS35732
mnt-by: UKWEBHOSTING-MNT
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.73.1 (DBC-WHOIS2)
[Duo2 ~]$
-
ISP: Plusnet
Location: Worcestershire
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 5 ms 1 ms 1 ms 192.168.0.1
2 30 ms 24 ms 26 ms lo0-central10.pcl-ag05.plus.net [195.166.128.186]
3 26 ms 25 ms 25 ms link-a-central10.pcl-gw01.plus.net [212.159.2.176]
4 26 ms 24 ms 54 ms xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
5 26 ms 25 ms 24 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
6 32 ms 31 ms 34 ms vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
7 33 ms 31 ms 33 ms ae-44-44.ebr1.Paris1.Level3.net [4.69.159.94]
8 36 ms 31 ms 31 ms ae-71-71.csw2.Paris1.Level3.net [4.69.161.82]
9 33 ms 31 ms 38 ms ae-2-70.edge4.Paris1.Level3.net [4.69.168.71]
10 41 ms 39 ms 38 ms NTT-level3-2x10G.Paris.Level3.net [4.68.63.118]
11 2099 ms 44 ms 43 ms ae-4.r04.parsfr01.fr.bb.gin.ntt.net [129.250.4.117]
12 55 ms 47 ms 52 ms ae-3.r20.parsfr01.fr.bb.gin.ntt.net [129.250.6.176]
13 54 ms 53 ms 57 ms as-2.r23.londen03.uk.bb.gin.ntt.net [129.250.5.8]
14 53 ms 57 ms 54 ms ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.5.41]
15 68 ms 61 ms 61 ms ae-2.r02.londen01.uk.bb.gin.ntt.net [129.250.3.1]
16 54 ms 55 ms 54 ms ae-1.r03.londen01.uk.bb.gin.ntt.net [129.250.3.37]
17 57 ms 60 ms 58 ms 91.198.165.76
18 65 ms 51 ms 41 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
-
kind of reminds me when I was on tiscali/talktalk. Almost all my traffic was routed london-frankfurt-munich-london-etc for some weird reason. I never did get to the bottom of it.
-
Thanks guys... still not sure whats happening... its normally 15ms, yet atm its all over the place going round London and France. ???
The fact that it now says UK Webhosting is fine.. I wont show as Vidahost cause its my own server.
-
From mid Kent:
root@chaffinch:/home/eric# traceroute -I kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 0.459 ms 0.847 ms 0.852 ms
2 host-2-97-160-1.as13285.net (2.97.160.1) 16.445 ms 17.240 ms 18.827 ms
3 host-78-151-238-209.as13285.net (78.151.238.209) 20.821 ms 21.623 ms 22.019 ms
4 host-78-151-238-220.as13285.net (78.151.238.220) 23.212 ms 24.003 ms 25.994 ms
5 host-78-144-1-48.as13285.net (78.144.1.48) 25.776 ms 27.002 ms 27.783 ms
6 xe-10-2-0-scr010.sov.as13285.net (78.144.0.216) 27.983 ms 18.560 ms 18.942 ms
7 195.66.237.228 (195.66.237.228) 21.722 ms 17.904 ms 18.675 ms
8 91.198.165.76 (91.198.165.76) 21.461 ms 21.335 ms 21.704 ms
9 kitz.servers.eqx.misp.co.uk (185.24.98.37) 21.299 ms 19.297 ms 19.271 ms
root@chaffinch:/home/eric#
(In Linux, the -I parameter forces it to use ICMP echo for the probes. Without it, it times out in the same way as B*cat's responses above).
-
Ahh... thank you for the explanation Eric. :)
Seems like Level3 does have some sort of routing problem, its outside of the ISP network and also my hosts, so I guess I'll just have to hope that it get fixed at some point.
-
Its more likely that its a peering issue kitz :
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.10
2 * * * Request timed out.
3 10 ms 15 ms 15 ms 02780842.bb.sky.com [2.120.8.66]
4 10 ms 9 ms 10 ms ae-1.r00.londen01.uk.bb.gin.ntt.net [83.231.199.161]
5 10 ms 10 ms 9 ms ae-1.r03.londen01.uk.bb.gin.ntt.net [129.250.3.37]
6 9 ms 9 ms 9 ms 62.73.179.150
7 12 ms 10 ms 14 ms 91.198.165.76
8 10 ms 9 ms 9 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
I suspect your host doesn't peer directly with L3 & Plusnet don't peer directly with NTT. Sky have peering links with both last time I checked the BGP adverts.
-
both Level3 and NTT have nodes in london so there should be no need for it to go to paris and do a sightseeing tour around the french capital.
-
both Level3 and NTT have nodes in london so there should be no need for it to go to paris and do a sightseeing tour around the french capital.
Doesn't work that way I'm afraid - Paris (& indeed AMS-IX) will likely be the lowest-metric route if one of the ISPs doesn't have the appropriate LINX/LoNAP peering.
Telefonica (O2/Be as was) for example are notorious for using sub-optimal routing in this way as it saves them a lot of cash (which they don't have as they're going bust).
-
Having looked at RIPEstat for 185.24.98.37 (https://stat.ripe.net/185.24.98.37#tabId=at-a-glance) and it seems that routings were being exchanged between Cogent and NTT.
-
From that link you can see there's no peering from the website host to L3 in London but there is peering to L3 in AMS-IX, hence if Plusnet don't peer with NTT in London then the traffic will go via AMS-IX - or private peering in Paris as they are the lowest metric.
However Plusnet do in fact peer with NTT (AS2914) in London so I would assume that the issue lies with NTT/Plusnet.
Edit - and NTT changing BGP adverts for whatever reason may well have done that temporarily.
-
Thanks for the info guys, although you lost me a bit there :(
What I cant understand is the following:
If I trace to my hosts website I get this
Tracing route to vidahost.com [91.146.106.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 67 ms 25 ms 16 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 15 ms 15 ms 15 ms link-a-central10.ptn-gw01.plus.net [212.159.2.132]
4 15 ms 15 ms 16 ms xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
5 16 ms 16 ms * te-4-2.car5.London1.Level3.net [217.163.45.249]
6 15 ms 16 ms 16 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
7 19 ms 16 ms 15 ms ae-227-3603.edge3.London1.Level3.net [4.69.166.154]
8 17 ms 17 ms 18 ms be3043.ccr22.lon01.atlas.cogentco.com [130.117.15.245]
9 17 ms 17 ms 17 ms te3-8.ccr01.lon10.atlas.cogentco.com [154.54.75.66]
10 17 ms 17 ms 17 ms te3-2.ccr01.lon15.atlas.cogentco.com [154.54.57.234]
11 18 ms 18 ms 17 ms te3-2.ccr01.lon14.atlas.cogentco.com [154.54.58.49]
12 18 ms 18 ms 18 ms te0-6-0-3.rcr21.lhr01.atlas.cogentco.com [130.117.51.185]
13 18 ms 19 ms 19 ms 149.6.8.226 (cogentco peer point)
14 19 ms 18 ms 18 ms 91.198.165.76 <-------- webhost gateway Maidenhead/Slough
15 18 ms 18 ms 18 ms bit-tech2.servers.rbl-mer.misp.co.uk [91.198.165.68]
16 18 ms 17 ms 18 ms 91.146.106.2
Yet to my server gives this
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 50 ms 21 ms 56 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 16 ms 16 ms 15 ms link-b-central10.ptn-gw02.plus.net [212.159.2.134]
4 15 ms 15 ms 15 ms xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
5 17 ms 16 ms 19 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 16 ms 16 ms 37 ms ae1.pcl-cr01.plus.net [195.166.129.1]
7 16 ms 15 ms 16 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.213]
8 22 ms 23 ms 22 ms vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
9 22 ms 22 ms 22 ms ae-42-42.ebr1.Paris1.Level3.net [4.69.159.86]
10 22 ms 22 ms 22 ms ae-91-91.csw4.Paris1.Level3.net [4.69.161.90]
11 23 ms 22 ms 22 ms ae-4-90.edge4.Paris1.Level3.net [4.69.168.199]
12 24 ms 24 ms 24 ms NTT-level3-2x10G.Paris.Level3.net [4.68.63.118]
13 24 ms 24 ms 24 ms ae-0.r20.parsfr01.fr.bb.gin.ntt.net [129.250.5.136]
14 24 ms 23 ms 24 ms as-2.r23.londen03.uk.bb.gin.ntt.net [129.250.5.8]
15 25 ms 25 ms 25 ms ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.5.41]
16 25 ms 26 ms 25 ms ae-2.r02.londen01.uk.bb.gin.ntt.net [129.250.3.1]
17 27 ms 25 ms 25 ms ae-1.r03.londen01.uk.bb.gin.ntt.net [129.250.3.37]
18 26 ms 25 ms 25 ms 62.73.179.150 (Verio ntt.net peer point)
19 26 ms 26 ms 26 ms 91.198.165.76 <-------- webhost gateway Maidenhead/Slough
20 25 ms 25 ms 25 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
So I have to go through Vidahosts gateway (91.198.165.76) anyhow... and if I tracert to there I get correct routing
C:\Users\kitz>tracert 91.198.165.76
Tracing route to 91.198.165.76 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 17 ms 16 ms 16 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 16 ms 15 ms 15 ms link-a-central10.ptn-gw01.plus.net [212.159.2.132]
4 15 ms 15 ms 15 ms xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
5 * * * Request timed out.
6 16 ms 16 ms 16 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
7 16 ms 16 ms 16 ms ae-227-3603.edge3.London1.Level3.net [4.69.166.154]
8 17 ms 17 ms 17 ms be3043.ccr22.lon01.atlas.cogentco.com [130.117.15.245]
9 17 ms 18 ms 17 ms te3-8.ccr01.lon10.atlas.cogentco.com [154.54.75.66]
10 17 ms 17 ms 17 ms te3-2.ccr01.lon15.atlas.cogentco.com [154.54.57.234]
11 18 ms 18 ms 17 ms te3-2.ccr01.lon14.atlas.cogentco.com [154.54.58.49]
12 18 ms 18 ms 18 ms te0-6-0-3.rcr21.lhr01.atlas.cogentco.com [130.117.51.185]
13 18 ms 17 ms 18 ms 149.6.8.226
14 19 ms 18 ms 19 ms 91.198.165.76
So why is anyone from Plusnet having to go via france to get to my server behind exactly the same gateway?
:confused: :shrug2:
-
Target Name: kitz.co.uk
IP: 185.24.98.37
Date/Time: 30/05/2014 01:01:59
1 0 ms 0 ms N/A home.gateway.home.gateway [192.168.1.254]
2 14 ms 68 ms 14 ms lo0-central10.pcl-ag04.plus.net [195.166.128.185]
3 14 ms 14 ms 14 ms link-b-central10.pcl-gw02.plus.net [212.159.2.174]
4 14 ms 23 ms 13 ms xe-0-2-0.pcl-cr02.plus.net [212.159.0.206]
5 47 ms 13 ms 14 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 26 ms 14 ms 14 ms xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
7 22 ms 20 ms 20 ms vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
8 21 ms 20 ms 21 ms ae-44-44.ebr1.Paris1.Level3.net [4.69.159.94]
9 21 ms 20 ms 20 ms ae-81-81.csw3.Paris1.Level3.net [4.69.161.86]
10 21 ms 21 ms 21 ms ae-3-80.edge4.Paris1.Level3.net [4.69.168.135]
11 21 ms 22 ms 22 ms NTT-level3-2x10G.Paris.Level3.net [4.68.63.118]
12 22 ms 22 ms 22 ms ae-0.r20.parsfr01.fr.bb.gin.ntt.net [129.250.5.136]
13 23 ms 30 ms 22 ms as-2.r23.londen03.uk.bb.gin.ntt.net [129.250.5.8]
14 23 ms 24 ms 23 ms ae-2.r02.londen03.uk.bb.gin.ntt.net [129.250.5.41]
15 23 ms 23 ms 23 ms ae-2.r02.londen01.uk.bb.gin.ntt.net [129.250.3.1]
16 23 ms 23 ms 23 ms ae-1.r03.londen01.uk.bb.gin.ntt.net [129.250.3.37]
17 23 ms 23 ms 23 ms [62.73.179.150]
18 24 ms 24 ms 23 ms [91.198.165.76]
19 24 ms 24 ms 23 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Ping statistics for kitz.co.uk - Default Settings
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 23ms, Maximum = 24ms, Average = 23ms
-
You'd have to prod someone at Plusnet but my guess is that L3 has a lower metric (cost) to Plusnet when compared to NTT or Cogent. That means the route from Plusnet is going to use L3 transit from Plusnet's edge routers.
However your webhost wants to use NTT for the same reason and that forces the transit to go via Paris (NTT<->L3 peering) as there's no direct route to UKWEB from L3 in London and/or the transit is too expensive (quite probable knowing L3).
I suspect that your webhost is using NTT because its significantly cheaper than using Cogent but for their main website/etc they will accept traffic on both NTT & Cogent.
That would make sense if NTT transit is significantly cheaper for UKWEB - put all the customer website traffic onto NTT transit as that's the vast majority of their traffic; their own website probably uses trivial amounts of traffic in comparison.
The "gateway" is a bit of a red herring I'm afraid as its on a totally different subnet to the website so routing may well be set up differently - and it appears that it is indeed setup differently.
It looks like your webhost rearranged their routing at 0200 on May 24 - does that correspond with when you started noticing issues?
Oh and what does the route look like if you tracert from this website to your IP address?
-
Cheers for the reply rizla.
On Thurs eve it was supposedly flagged by PN, but it would seem that the Paris route is a regular 'feature' of Level3 :(
Plusnet only use L3 and BT for transit.. plus the common peer points.
L3 seem to have weird and wonderful routing.
I also raised it with vidahost on Friday.. got a response within a few mins saying although this was outside their control but they'd see what they could do. I later got an email to say theyve applied to direct peer with Plusnet. Tonight Ive got an email saying that hopefully within 48-72 hours this should be completed.
It looks like my hosts already direct peer with a couple of UK ISPs - including UKO - which is why on Sky you didnt see any problems.
-
different route now, via clognet (as one of my friends used to call cogent)
C:\Users\loonylion>tracert kitz.co.uk
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms smoothwall [10.0.0.10]
2 27 ms 21 ms 21 ms lo0-central10.pcl-ag08.plus.net [195.166.128.189
]
3 21 ms 21 ms 21 ms link-a-central10.pcl-gw01.plus.net [212.159.2.18
8]
4 21 ms 21 ms 49 ms xe-9-1-0.pcl-cr01.plus.net [212.159.0.220]
5 21 ms 21 ms 21 ms xe-11-1-0.edge3.London2.Level3.net [212.187.201.
209]
6 23 ms 22 ms 21 ms vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202
.169]
7 21 ms 21 ms 22 ms ae-48-48.ebr1.London15.Level3.net [4.69.159.78]
8 22 ms 24 ms 21 ms ae-42-42.ebr1.London1.Level3.net [4.69.167.22]
9 22 ms 22 ms 21 ms ae-56-111.csw1.London1.Level3.net [4.69.153.114]
10 21 ms 21 ms 21 ms ae-115-3501.edge3.London1.Level3.net [4.69.166.1
30]
11 23 ms 23 ms 23 ms be3043.ccr22.lon01.atlas.cogentco.com [130.117.1
5.245]
12 22 ms 22 ms 22 ms te3-8.ccr01.lon10.atlas.cogentco.com [154.54.75.
66]
13 24 ms 23 ms 22 ms te3-2.ccr01.lon15.atlas.cogentco.com [154.54.57.
234]
14 26 ms 25 ms 24 ms te3-2.ccr01.lon14.atlas.cogentco.com [154.54.58.
49]
15 24 ms 23 ms 24 ms te0-6-0-3.rcr21.lhr01.atlas.cogentco.com [130.11
7.51.185]
16 24 ms 24 ms 24 ms 149.6.8.226
17 25 ms 25 ms 25 ms 91.198.165.76
18 23 ms 24 ms 23 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Trace complete.
-
ooh... me too.
Earlier it was still going via Paris
-
Cheers for the reply rizla.
On Thurs eve it was supposedly flagged by PN, but it would seem that the Paris route is a regular 'feature' of Level3 :(
Plusnet only use L3 and BT for transit.. plus the common peer points.
L3 seem to have weird and wonderful routing.
I also raised it with vidahost on Friday.. got a response within a few mins saying although this was outside their control but they'd see what they could do. I later got an email to say theyve applied to direct peer with Plusnet. Tonight Ive got an email saying that hopefully within 48-72 hours this should be completed.
It looks like my hosts already direct peer with a couple of UK ISPs - including UKO - which is why on Sky you didnt see any problems.
Sky have the best routing of any UK ISP - bar none - which is one of the reasons I binned Telefonica (Be) a couple of years back. I'd have to look again but they have transit rented from just about every major carrier so it wouldn't really matter to me who your host used, Sky routing would stay within the UK. Even if there wasn't direct peering there's a choice of L3, NTT, Cogent, Tata <spit>, Hurricane Electric plus a few Euro telecos at LINX/LoNAP/PacketExchange.
I wouldn't be happy with an ISP who only use L3 & BT - BTs network is frankly a shambles (see RevK's comments about 3% PL 24/7) and L3 are a law unto themselves (always have been).
Your host seems on the ball though, nice to see them taking matters into their own hands :)
http://bgp.he.net/AS5607#_graph4 <--BSkyB IPv4 routes
http://bgp.he.net/AS4589#_graph4 <--Easynet IPv4 routes
http://bgp.he.net/AS6871#_graph4 <--Plusnet IPv4 routes (basically BTnet, L3, HE - virtually every route is via L3 which I wouldn't be happy with).
-
I am not following this but here is one from TTB, it looks normal to me. (From Worcestershire)
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
>tracert kitz.co.uk
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 4 ms 4 ms 4 ms host-62-24-233-143.as13285.net [62.24.233.143]
2 5 ms 5 ms 5 ms 78.151.227.0
3 5 ms 5 ms 5 ms host-78-151-227-21.as13285.net [78.151.227.21]
4 11 ms 10 ms 11 ms host-78-144-9-97.as13285.net [78.144.9.97]
5 11 ms 11 ms 11 ms 195.66.237.228
6 13 ms 13 ms 12 ms 91.198.165.76
7 11 ms 11 ms 12 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Trace complete.
Pinging kitz.co.uk [185.24.98.37] with 32 bytes of data:
Ping statistics for 185.24.98.37:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
-
Also a TT service and from BSE, Suffolk.
[Duo2 ~]$ sudo traceroute -I kitz.co.uk
traceroute to kitz.co.uk (185.24.98.37), 30 hops max, 60 byte packets
1 AP (192.168.1.254) 0.343 ms 0.426 ms 0.552 ms
2 host-92-24-128-1.ppp.as43234.net (92.24.128.1) 28.276 ms 30.019 ms 30.429 ms
3 host-78-151-230-45.as13285.net (78.151.230.45) 34.648 ms 35.561 ms 36.254 ms
4 host-78-151-230-28.as13285.net (78.151.230.28) 38.120 ms 38.828 ms 40.176 ms
5 host-78-144-1-42.as13285.net (78.144.1.42) 41.437 ms 42.369 ms 43.109 ms
6 xe-10-2-0-scr010.sov.as13285.net (78.144.0.216) 55.185 ms 54.888 ms 54.971 ms
7 195.66.237.228 (195.66.237.228) 47.006 ms 33.322 ms 33.404 ms
8 91.198.165.76 (91.198.165.76) 36.028 ms 34.733 ms 35.592 ms
9 kitz.servers.eqx.misp.co.uk (185.24.98.37) 35.466 ms 32.864 ms 33.933 ms
[Duo2 ~]$
-
For those not really following this then look at :
http://bgp.he.net/AS6871#_graph4
Start from the left & work to the right (hover the mouse over the bubbles to get info). Needs javascript for you guys running noscript.
Those are the public routes which Plusnet advertise - or in simple terms this is like a "how to contact us" broadcast for all of Plusnet's IPv4 addresses. I'm using the Hurricane Electric BGP looking glass facility because its got a great graph which shows routing much better than most.
You'll see that Plusnet have only one real public route to the internet - that's Level 3 (AS3356). They also have BTnet (AS2856) but that only provides routing to QWest (AS209). The last "route" you see out of Plusnet is Hurricane Electric (AS6939) which is a private peering link. They will have lots of these private peering links but ultimately they are (IMHO) way too reliant on L3.
Level 3 are one of the original backbone transit providers & their policies are still somewhere in the stone age of the internet in terms of any flexibility - and they cost more than average for very average/poor service IMHO.
The problem with this website is/was that due to Plusnet's reliance on Level 3 transit anyone visiting from Plusnet was having to go to Paris where they'd get hooked up with the website hosts preferred (cheaper) network transit. Kitz' webhost has now decided to fix that problem by doing some private peering (a free connection between networks) with Plusnet.
That indicates a damn good hosting service IMHO - its not their problem that Plusnet are run by BT but they've gone out and done the right thing for their customer. +1 for that.
I guess routing isn't something that even 0.1% of people consider when choosing an ISP :(
-
TBH Rizla I was also surprised the other day when I also found out that basically just how reliant Plusnet are on L3. It didnt used to be that way.
---
Meant to add.. Sky is likely good because uko/easynets was... which as you know they bought out.
-
Sky has come a very VERY long way since they bought Easynet - they have MUCH better network architects/BOFHs than BT these days (they pay a lot better).
I was frankly astounded at the complete ignorance of the guy who was arguing with RevK about 3% PL within BTnet - he styled himself "BT Chief Network Architect" (which apparently he is) or some such nonsense. The guy is completely clueless and if he's the top techie then its no wonder BTnet is so absymal.
Re Plusnet & L3 - that'll just be BT imposing the same public routing which they have. I doubt Plusnet have any say in the matter - they'll have control of private peering and not much else.
-
Forgot to update this earlier.
This has now been sorted and my hosts direct peer with Plusnet.
Anyone coming in via one of Plusnets PTW gateways should reach my server in a few hops.
-
Sky are good probably because of easynet's network etho's, when I was on ukonline which was basically a rebadged easynet service It was the best peering/transit I had ever seen on any isp, excellent routes to everywhere.
I agree plusnet over relying on level3 isnt a good thing, its worrying actually, never like to see that from a provider.
What I will say tho is that I dont frequently see level3 in traceroutes, that graph will be for non peered traffic, and plusnet do seem to have a reasonable amount of peering in place.
e.g. traffic to my german server does not touch level3, neither to holland, as well as a french server. But outside of EU level3 is used much more, so seems mainly for international transit. Basically where plusnet arent likely to have peering.