ixreport

e-utp.net

AS56662 · e-utp.net

10Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Non-ProfitType
OpenPeering policy
10Using the route servers
6To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with e-utp.net? · Where should e-utp.net peer next? · Compare e-utp.net with another network

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

PeeringDB fix list Printable page · CSV

6 things to fix in e-utp.net's PeeringDB record, from what its exchanges publish: 2 to add, 4 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on e-utp.net'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 (2)

On the exchange's own member list, but not in e-utp.net's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::dd56:1
    SpeedNot published
    RS peerYes
  2. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4193.189.82.226
    IPv62001:7f8:33::a105:6662: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 (4)

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
    IPv4 address missing from PeeringDBnone185.1.170.139
    Port speed differs1G10G
    • In the entry with IPv6 2001:7f8:9e::dd56:0:1: set IPv4 to 185.1.170.139 (now empty); set Speed to 10000 (10G) (now 1000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone80.81.196.214
    Port speed differs100M10G
    • In the entry with IPv6 2001:7f8::dd56:0:1: set IPv4 to 80.81.196.214 (now empty); set Speed to 10000 (10G) (now 100).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.210.144
    Port speed differs1G10G
    • In the entry with IPv6 2001:7f8:3d::dd56:0:1: set IPv4 to 185.1.210.144 (now empty); set Speed to 10000 (10G) (now 1000).
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.208.149
    Port speed differs1G10G
    • In the entry with IPv6 2001:7f8:44::dd56:0:1: set IPv4 to 185.1.208.149 (now empty); set Speed to 10000 (10G) (now 1000).

Exchanges over time

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

Map

Where e-utp.net'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 7.2G, at the 9 of 10 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::dd56:1 Yes Not in PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 2001:7f8:9e::dd56:0:1 1G 4 routes Both IPv4 not in PeeringDBSpeed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 2001:7f8::dd56:0:1 100M 4 routes Both IPv4 not in PeeringDBSpeed differs
Germany DE-CIX Hamburg Hamburg, Germany 2001:7f8:3d::dd56:0:1 1G 4 routes Both IPv4 not in PeeringDBSpeed differs
Germany DE-CIX Munich Munich, Germany 2001:7f8:44::dd56:0:1 1G 4 routes Both IPv4 not in PeeringDBSpeed differs
Germany KleyReX Frankfurt, Germany 193.189.82.226 2001:7f8:33::a105:6662:1 100M Yes Not in PeeringDB
Germany LOCIX DUSSELDORF Dusseldorf, Germany 2a0c:b641:701:0:a5:56:662:1 1G Yes PeeringDB
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 2001:7f8:f2:e1:0:a105:6662:1 1G Yes PeeringDB
Netherlands LOCIX NETHERLANDS Meppel, Netherlands 185.1.138.27 2a0c:b641:700::5:6662 1G Yes PeeringDB
Netherlands Speed-IX Dronten, Netherlands 2001:7f8:b7::a55:6662:1 1G 4 routes Both

e-utp.net lists no facilities in PeeringDB.