any Metronet customers on higher speeds

Just wanted to check on 1 Mbps or 2 Mbps service being OK.

Can you confirm who actually supplies the ADSL connectivity ?

A traceroute to say news.bbc.co.uk would be useful, and the part
of the login user details after the "@" also handy... (From the
past, dial-up access wasn't in-house but supplied by AIH, so is
ADSL done on similar lines ?) Peter M.

Dear Peter,

BT enable the DSLAM to ADSL modem/router link, and as-if-by-magic (TM) the
data appears on our network. We do not resell BT's ADSL connection, we have
our own peers (two of them plus backups). You should know that the all ADSL
connections follow the same route and arrive in the same place on our
network; so a traceroute from a 512kbps connection should be the same as a
1Mbps and 2Mbps one.

Bear in mind that recently the BBC decided to move their servers to the US,
stranger things have happened.....xpilot and such though is perfectly
okay....

From one of our customers, a 1Mbps link to several sites:

traceroute to www.bbc.net.uk (212.58.240.110), 30 hops max, 38 byte packets
1 213-162-122-29.andycl935.adsl.metronet.co.uk (213.162.122.29) 0.224 ms 0.148 ms 0.145 ms
2 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.785 ms 1.109 ms 0.764 ms
3 metronethg1.ilford.broadband.bt.net (217.47.153.121) 25.809 ms 13.604 ms 14.347 ms
4 gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.176 ms 13.137 ms 12.775 ms
5 lvl3gw.thn.packetexchange.net (212.187.197.193) 15.218 ms 14.688 ms 17.307 ms
6 so-1-3-0.gar2.London1.level3.net (212.113.3.29) 14.817 ms 15.594 ms 14.721 ms
7 ae0-56.mp2.London1.Level3.net (212.187.131.178) 15.474 ms 13.862 ms 13.736 ms
8 so-1-0-0.bbr2.NewYork1.level3.net (212.187.128.153) 82.750 ms 79.900 ms 79.836 ms
9 gige9-1-54.hsipaccess1.NewYork1.Level3.net (64.159.17.103) 79.254 ms 83.295 ms 80.904 ms
10 unknown.Level3.net (209.246.126.6) 82.014 ms 81.459 ms 82.734 ms
11 www10.thny.bbc.co.uk (212.58.240.110) 83.760 ms 82.932 ms 83.481 ms

traceroute to peach.ripe.net (193.0.0.203), 30 hops max, 38 byte packets
1 213-162-122-29.andycl935.adsl.metronet.co.uk (213.162.122.29) 0.202 ms 0.150 ms 0.144 ms
2 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.776 ms 0.768 ms 0.754 ms
3 metronethg1.ilford.broadband.bt.net (217.47.153.121) 13.148 ms 14.057 ms 25.321 ms
4 gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.265 ms 14.409 ms 14.390 ms
5 lvl3gw.thn.packetexchange.net (212.187.197.193) 13.989 ms 14.780 ms 16.483 ms
6 so-1-2-0.gar1.London1.level3.net (212.113.0.114) 14.981 ms 14.891 ms 15.233 ms
7 so-7-0-0.mp1.London1.Level3.net (212.113.3.1) 15.477 ms 19.835 ms 14.726 ms
8 so-2-0-0.mp1.Amsterdam1.Level3.net (212.187.128.26) 22.134 ms 22.544 ms 21.397 ms
9 gige1-2.core2.Amsterdam1.Level3.net (213.244.165.102) 20.894 ms 21.533 ms 21.880 ms
10 Amsterdam1.ripe.net (193.148.15.68) 22.640 ms 21.581 ms 22.610 ms
11 peach.ripe.net (193.0.0.203) 23.868 ms 22.525 ms 23.114 ms

traceroute to www.mirror.ac.uk (212.219.56.162), 30 hops max, 38 byte packets
1 213-162-122-29.andycl935.adsl.metronet.co.uk (213.162.122.29) 0.211 ms 0.151 ms 0.147 ms
2 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.769 ms 0.778 ms 1.991 ms
3 metronethg1.ilford.broadband.bt.net (217.47.153.121) 13.381 ms 13.031 ms 14.755 ms
4 gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.547 ms 25.559 ms 14.041 ms
5 lvl3gw.thn.packetexchange.net (212.187.197.193) 14.183 ms 14.035 ms 20.410 ms
6 so-1-2-0.gar1.London1.level3.net (212.113.0.114) 13.738 ms 15.020 ms 16.200 ms
7 so-7-0-0.mp1.London1.Level3.net (212.113.3.1) 16.458 ms 14.083 ms 14.734 ms
8 so-3-0-0.mp2.London2.Level3.net (212.187.128.45) 14.756 ms 17.322 ms 13.508 ms
9 pos5-0.hsipaccess1.London2.Level3.net (212.187.129.254) 14.739 ms 15.364 ms 14.249 ms
10 195.50.116.202 (195.50.116.202) 15.460 ms 14.828 ms 14.243 ms
11 lond-scr2.ja.net (146.97.37.73) 15.955 ms 15.065 ms 15.829 ms
12 po5-0.lond-scr.ja.net (146.97.33.1) 14.410 ms 16.575 ms 14.486 ms
13 po0-0-0.chatham-bar.ja.net (146.97.35.18) 17.685 ms 16.308 ms 18.652 ms
14 uog-m.kentman.ac.uk (146.97.40.6) 16.735 ms 17.528 ms 17.956 ms
15 ukc-c-atm1.kentman.ac.uk (212.219.171.22) 19.424 ms 21.036 ms 19.647 ms
16 ukc-c-b.kentman.ac.uk (212.219.171.130) 18.445 ms 18.802 ms 18.939 ms
17 mrcsa.ukc.ac.uk (129.12.254.74) 20.904 ms 19.475 ms 21.254 ms
18 maxwell.mirror.ac.uk (212.219.56.162) 20.064 ms 18.650 ms 19.410 ms

