ixreport

VeloxServ Communications

AS3170 · VeloxServ, Etheroute

VeloxServ Communications Ltd

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
4Using the route servers
1To fix in PeeringDB
13Facilities in PeeringDB

Tools: Where can I peer with VeloxServ Communications? · Where should VeloxServ Communications peer next? · Compare VeloxServ Communications with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in VeloxServ Communications's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on VeloxServ Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where VeloxServ Communications's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 250G across 4 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.162
178.18.236.214
2a03:5f80:4::226:162
2a03:5f80:4:2::236:214
2 × 100G Yes Both Speed differs
United Kingdom LINX LON1 London, United Kingdom 195.66.227.195 2001:7f8:4::c62:1 20G 442 routes Both
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.88 2001:7f8:4:2::c62:1 10G 673 routes Both
United Kingdom LONAP London, United Kingdom 5.57.82.162 2001:7f8:17::c62:1 20G 448 routes Both

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

These exchanges have a switch in a facility where VeloxServ Communications lists itself in PeeringDB, but don't have VeloxServ Communications 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.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North); Equinix LD8 - London, Docklands; Telehouse - London (Docklands East) and 3 more
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands North); Equinix LD8 - London, Docklands; Telehouse - London (Docklands East) and 3 more
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix LD8 - London, Docklands
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands North); Equinix LD8 - London, Docklands; Telehouse - London (Docklands East) and 2 more
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North); Telehouse - London (Docklands East); Telehouse - London (Docklands West) and 2 more
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Telehouse - London (Docklands North)
United Kingdom Equinix LondonLondon, United Kingdom 53 Equinix LD8 - London, Docklands
Romania Balcan-IXBucharest, Romania 29 Telehouse - London (Docklands North)
United Kingdom RapidIX LON1London, United Kingdom 7 Digital Realty London LON1-3
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North); Equinix LD8 - London, Docklands
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands North); Equinix LD8 - London, Docklands; Telehouse - London (Docklands West) and 1 more
Facilities (13)

The buildings VeloxServ Communications lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Telehouse - London (Docklands North)London 3 of 11
United Kingdom Equinix LD8 - London, DocklandsLondon 2 of 9
United Kingdom Telehouse - London (Docklands West)London 2 of 7
United Kingdom Telehouse - London (Docklands East)London 2 of 6
United Kingdom Digital Realty London LON1-3London 2 of 5
United Kingdom Telehouse - London (Docklands North Two)London 2 of 5
United Kingdom Telehouse - London (Docklands South)London 1 of 3
United Kingdom Pulsant Manchester NW-1Manchester 1 of 2
United Kingdom Teledata Manchester - Delta HouseManchester 1 of 1
United Kingdom VeloxServ DC1 - WolverhamptonWolverhampton No exchange
United Kingdom VeloxServ DC2 - WolverhamptonWolverhampton No exchange
United Kingdom VeloxServ DC3 - RedditchRedditch No exchange
United Kingdom VeloxServ Wolverhampton CentralWolverhampton No exchange