e-utp.net
AS56662 · e-utp.net
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.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
IPv4 – IPv6 2001:7f8:d0::dd56:1 Speed Not published RS peer Yes -
IPv4 193.189.82.226 IPv6 2001:7f8:33::a105:6662:1 Speed 100 Mbps (100M) RS peer Yes 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.1.170.139 Port speed differs 1G 10G - 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).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 80.81.196.214 Port speed differs 100M 10G - 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).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.1.210.144 Port speed differs 1G 10G - 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).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.1.208.149 Port speed differs 1G 10G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
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.
| 4b42 Internet Exchange Point Zurich, Switzerland | Not in PeeringDB | ||
| DE-CIX Dusseldorf Düsseldorf, Germany | 1G | Both IPv4 not in PeeringDBSpeed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 100M | Both IPv4 not in PeeringDBSpeed differs | |
| DE-CIX Hamburg Hamburg, Germany | 1G | Both IPv4 not in PeeringDBSpeed differs | |
| DE-CIX Munich Munich, Germany | 1G | Both IPv4 not in PeeringDBSpeed differs | |
| KleyReX Frankfurt, Germany | 100M | Not in PeeringDB | |
| LOCIX DUSSELDORF Dusseldorf, Germany | 1G | PeeringDB | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 1G | PeeringDB | |
| LOCIX NETHERLANDS Meppel, Netherlands | 1G | PeeringDB | |
| Speed-IX Dronten, Netherlands | 1G | Both |
e-utp.net lists no facilities in PeeringDB.