BGP.Tools Route Collector
AS212232 · BGP.Tools
Ben Cartwright-Cox
Tools: Where can I peer with BGP.Tools Route Collector? · Where should BGP.Tools Route Collector peer next? · Compare BGP.Tools Route Collector with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
54 things to fix in BGP.Tools Route Collector's PeeringDB record, from what its exchanges publish: 4 to add, 30 to correct, 15 to check, 5 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.
Make the changes on BGP.Tools Route Collector's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (4)
On the exchange's own member list, but not in BGP.Tools Route Collector's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 149.112.50.61 IPv6 2001:504:125:e1::61 Speed 100 Mbps (100M) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 – IPv6 2001:7f8:1d:4:0:3:3d08:1 Speed Not published RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 – IPv6 2001:7f8:1d:7:0:3:3d08:1 Speed Not published RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (30)
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 Port speed differs 100M 10G - In the entry with IPv4 185.1.30.11: set Speed to 10000 (10G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 149.112.134.7: set Speed to 10000 (10G) (now 1000).
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 1G - In the entry with IPv4 185.1.119.45: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 149.112.11.45: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 206.53.202.92: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.170.248: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 80.81.196.188: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.210.207: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.48.42: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.245.7: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.131.58: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.192.139: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.47.63: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.208.119: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 206.82.105.4: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 185.1.46.1: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 149.112.27.25: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 206.53.137.2: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.160.247: set Speed to 10000 (10G) (now 1000).
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 1G 10G - In the entry with IPv4 103.142.153.26: set Speed to 10000 (10G) (now 1000).
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 100G 1M - In the entry with IPv4 218.100.54.6: set Speed to 1 (1M) (now 100000).
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 100G 1M - In the entry with IPv4 218.100.76.6: set Speed to 1 (1M) (now 100000).
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 100G 1M - In the entry with IPv4 218.100.54.141: set Speed to 1 (1M) (now 100000).
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 100G 1M - In the entry with IPv4 218.100.78.23: set Speed to 1 (1M) (now 100000).
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 100G 1M - In the entry with IPv4 27.106.192.14: set Speed to 1 (1M) (now 100000).
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 100G 200G - In the entry with IPv4 218.100.52.5: set Speed to 200000 (200G) (now 100000).
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 1G 4G - In the entry with IPv4 196.60.124.31: set Speed to 4000 (4G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 4G - In the entry with IPv4 196.60.114.52: set Speed to 4000 (4G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 212.91.0.32: set Speed to 100000 (100G) (now 1000).
- Add an entry: IPv4 212.91.0.32, IPv6 –, speed 100000 (100G).
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 1G 100G - In the entry with IPv4 194.116.96.252: set Speed to 100000 (100G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (15)
In PeeringDB, but on none of the exchange's own lists. If BGP.Tools Route Collector has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.71.10.4 IPv6 2001:504:45:10::4 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 185.1.121.118 IPv6 2001:7f8:cb:dcbb::18 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 195.66.236.149 IPv6 2001:7f8:4:1:0:3:3d08:1 Speed 2000 Mbps (2G) -
IPv4 194.68.130.146 IPv6 2001:7f8:d:100::146 Speed 100 Mbps (100M) -
IPv4 185.1.230.73 IPv6 2001:7f8:122::73 Speed 100 Mbps (100M) -
IPv4 185.1.230.146 IPv6 2001:7f8:122:8000::146 Speed 100 Mbps (100M) -
IPv4 194.68.131.76 IPv6 2001:7f8:d:400::76 Speed 100 Mbps (100M) -
IPv4 194.153.157.5 IPv6 2001:7f8:d:500::5 Speed 1000 Mbps (1G) -
IPv4 194.153.157.69 IPv6 2001:7f8:d:501::69 Speed 1000 Mbps (1G) -
IPv4 194.68.128.146 IPv6 2001:7f8:d:fe::146 Speed 100 Mbps (100M) -
IPv4 195.69.119.146 IPv6 2001:7f8:d:fb::146 Speed 100 Mbps (100M) -
IPv4 194.68.123.146 IPv6 2001:7f8:d:ff::146 Speed 100 Mbps (100M) -
IPv4 195.245.240.146 IPv6 2001:7f8:d:fc::146 Speed 100 Mbps (100M) -
IPv4 194.68.133.146 IPv6 2001:7f8:d:300::146 Speed 100 Mbps (100M) -
IPv4 206.126.235.37 IPv6 2001:504:33::31 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges that look shut down (5)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 101.203.75.13 IPv6 2403:c780:7200:b075:0:21:2232:1 Speed 100 Mbps (100M) -
Only one outside network
IPv4 101.203.73.13 IPv6 2403:c780:7200:b073:0:21:2232:1 Speed 100 Mbps (100M) -
Only one outside network
IPv4 101.203.76.15 IPv6 2403:c780:7200:b076:0:21:2232:1 Speed 100 Mbps (100M) -
Only one outside network
IPv4 194.59.191.6 IPv6 2001:7f8:8:2::6 Speed 100 Mbps (100M) -
Only one outside network
IPv4 206.53.169.70 IPv6 2606:a980:0:f::6 Speed 100 Mbps (100M)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 149 |
| Nov 18, 2026 | 149 |
| Nov 17, 2026 | 149 |
| Nov 16, 2026 | 149 |
| Nov 15, 2026 | 149 |
| Nov 14, 2026 | 149 |
| Nov 13, 2026 | 149 |
| Nov 12, 2026 | 149 |
| Nov 11, 2026 | 149 |
| Nov 10, 2026 | 149 |
| Nov 9, 2026 | 149 |
| Nov 8, 2026 | 149 |
| Nov 7, 2026 | 149 |
| Nov 6, 2026 | 149 |
| Nov 5, 2026 | 149 |
| Nov 4, 2026 | 149 |
| Nov 3, 2026 | 149 |
| Nov 2, 2026 | 149 |
| Nov 1, 2026 | 148 |
| Oct 31, 2026 | 148 |
| Oct 30, 2026 | 148 |
| Oct 29, 2026 | 148 |
| Oct 28, 2026 | 148 |
| Oct 27, 2026 | 148 |
| Oct 26, 2026 | 148 |
| Oct 25, 2026 | 148 |
| Oct 24, 2026 | 147 |
| Oct 23, 2026 | 147 |
| Oct 22, 2026 | 148 |
| Oct 21, 2026 | 148 |
| Oct 20, 2026 | 148 |
| Oct 19, 2026 | 148 |
| Oct 18, 2026 | 148 |
| Oct 17, 2026 | 148 |
| Oct 16, 2026 | 148 |
| Oct 15, 2026 | 148 |
| Oct 14, 2026 | 148 |
| Oct 13, 2026 | 148 |
| Oct 12, 2026 | 148 |
| Oct 11, 2026 | 148 |
| Oct 10, 2026 | 148 |
| Oct 9, 2026 | 148 |
| Oct 8, 2026 | 148 |
| Oct 7, 2026 | 148 |
| Oct 6, 2026 | 148 |
| Oct 5, 2026 | 148 |
| Oct 4, 2026 | 148 |
| Oct 3, 2026 | 148 |
Map
Where BGP.Tools Route Collector'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.
| 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 1G | Both | |
| 1-NL FREE Amsterdam, Netherlands | 10G | PeeringDB | |
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| B-IX Sofia, Bulgaria | 100M | Both Speed differs | |
| BBIX Amsterdam Amsterdam, Netherlands | 100M | PeeringDB | |
| BBIX Chicagoghost Chicago, United States | 100M | PeeringDB | |
| BBIX Dallasghost Dallas, United States | 100M | PeeringDB | |
| BBIX Londonghost London, United Kingdom | 100M | PeeringDB | |
| BBIX Singapore Singapore, Singapore | 100M | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 100M | Both | |
| BBIX US-West West Coast, United States | 100M | PeeringDB | |
| BCIX Berlin, Germany | 1G | Both | |
| BIX.BG Sofia, Bulgaria | 100M | Both | |
| BNIX Brussels, Belgium | 1G | Both | |
| BreizhIX Rennes, France | 1G | Both | |
| CANIX Montreal Montreal, Canada | 10G | Both | |
| CANIX Ottawa Ottawa / Gatineau, Canada | 10G | Both | |
| CANIX Toronto Toronto, Canada | 1G | Both Speed differs | |
| Central Oregon Internet Exchange Bend, United States | 1G | Both | |
| CINX Cape Town, South Africa | 10G | Both | |
| CRIX San Jose, Costa Rica | 1G | Both | |
| DE-CIX Barcelona Barcelona, Spain | 100M | Both Speed differs | |
| DE-CIX Chicago Chicago, United States | 100M | Both Speed differs | |
| DE-CIX Dallas Dallas, United States | 100M | Both Speed differs | |
| 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 Leipzig Leipzig, Germany | 100M | Both Speed differs | |
| DE-CIX Lisbon Lisbon, Portugal | 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 | |
| DE-CIX Palermo Palermo, Italy | 100M | Both Speed differs | |
| DE-CIX Phoenix Phoenix, United States | 100M | Both Speed differs | |
| DE-CIX Richmond Ashland, United States | 100M | Both Speed differs | |
| DINX Durban, South Africa | 10G | Both | |
| EdgeIX - Adelaide Adelaide, Australia | 1G | PeeringDB | |
| EdgeIX - Auckland Auckland, New Zealand | 1G | PeeringDB | |
| EdgeIX - Brisbane Brisbane, Australia | 1G | PeeringDB | |
| EdgeIX - Melbourne Melbourne, Australia | 1G | PeeringDB | |
| EdgeIX - Perth Perth, Australia | 1G | PeeringDB | |
| EdgeIX - Sydney Sydney, Australia | 1G | Both | |
| EuroRhine-IX Strasbourg, France | 1G | Both | |
| FD-IX - Indianapolis Indianapolis, Indiana, United States | 1G | Both | |
| FD-IX - St. Louis St. Louis, MO, United States | 1G | PeeringDB only | |
| FIXO Oslo, Norway | 1G | Both | |
| France-IX AURA Lyon and Grenoble, France | 1G | PeeringDB | |
| France-IX Lille Lille, France | 1G | PeeringDB | |
| France-IX Marseille Marseille, France | 1G | PeeringDB | |
| France-IX Paris Paris, France | 100M | PeeringDB | |
| France-IX Toulouse Toulouse, France | 1G | PeeringDB | |
| frankonIX Nuremberg, Germany | Website list only | ||
| Frys-IX Fryslân, Netherlands | 1G | Both Speed differs | |
| GetaFIX Cebu Cebu, Philippines | 1G | PeeringDB | |
| GetaFIX Davao Davao, Philippines | 1G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 1G | PeeringDB | |
| GraniteIX Salt Lake City, UT, United States | 10G | PeeringDB | |
| Guam IX Tamuning, Guam | 1G | Both Speed differs | |
| IndyIX Indianapolis, United States | 1G | Both | |
| INEX LAN1 Dublin, Ireland | 1G | Both | |
| INEX LAN2 Dublin, Ireland | 1G | Both | |
| INTERIX Amsterdam, Netherlands | 10G | Both | |
| InterLAN-IX Bucharest, Romania | 1G | Both | |
| IRAQ-IXP Baghdad, Iraq | 1G | PeeringDB | |
| IX Australia Adelaide (SA-IX) Adelaide, Australia | 100G | Both Speed differs | |
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 100G | Both Speed differs | |
| IX Australia Canberra (ACT-IX) Canberra, Australia | 100G | Both Speed differs | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 100G | Both Speed differs | |
| IX Australia Perth (WA-IX) Perth, Australia | 100G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 100G | Both Speed differs | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 1G | PeeringDB only | |
| IXP.mk Skopje, North Macedonia | 1G | PeeringDB only | |
| JINX Johannesburg, South Africa | 10G | Both | |
| Lillix Lille, France | 1G | PeeringDB | |
| LINX LON1 London, United Kingdom | 1G | Both | |
| LINX LON2 London, United Kingdom | 2G | PeeringDB only | |
| LINX Mombasa Mombasa, Kenya | 1G | Both Speed differs | |
| LINX Nairobi Nairobi, Kenya | 1G | Both Speed differs | |
| LONAP London, United Kingdom | 1G | Both | |
| LU-CIX Luxembourg, Luxembourg | 100M | Both | |
| MegaIX Adelaide Adelaide, Australia | 100M | Both | |
| MegaIX Ashburn Ashburn, United States | 100M | Both | |
| MegaIX Atlanta Atlanta, United States | 100M | Both | |
| MegaIX Auckland Auckland, New Zealand | 100M | Both | |
| MegaIX Bay Area San Francisco, United States | 100M | Both | |
| MegaIX Berlin Berlin, Germany | 100M | Both | |
| MegaIX Brisbane Brisbane, Australia | 100M | Both | |
| MegaIX Charlotte Charlotte, United States | 100M | Both | |
| MegaIX Chicago Chicago, United States | 100M | Both | |
| MegaIX Dallas Dallas, United States | 100M | Both | |
| MegaIX Denver Denver, United States | 100M | Both | |
| MegaIX Dublinghost Dublin, Ireland | 100M | PeeringDB | |
| MegaIX Dusseldorf Dusseldorf, Germany | 100M | Both | |
| MegaIX Frankfurt Frankfurt, Germany | 100M | Both | |
| MegaIX Hamburg Hamburg, Germany | 100M | Both | |
| MegaIX Houstonghost Houston, United States | 100M | PeeringDB | |
| MegaIX Las Vegas Las Vegas, United States | 100M | Both | |
| MegaIX Los Angeles Los Angeles, United States | 100M | Both | |
| MegaIX Melbourne Melbourne, Australia | 100M | Both | |
| MegaIX Miami Miami, United States | 100M | Both | |
| MegaIX Munich Munich, Germany | 100M | Both | |
| MegaIX New York New York, United States | 100M | Both | |
| MegaIX Osaka Osaka, Japan | 100M | PeeringDB | |
| MegaIX Perth Perth, Australia | 100M | Both | |
| MegaIX Seattle Seattle, United States | 100M | Both | |
| MegaIX Singapore Singapore, Singapore | 100M | Both | |
| MegaIX Sofia Sofia, Bulgaria | 100M | Both | |
| MegaIX Sydney Sydney, Australia | 100M | Both | |
| MegaIX Toronto Toronto, Canada | 100M | Both | |
| MIX-IT Milan, Italy | 10G | Both | |
| MSK-IX Moscow Moscow, Russia | 100M | Both | |
| Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark | 100M | Both | |
| Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark | 100M | Both | |
| Netnod Gothenburg -- MTU1500 Gothenburg, Sweden | 100M | PeeringDB only | |
| Netnod Helsinki BLUE -- MTU9K Helsinki, Finland | 100M | PeeringDB only | |
| Netnod Helsinki GREEN -- MTU9K Helsinki, Finland | 100M | PeeringDB only | |
| Netnod Lulea -- MTU9K Lulea, Sweden | 100M | PeeringDB only | |
| Netnod Oslo BLUE -- MTU9K Oslo, Norway | 1G | PeeringDB only | |
| Netnod Oslo GREEN -- MTU9K Oslo, Norway | 1G | PeeringDB only | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 100M | PeeringDB only | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | 100M | PeeringDB only | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 100M | PeeringDB only | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | 100M | PeeringDB only | |
| Netnod Sundsvall -- MTU1500 Sundsvall / Gavle, Sweden | 100M | PeeringDB only | |
| nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 10G | Both | |
| NIX.CZ Prague, Czechia | 1G | Both | |
| NIX.SK Bratislava, Slovakia | 1G | Both | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 100M | Both | |
| NMBINX Gqeberha, South Africa | 10G | Both | |
| OmahaIX Omaha, United States | 1G | PeeringDB only | |
| ONIX Toronto, Canada | 100M | Not in PeeringDB | |
| OpenIX Beirut Beirut, Lebanon | 1G | Both | |
| PatagoniaIX Punta Arenas, Chile | 1G | Both | |
| PIT-IX Pittsburgh, United States | 10G | Both | |
| RomandIX Lausanne, Switzerland | 100M | PeeringDB | |
| SFMIX San Francisco, United States | 10G | Both | |
| SIX.SK Bratislava, Slovakia | 1G | Both | |
| SONIX Stockholm Stockholm, Sweden | 10G | Both | |
| SOX Serbia Belgrade/Serbia, Serbia | 1G | PeeringDB | |
| STUIX Taipei City, Taiwan | 1G | Both | |
| Stuttgart-IX Stuttgart, Germany | 1G | Both | |
| THINX Warsaw Warsaw, Poland | 1G | Both Speed differs | |
| TOP-IX Turin, Italy | 1G | Both Speed differs | |
| TREX Tampere Tampere, Finland | Not in PeeringDB | ||
| TREX turku Turku, Finland | Not in PeeringDB | ||
| TurkIX Sofia Sofia, Bulgaria | 10G | Both | |
| YXEIX Saskatoon, Canada | 1G | Both |
These exchanges have a switch in a facility where BGP.Tools Route Collector lists itself in PeeringDB, but don't have BGP.Tools Route Collector 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 | |
| FogIXPAvers, Switzerland | 532 | |
| Speed-IXDronten, Netherlands | 289 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| NetIXSofia, Bulgaria | 204 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| PyramIXCairo, Egypt | 48 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| Clue-IXAmsterdam, Netherlands | 36 | |
| Asteroid AmsterdamAmsterdam, Netherlands | 27 | |
| RegPEXAnkara, Türkiye | 19 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| RapidIX LON1London, United Kingdom | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Noord-IXLeeuwarden, Netherlands | 4 |
Facilities (3)
The buildings BGP.Tools Route Collector lists in PeeringDB, and how many of the exchanges in each it's on.
| NIKHEF AmsterdamAmsterdam | 7 of 28 | |
| Digital Realty London LON1-3London | 3 of 5 | |
| Pfalzkom DCRN IIMutterstadt | 1 of 1 |
Recent changes Search them
- Nov 12, 2026 [PDB] AS212232 BGP.Tools Route Collector now in PeeringDB at TurkIX Sofia
- Nov 12, 2026 [PDB] AS212232 BGP.Tools Route Collector no longer in PeeringDB at TurkIX Sofia (still on its IX-F list and on its website's members list)
- Nov 12, 2026 [PDB] AS212232 BGP.Tools Route Collector now in PeeringDB at TurkIX Sofia
- Oct 13, 2026 [WEB] AS212232 BGP.Tools Route Collector now on Guam IX's website list
- Oct 13, 2026 [WEB] AS212232 BGP.Tools Route Collector now on TurkIX Sofia's website list
- Oct 8, 2026 [WEB] AS212232 BGP.Tools Route Collector dropped from LINX LON2's website list (still in PeeringDB)
- Oct 8, 2026 [IXF] AS212232 BGP.Tools Route Collector dropped from LINX LON2's IX-F list (still in PeeringDB and on its website's members list)