V4LESS
AS215250 · Tobias Fiebig
Tobias Fiebig
Tools: Where can I peer with V4LESS? · Where should V4LESS peer next? · Compare V4LESS with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
10 things to fix in V4LESS's PeeringDB record, from what its exchanges publish: 10 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on V4LESS'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 (10)
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 80.249.213.30 - In the entry with IPv6 2001:7f8:1:0:a500:21:5250:1: set IPv4 to 80.249.213.30 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:9e:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8::3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:3d:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:3f:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:a0:0:3:48d2:0:2: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:36:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:7f8:44:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 200G - In the entry with IPv6 2001:504:36:0:3:48d2:0:1: set Speed to 200000 (200G) (now 100).
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.239.119.167 - In the entry with IPv6 2001:7f8:13::a521:5250:1: set IPv4 to 193.239.119.167 (now empty).
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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 35 |
| Nov 18, 2026 | 35 |
| Nov 17, 2026 | 35 |
| Nov 16, 2026 | 35 |
| Nov 15, 2026 | 35 |
| Nov 14, 2026 | 35 |
| Nov 13, 2026 | 35 |
| Nov 12, 2026 | 35 |
| Nov 11, 2026 | 35 |
| Nov 10, 2026 | 35 |
| Nov 9, 2026 | 35 |
| Nov 8, 2026 | 35 |
| Nov 7, 2026 | 35 |
| Nov 6, 2026 | 35 |
| Nov 5, 2026 | 35 |
| Nov 4, 2026 | 35 |
| Nov 3, 2026 | 35 |
| Nov 2, 2026 | 35 |
| Nov 1, 2026 | 35 |
| Oct 31, 2026 | 35 |
| Oct 30, 2026 | 35 |
| Oct 29, 2026 | 35 |
| Oct 28, 2026 | 35 |
| Oct 27, 2026 | 35 |
| Oct 26, 2026 | 35 |
| Oct 25, 2026 | 35 |
| Oct 24, 2026 | 35 |
| Oct 23, 2026 | 35 |
| Oct 22, 2026 | 35 |
| Oct 21, 2026 | 35 |
| Oct 20, 2026 | 35 |
| Oct 19, 2026 | 35 |
| Oct 18, 2026 | 35 |
| Oct 17, 2026 | 35 |
| Oct 16, 2026 | 35 |
| Oct 15, 2026 | 35 |
| Oct 14, 2026 | 35 |
| Oct 13, 2026 | 35 |
| Oct 12, 2026 | 35 |
| Oct 11, 2026 | 35 |
| Oct 10, 2026 | 35 |
| Oct 9, 2026 | 35 |
| Oct 8, 2026 | 35 |
| Oct 7, 2026 | 35 |
| Oct 6, 2026 | 35 |
| Oct 5, 2026 | 35 |
| Oct 4, 2026 | 35 |
| Oct 3, 2026 | 35 |
Map
Where V4LESS'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.
| AMS-IX Amsterdam, Netherlands | 10G | Both IPv4 not in PeeringDB | |
| BCIX Berlin, Germany | 1G | Both | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 100M | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 100M | Both Speed differs | |
| DE-CIX Hamburg Hamburg, Germany | 100M | Both Speed differs | |
| DE-CIX Istanbul Istanbul, Türkiye | 100M | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 100M | Both Speed differs | |
| DE-CIX Marseille Marseille, France | 100M | Both Speed differs | |
| DE-CIX Munich Munich, Germany | 100M | Both Speed differs | |
| DE-CIX New York New York, United States | 100M | Both Speed differs | |
| FogIXP Avers, Switzerland | 1G | Both | |
| France-IX Lille Lille, France | 200M | PeeringDB | |
| France-IX Paris Paris, France | 200M | PeeringDB | |
| ixFabric - BogataVIX Bogata, Colombia | 1G | PeeringDB | |
| ixFabric - Buenos AiresVIX Buenos Aires, Argentina | 1G | PeeringDB | |
| ixFabric - ChicagoVIX Chicago, United States | 1G | PeeringDB | |
| ixFabric - FortalezaVIX Fortaleza, Brazil | 1G | PeeringDB | |
| ixFabric - Kansas Kansas, United States | 1G | PeeringDB | |
| ixFabric - LimaVIX Lima, Peru | 1G | PeeringDB | |
| ixFabric - Los AngelesVIX Los Angeles, United States | 1G | PeeringDB | |
| ixFabric - Mexico CityVIX Mexico City, Mexico | 1G | PeeringDB | |
| ixFabric - MiamiVIX Miami, United States | 1G | PeeringDB | |
| ixFabric - Moscow Moscow, Russia | 1G | PeeringDB | |
| ixFabric - Panama CityVIX Panama City, Panama | 1G | PeeringDB | |
| ixFabric - QuitoVIX Quito, Ecuador | 1G | PeeringDB | |
| ixFabric - Rio de JaneiroVIX Rio de Janeiro, Brazil | 1G | PeeringDB | |
| ixFabric - Rome Rome, Italy | 1G | PeeringDB | |
| ixFabric - SantiagoVIX Santiago, Chile | 1G | PeeringDB | |
| ixFabric - Sao PauloVIX Sao Paulo, Brazil | 1G | PeeringDB | |
| ixFabric - Tel-Aviv Tel-Aviv, Israel | 1G | PeeringDB | |
| LOCIX DUSSELDORF Dusseldorf, Germany | 1G | PeeringDB | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 1G | PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Both IPv4 not in PeeringDB | ||
| TREX Tampere Tampere, Finland | Both | ||
| TREX turku Turku, Finland | Both |
These exchanges have a switch in a facility where V4LESS lists itself in PeeringDB, but don't have V4LESS 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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| MegaIX DusseldorfDusseldorf, Germany | 97 | |
| MegaIX BerlinBerlin, Germany | 43 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| Global Peer ExchangeWashington, United States | 6 | |
| SBIX DusseldorfDusseldorf, Germany | 5 | |
| ixFabricGlobal, Australia | 2 |
Facilities (3)
The buildings V4LESS lists in PeeringDB, and how many of the exchanges in each it's on.
| Speedbone BerlinBerlin | 2 of 6 | |
| WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf | 3 of 6 | |
| Cogent AmsterdamHalfweg | 0 of 1 |