ixreport

Lukas Schauer

AS62269 · kurz.pw

4Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
4Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

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

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

  1. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.83.171
    IPv62001:7f8:33::a106:2269:1
    Speed100 Mbps (100M)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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 differs1G200G
    • In the entry with IPv4 185.1.170.153: set Speed to 200000 (200G) (now 1000).

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 Lukas Schauer'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 12.1G across 4 exchanges.

Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.153 2001:7f8:9e::f33d:0:1 1G 2 routes Both Speed differs
Germany KleyReX Frankfurt, Germany 193.189.83.171 2001:7f8:33::a106:2269:1 100M Yes Not in PeeringDB
Germany LOCIX DUSSELDORF Dusseldorf, Germany 185.1.155.79 2a0c:b641:701::6:2269:1 10G Yes PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 185.1.166.135 2001:7f8:f2:e1:0:a162:269:1 1G Yes PeeringDB

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

These exchanges have a switch in a facility where Lukas Schauer lists itself in PeeringDB, but don't have Lukas Schauer 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 (1)

The buildings Lukas Schauer 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