ixreport

komro

AS29413 · komro GmbH

komro GmbH

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on komro'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 komro's PeeringDB record. Add one entry per connection with these values.

  1. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members list
    IPv4185.0.21.16
    IPv62001:7f8:7f::c:16
    Speed12500 Mbps (12.5G)
    RS peerYes

Correct these entries (2)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 80.81.195.66: set Speed to 100000 (100G) (now 50000).
  2. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 185.1.208.75: set Speed to 100000 (100G) (now 50000).

Exchanges over time

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

Map

Where komro'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 117.5G across 4 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.66 2001:7f8::72e5:0:1 50G 17 routes Both Speed differs
Germany DE-CIX Munich Munich, Germany 185.1.208.75 2001:7f8:44::72e5:0:1 50G 17 routes Both Speed differs
Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia 185.0.21.16 2001:7f8:7f::c:16 12.5G Yes Not in PeeringDB
Austria SAIX Salzburg, Austria 185.1.43.39 2001:7f8:11::39 5G Yes PeeringDB

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

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

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

Germany EMC Home of Data MUC I/II - MuCon-XMunich 1 of 3
Germany noris network datacenter.de MUC5Aschheim 1 of 1