Hope this helps. If you have any further queries then do get in touch.

Regards

Alex

In article <(E-Mail Removed) >, Peter Morgan - 0870 432 9631 wrote:
> Just wanted to check on 1 Mbps or 2 Mbps service being OK.
>
> Can you confirm who actually supplies the ADSL connectivity ?
>
> A traceroute to say news.bbc.co.uk would be useful, and the part
> of the login user details after the "@" also handy... (From the
> past, dial-up access wasn't in-house but supplied by AIH, so is
> ADSL done on similar lines ?) Peter M.


--
Alexander Clouter <(E-Mail Removed)>
MetroNet Support http://www.metronet.co.uk/support/

sub 1ms for the first 2 hops!!! Does this 'customer' (andy?) reside live in
your server building???

steve

Metronet Support wrote:
> Dear Peter,
>
> BT enable the DSLAM to ADSL modem/router link, and as-if-by-magic
> (TM) the
> data appears on our network. We do not resell BT's ADSL connection,
> we have
> our own peers (two of them plus backups). You should know that the
> all ADSL
> connections follow the same route and arrive in the same place on our
> network; so a traceroute from a 512kbps connection should be the same
> as a 1Mbps and 2Mbps one.
>
> Bear in mind that recently the BBC decided to move their servers to
> the US,
> stranger things have happened.....xpilot and such though is perfectly
> okay....
>
> From one of our customers, a 1Mbps link to several sites:
>
> traceroute to www.bbc.net.uk (212.58.240.110), 30 hops max, 38 byte
> packets 1 213-162-122-29.andycl935.adsl.metronet.co.uk
> (213.162.122.29) 0.224 ms 0.148 ms 0.145 ms 2
> 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.785
> ms 1.109 ms 0.764 ms 3 metronethg1.ilford.broadband.bt.net
> (217.47.153.121) 25.809 ms 13.604 ms 14.347 ms 4
> gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.176 ms
> 13.137 ms 12.775 ms 5 lvl3gw.thn.packetexchange.net
> (212.187.197.193) 15.218 ms 14.688 ms 17.307 ms 6
> so-1-3-0.gar2.London1.level3.net (212.113.3.29) 14.817 ms 15.594
> ms 14.721 ms 7 ae0-56.mp2.London1.Level3.net (212.187.131.178)
> 15.474 ms 13.862 ms 13.736 ms 8 so-1-0-0.bbr2.NewYork1.level3.net
> (212.187.128.153) 82.750 ms 79.900 ms 79.836 ms 9
> gige9-1-54.hsipaccess1.NewYork1.Level3.net (64.159.17.103) 79.254 ms
> 83.295 ms 80.904 ms 10 unknown.Level3.net (209.246.126.6) 82.014
> ms 81.459 ms 82.734 ms 11 www10.thny.bbc.co.uk (212.58.240.110)
> 83.760 ms 82.932 ms 83.481 ms
>
> traceroute to peach.ripe.net (193.0.0.203), 30 hops max, 38 byte
> packets 1 213-162-122-29.andycl935.adsl.metronet.co.uk
> (213.162.122.29) 0.202 ms 0.150 ms 0.144 ms 2
> 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.776
> ms 0.768 ms 0.754 ms 3 metronethg1.ilford.broadband.bt.net
> (217.47.153.121) 13.148 ms 14.057 ms 25.321 ms 4
> gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.265 ms
> 14.409 ms 14.390 ms 5 lvl3gw.thn.packetexchange.net
> (212.187.197.193) 13.989 ms 14.780 ms 16.483 ms 6
> so-1-2-0.gar1.London1.level3.net (212.113.0.114) 14.981 ms 14.891
> ms 15.233 ms 7 so-7-0-0.mp1.London1.Level3.net (212.113.3.1) 15.477
> ms 19.835 ms 14.726 ms 8 so-2-0-0.mp1.Amsterdam1.Level3.net
> (212.187.128.26) 22.134 ms 22.544 ms 21.397 ms 9
> gige1-2.core2.Amsterdam1.Level3.net (213.244.165.102) 20.894 ms
> 21.533 ms 21.880 ms 10 Amsterdam1.ripe.net (193.148.15.68) 22.640
> ms 21.581 ms 22.610 ms 11 peach.ripe.net (193.0.0.203) 23.868 ms
> 22.525 ms 23.114 ms
>
> traceroute to www.mirror.ac.uk (212.219.56.162), 30 hops max, 38 byte
> packets 1 213-162-122-29.andycl935.adsl.metronet.co.uk
> (213.162.122.29) 0.211 ms 0.151 ms 0.147 ms 2
> 213-162-122-30.andycl935.adsl.metronet.co.uk (213.162.122.30) 0.769
> ms 0.778 ms 1.991 ms 3 metronethg1.ilford.broadband.bt.net
> (217.47.153.121) 13.381 ms 13.031 ms 14.755 ms 4
> gw.adsl.1.e14.uk.router.parbin.co.uk (213.162.127.6) 13.547 ms
> 25.559 ms 14.041 ms 5 lvl3gw.thn.packetexchange.net
> (212.187.197.193) 14.183 ms 14.035 ms 20.410 ms 6
> so-1-2-0.gar1.London1.level3.net (212.113.0.114) 13.738 ms 15.020
> ms 16.200 ms 7 so-7-0-0.mp1.London1.Level3.net (212.113.3.1) 16.458
> ms 14.083 ms 14.734 ms 8 so-3-0-0.mp2.London2.Level3.net
> (212.187.128.45) 14.756 ms 17.322 ms 13.508 ms 9
> pos5-0.hsipaccess1.London2.Level3.net (212.187.129.254) 14.739 ms
> 15.364 ms 14.249 ms 10 195.50.116.202 (195.50.116.202) 15.460 ms
> 14.828 ms 14.243 ms 11 lond-scr2.ja.net (146.97.37.73) 15.955 ms
> 15.065 ms 15.829 ms 12 po5-0.lond-scr.ja.net (146.97.33.1) 14.410
> ms 16.575 ms 14.486 ms 13 po0-0-0.chatham-bar.ja.net
> (146.97.35.18) 17.685 ms 16.308 ms 18.652 ms 14
> uog-m.kentman.ac.uk (146.97.40.6) 16.735 ms 17.528 ms 17.956 ms 15
> ukc-c-atm1.kentman.ac.uk (212.219.171.22) 19.424 ms 21.036 ms
> 19.647 ms 16 ukc-c-b.kentman.ac.uk (212.219.171.130) 18.445 ms
> 18.802 ms 18.939 ms 17 mrcsa.ukc.ac.uk (129.12.254.74) 20.904 ms
> 19.475 ms 21.254 ms 18 maxwell.mirror.ac.uk (212.219.56.162)
> 20.064 ms 18.650 ms 19.410 ms
>
> Hope this helps. If you have any further queries then do get in
> touch.
>
> Regards
>
> Alex
>
> In article <(E-Mail Removed) >, Peter
> Morgan - 0870 432 9631 wrote:
>> Just wanted to check on 1 Mbps or 2 Mbps service being OK.
>>
>> Can you confirm who actually supplies the ADSL connectivity ?
>>
>> A traceroute to say news.bbc.co.uk would be useful, and the part
>> of the login user details after the "@" also handy... (From the
>> past, dial-up access wasn't in-house but supplied by AIH, so is
>> ADSL done on similar lines ?) Peter M.

