ixreport

Malte Nagel

AS203269

MNAGEL Network

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

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

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in Malte Nagel's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Malte Nagel'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. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.239.117.150
    • In the entry with IPv6 2001:7f8:13::a520:3369:1: set IPv4 to 193.239.117.150 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where Malte Nagel'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

Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 2001:7f8:13::a520:3369:1 Yes Both IPv4 not in PeeringDB

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

These exchanges have a switch in a facility where Malte Nagel lists itself in PeeringDB, but don't have Malte Nagel 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.

Germany DE-CIX FrankfurtFrankfurt, Germany 1,075 Telehouse - Frankfurt
Germany KleyReXFrankfurt, Germany 471 Telehouse - Frankfurt; iNTERWERK Rechenzentrum
Germany LOCIX FRANKFURTFrankfurt am Main, Germany 205 iNTERWERK Rechenzentrum
Germany MegaIX FrankfurtFrankfurt, Germany 114 Telehouse - Frankfurt
Germany ERA-IX FrankfurtFrankfurt, Germany 85 Telehouse - Frankfurt
Germany TievoluIXFrankfurt, Germany 4 iNTERWERK Rechenzentrum
Facilities (2)

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

Germany Telehouse - FrankfurtFrankfurt 1 of 5
Germany iNTERWERK RechenzentrumFrankfurt 0 of 3