Murphx Routing and Peering

Having looked at the RIPE peering data for Murphx's AS why is it that they list peering arrangements with the likes of the BBC but virtually all traffic routes out via Cogent?:

http://www.db.ripe.net/whois?form_type=simple&full_q...

My traffic to BBC routes directly, without going via Cogent:
traceroute to www.bbc.net.uk (212.58.246.161), 64 hops max, 72 byte packets
1 dsldevice (95.172.228.201) 11.179 ms 96.393 ms 99.890 ms
2 lns2.uan.the.uk.murphx.net (94.30.127.73) 21.197 ms 20.554 ms 20.910 ms
3 er2.uan.the.uk.murphx.net (94.30.127.66) 21.732 ms 21.431 ms 20.937 ms
4 ge2-7-1.cr2.core.the.uk.murphx.net (94.30.127.237) 21.061 ms 20.989 ms 22.419 ms
5 ge0-1-1.pr1.core.the.uk.murphx.net (94.30.127.218) 20.706 ms 21.811 ms 24.368 ms
6 bbc-gw0-linx.prt0.thdoe.bbc.co.uk (195.66.224.103) 22.814 ms 22.253 ms 20.729 ms
7 212.58.238.129 (212.58.238.129) 21.885 ms 22.084 ms 21.848 ms
8 te12-1.hsw0.cwwtf.bbc.co.uk (212.58.239.222) 25.758 ms 22.604 ms 22.790 ms
9 212.58.255.12 (212.58.255.12) 28.848 ms 24.820 ms 23.848 ms
10 fmt-vip04.cwwtf.bbc.co.uk (212.58.246.161) 21.684 ms 20.634 ms 21.440 ms

And to Gradwell, goes via NetConnex:

traceroute to sip.gradwell.net (193.111.200.56), 64 hops max, 72 byte packets
1 dsldevice (95.172.228.201) 11.957 ms 100.228 ms 98.083 ms
2 lns2.uan.the.uk.murphx.net (94.30.127.73) 20.599 ms 21.915 ms 22.323 ms
3 er2.uan.the.uk.murphx.net (94.30.127.66) 21.114 ms 21.602 ms 20.407 ms
4 ge2-7-1.cr2.core.the.uk.murphx.net (94.30.127.237) 21.018 ms 20.512 ms 21.468 ms
5 ge0-1-1.pr1.core.the.uk.murphx.net (94.30.127.218) 21.160 ms 21.051 ms 21.259 ms
6 linx-gw1.rbsov.ncuk.net (195.66.224.240) 20.948 ms 22.538 ms 21.857 ms
7 ip97-82.thdo.ncuk.net (80.249.97.82) 24.817 ms 25.451 ms 22.933 ms
8 79.135.121.37 (79.135.121.37) 25.523 ms 24.460 ms 24.814 ms
9 79.135.121.21 (79.135.121.21) 25.157 ms 25.186 ms 22.726 ms
10 lilac.gradwell.net (193.111.200.56) 23.665 ms 22.329 ms 22.983 ms

This is with Xilo; not sure if it's different for different providers.

Alan

Same on vivaciti
3 50 ms 51 ms 51 ms er2.uan.the.uk.murphx.net [94.30.127.66]
4 51 ms 51 ms 51 ms ge2-7-1.cr2.core.the.uk.murphx.net [94.30.127.237]
5 51 ms 51 ms 51 ms ge0-1-1.pr1.core.the.uk.murphx.net [94.30.127.218]
6 51 ms 51 ms 51 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
7 51 ms 51 ms 51 ms 212.58.238.153
8 52 ms 51 ms 50 ms 212.58.239.62
9 52 ms 52 ms 52 ms 212.58.251.43
10 52 ms 51 ms 59 ms www.bbc.co.uk [212.58.244.140]

Trace complete.

In reply to a post by aramsay:

This is with Xilo; not sure if it's different for different providers.

Yes it could very well be, depending on where the relevant realm is routed.

Matt

It should be the same for anyone reselling the C&W service via Murphx. Those who take it as an L2TP service an rebadge it will route differently.

Such peering agreements are generally intended to ensure fastest delivery of traffic to those routes rather than seeking some kind of general distribution of traffic overall which would not necessarily result in a network that can be managed either in terms of traffic flows or costs.