Cable Forum - View Single Post - Virgin Media to possibly peer with LINX (London Internet Exchange)

Ignitionnet · 16-09-2008, 09:34

Morning superkey, start of NMC shift?

You might want to check regarding DTAG being a peer, they don't seem to know that they peer with VM looking at the communities that are set in the routes they hold for you guys, they list you as a transit customer.

Community: 3320:1826 3320:2010 3320:9010

3320:1826 Imported in Great Britain
3320:2010 Imported in Europe
3320:9010 Imported from a customer

As opposed to:

3320:9020 Imported from a peerr

Their mis-spelling not mine

I checked on 5462 as well - same thing, no sign of a peering with DTAG and as far as DTAG are concerned has been moved behind 5089.

If VM have multiple peerings with OVH they're either down or were broken by the AS migration, which is far from impossible when noting some of VM's internal routing has been broken by the AS migration. Be quite impressive to break a peering to the extent where you prefer a longer AS path but still from what I've seen 5462's external connectivity has also been largely moved behind 5089 even where it's the better paths.

16-09-2008, 09:34	#27
Ignitionnet Inactive Join Date: Jun 2008 Location: Leeds, West Yorkshire Age: 47 Posts: 13,995	Re: Virgin Media to possibly peer with LINX (London Internet Exchange) Morning superkey, start of NMC shift? You might want to check regarding DTAG being a peer, they don't seem to know that they peer with VM looking at the communities that are set in the routes they hold for you guys, they list you as a transit customer. Community: 3320:1826 3320:2010 3320:9010 3320:1826 Imported in Great Britain 3320:2010 Imported in Europe 3320:9010 Imported from a customer As opposed to: 3320:9020 Imported from a peerr Their mis-spelling not mine I checked on 5462 as well - same thing, no sign of a peering with DTAG and as far as DTAG are concerned has been moved behind 5089. If VM have multiple peerings with OVH they're either down or were broken by the AS migration, which is far from impossible when noting some of VM's internal routing has been broken by the AS migration. Be quite impressive to break a peering to the extent where you prefer a longer AS path but still from what I've seen 5462's external connectivity has also been largely moved behind 5089 even where it's the better paths.