ixreport

Belcenter

AS31449 · as31449

8Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
6To fix in PeeringDB
2Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

6 things to fix in Belcenter's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Belcenter'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 (1)

On the exchange's own member list, but not in Belcenter's PeeringDB record. Add one entry per connection with these values.

  1. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.208
    IPv62001:7f8:d:ff::208
    Speed2000 Mbps (2G)
    RS peerYes

Correct these entries (5)

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a503:1449:1
    • In the entry with IPv4 80.249.210.71: set IPv6 to 2001:7f8:1::a503:1449:1 (now empty).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::7ad9:0:1
    Port speed differs200M100G
    • In the entry with IPv4 80.81.195.2: set IPv6 to 2001:7f8::7ad9:0:1 (now empty); set Speed to 100000 (100G) (now 200).
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::7ad9:1
    • In the entry with IPv4 195.66.231.64: set IPv6 to 2001:7f8:4::7ad9:1 (now empty).
  4. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4c::7ad9:1
    • In the entry with IPv4 188.93.170.58: set IPv6 to 2001:7f8:4c::7ad9:1 (now empty).

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

  5. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fe::208
    Port speed differs100M2G
    • In the entry with IPv4 194.68.128.208: set IPv6 to 2001:7f8:d:fe::208 (now empty); set Speed to 2000 (2G) (now 100).

Exchanges over time

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

Map

Where Belcenter'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 5.9G across 8 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.210.71 1G 2 routes Both IPv6 not in PeeringDB
Belgium BNIX Brussels, Belgium 194.53.172.107 2G Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.2 200M 2 routes Both IPv6 not in PeeringDBSpeed differs
France France-IX Paris Paris, France 37.49.236.73 250M Yes PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.231.64 250M 2 routes Both IPv6 not in PeeringDB
Luxembourg LU-CIX Luxembourg, Luxembourg 188.93.170.58 100M Yes Both IPv6 not in PeeringDB
Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden 194.68.128.208 100M 2 routes Both IPv6 not in PeeringDBSpeed differs
Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden 194.68.123.208 2001:7f8:d:ff::208 2G Yes Not in PeeringDB

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

These exchanges have a switch in a facility where Belcenter lists itself in PeeringDB, but don't have Belcenter 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
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 (2)

The buildings Belcenter 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