--

(¯`·._.· All Outgoing Mail Scanned With Norton Anti-Virus 2003 ·._.·´¯)

No problem!!

It just seemed surprisingly low, but the figures you quote of 10-30ms seem
more in line of what most users see.

Thanks,

Steve

Metronet Support wrote:
> In article <3f43b9eb$0$46011$(E-Mail Removed)>, eusty
> wrote:
>> sub 1ms for the first 2 hops!!! Does this 'customer' (andy?) reside
>> live in your server building???
>>
> As I said, BT supply the DSLAM<->End User link, this goes via ATM to
> BT which then appears by magic on our network. I would be surprised
> if the latencies were high, especially as its pretty much ATM to just
> one stop short of our network infrastructure. The first two hops
> should always be low as its still within BT network and really is
> just pure ATM up to those points.
>
> However, I will be honest and tell you that Andy is on the same
> 'Ilford' BT major ATM node....or whatever they call it. This means,
> if I remember correctly, that once it gets to his local exchange, it
> then goes straight to Ilford which is our local point-of-presence
> with the BT ADSL ATM network. Hence the low pings. However when I
> have been diagnosing ADSL users from our support line its very often
> we get ping times of around 10ms to 30ms. Anything higher is normally
> due to users complaining of slow internet access and we have to
> inform them of a large dubiously titled 'media' download which is
> taking place at the same time
>
> I personally have a couple of Linux machines outside the UK I have
> root access to, if you would like I can do some traceroutes to ADSL
> users around I can, however I would be surprised if there was much
> difference.
>
> Regards
>
> Alex

--

(¯`·._.· All Outgoing Mail Scanned With Norton Anti-Virus 2003 ·._.·´¯)