Defaultroute DMCC

AS60440

Defaultroute Limited

Website PeeringDB

0Exchanges

0On an exchange's list, not in PeeringDB

0In PeeringDB, not on the exchange's list

EnterpriseType

OpenPeering policy

0Using the route servers

2Facilities in PeeringDB

Tools: Where can I peer with Defaultroute DMCC? · Where should Defaultroute DMCC peer next?

Exchanges over time

This chart fills in as daily counts build up.

Exchanges


Not on any exchange right now.

Not on any exchange right now.

Exchanges in its buildings that it isn't on (12)

These exchanges have a switch in a facility where Defaultroute DMCC lists itself in PeeringDB, but don't have Defaultroute DMCC as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.


LINX LON1London, United Kingdom	837	Telehouse - London (Docklands North)
GNM-IXAmsterdam, Netherlands	756	Telehouse - London (Docklands North)
NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands	668	Telehouse - London (Docklands North)
LINX LON2London, United Kingdom	319	Telehouse - London (Docklands North)
LONAPLondon, United Kingdom	314	Telehouse - London (Docklands North)
NetIXSofia, Bulgaria	201	Telehouse - London (Docklands North)
nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France	153	Telehouse - London (Docklands North)
LINX ManchesterManchester, United Kingdom	137	Teledata Manchester - Delta House
Kent Internet Exchange PointKent, United Kingdom	88	Telehouse - London (Docklands North)
Balcan-IXBucharest, Romania	29	Telehouse - London (Docklands North)
EURASIA-IX.NETIstanbul, Türkiye	7	Telehouse - London (Docklands North)
Global Peer ExchangeWashington, United States	7	Telehouse - London (Docklands North)