ixreport

beON

AS212582

beON consult GmbH

2Exchanges, of which 1 VIX
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with beON? · Where should beON peer next? · Compare beON 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 beON's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 18:41 UTC.

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If beON has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.196.167
    IPv62001:7f8::3:3e66:0:1
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where beON'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 10.1G across 2 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.167 2001:7f8::3:3e66:0:1 10G Yes PeeringDB only
Egypt PyramIXVIX Cairo, Egypt 2a0e:46c4:102::212:582:1 100M Yes Both

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

These exchanges have a switch in a facility where beON lists itself in PeeringDB, but don't have beON 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 EMC Home of Data MUC I/II - MuCon-X
Germany DE-CIX MunichMunich, Germany 207 EMC Home of Data MUC I/II - MuCon-X
Germany MegaIX MunichMunich, Germany 35 EMC Home of Data MUC I/II - MuCon-X
Facilities (1)

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

Germany EMC Home of Data MUC I/II - MuCon-XMunich 0 of 3