ixreport

Stefan Dunkel

AS48646 · Stefan6 Network

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
8Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

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

Make the changes on Stefan Dunkel'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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.170.254: set Speed to 10000 (10G) (now 1000).

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 Stefan Dunkel'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 32.1G, at the 6 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.182 2001:7f8:d0::be06:1 Yes Both
Switzerland CHIX-CH Frauenfeld, Switzerland 185.1.59.140 2001:7f8:cc:333::140 1G Yes PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.254 2001:7f8:9e::be06:0:1 1G Down Both Speed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.243 2001:7f8::be06:0:1 10G Down Both
Germany KleyReX Frankfurt, Germany 193.189.82.190 2001:7f8:33::a04:8646:1 100M 4 routes Both
Germany LOCIX DUSSELDORF Dusseldorf, Germany 185.1.155.3 2a0c:b641:701:0:a5:48:646:1 10G Yes PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 185.1.166.111 2001:7f8:f2:e1:0:a124:8646:1 10G Yes PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.118.143 2001:7f8:13::a504:8646:1 Yes Both

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

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

Facilities (2)

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

Germany WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf 3 of 6
Germany iNTERWERK RechenzentrumFrankfurt 2 of 3