ixreport

Martin Jahn

AS208434

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

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Martin Jahn's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Martin Jahn'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 (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 KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.189.83.150
    • In the entry with IPv6 2001:7f8:33::a120:8434:1: set IPv4 to 193.189.83.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.

  2. 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.119.123
    • In the entry with IPv6 2001:7f8:13::a520:8434:1: set IPv4 to 193.239.119.123 (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

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

Map

Where Martin Jahn'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 13.1G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States EVIXVIX Fremont, United States 2602:fed2:fff:ffff:6::76 1G 5 routes Both
Switzerland FogIXP Avers, Switzerland 2001:7f8:ca:1:0:20:8434:1 1G Yes Both
Germany FogIXP Frankfurt Frankfurt, Germany 2001:7f8:11c:1:0:20:8434:1 1G Yes PeeringDB
Germany frankonIX Nuremberg, Germany 2001:7f8:15b:1::1:8 10G Yes Both
Germany KleyReX Frankfurt, Germany 2001:7f8:33::a120:8434:1 100M 5 routes Both IPv4 not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 2001:7f8:13::a520:8434:1 Yes Both IPv4 not in PeeringDB

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

These exchanges have a switch in a facility where Martin Jahn lists itself in PeeringDB, but don't have Martin Jahn 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 N-IXNürnberg, Germany 23 Hetzner Online NBG1 (Nuremberg)
United States Global Peer ExchangeWashington, United States 6 Hetzner Online NBG1 (Nuremberg)
Germany STACIXFrankfurt, Germany 5 Hetzner Online NBG1 (Nuremberg)
Facilities (1)

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

Germany Hetzner Online NBG1 (Nuremberg)Nuremberg 1 of 4