ixreport

BELNET

AS2611

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
3Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in BELNET's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on BELNET'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. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 2G2 × 1G
    • In the entry with IPv4 188.93.170.111: set Speed to 1000 (1G) (now 2000).
    • In the entry with IPv4 188.93.171.111: set Speed to 1000 (1G) (now 2000).

    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

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

Map

Where BELNET'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 304G across 3 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.208.43 2001:7f8:1::a500:2611:1 100G 96 routes Both
Belgium BNIX Brussels, Belgium 194.53.172.65
194.53.172.97
2001:7f8:26::a500:2611:1
2001:7f8:26::a500:2611:2
2 × 100G 432 routes Both
Luxembourg LU-CIX Luxembourg, Luxembourg 188.93.170.111
188.93.171.111
2001:7f8:4c::a33:1
2001:7f8:4c::a33:2
2 × 2G Yes Both Speed differs

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

These exchanges have a switch in a facility where BELNET lists itself in PeeringDB, but don't have BELNET 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 Digital Realty BRU1 - Brussels
Bulgaria NetIXSofia, Bulgaria 204 Level(3) Brussels
Belgium BelgiumIXBrussels, Ghent, Leuven, Antwerp, Hasselt, Belgium 32 Digital Realty BRU1 - Brussels; LCL Brussels (Diegem)
United States Global Peer ExchangeWashington, United States 6 Digital Realty BRU1 - Brussels; LCL Brussels (Diegem)
Facilities (4)

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

Belgium Digital Realty BRU1 - BrusselsBrussels 1 of 4
Belgium LCL Brussels (Diegem)Brussels 1 of 3
Belgium Level(3) BrusselsBrussels 1 of 2
Belgium Penta Infra Brussel BRU01Asse 1 of 1