ixreport

Netzwerge

AS199938

Netzwerge GmbH

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

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

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

PeeringDB fix list Printable page · CSV

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

Make the changes on Netzwerge'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 (8)

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. Denmark DE-CIX Copenhagen Copenhagen, Denmark · PeeringDB 4043
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.0.4.1: set Speed to 10000 (10G) (now 1000).
  2. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.170.79: set Speed to 10000 (10G) (now 1000).
  3. Denmark DE-CIX Esbjerg Esbjerg, Denmark · PeeringDB 4069
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.0.17.2: set Speed to 10000 (10G) (now 1000).
  4. Finland DE-CIX Helsinki Helsinki, Finland · PeeringDB 4044
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.0.5.2: set Speed to 10000 (10G) (now 1000).
  5. Norway DE-CIX Kristiansand Kristiansand, Norway · PeeringDB 4042
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.0.6.3: set Speed to 10000 (10G) (now 1000).
  6. Germany DE-CIX Leipzig Leipzig, Germany · PeeringDB 4004
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.245.17: set Speed to 10000 (10G) (now 1000).
  7. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.208.87: set Speed to 10000 (10G) (now 1000).
  8. Norway DE-CIX Oslo Oslo, Norway · PeeringDB 4041
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.0.7.1: set Speed to 10000 (10G) (now 1000).

Exchanges over time

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

Map

Where Netzwerge'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 40G across 12 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.211.237 2001:7f8:1:0:a500:19:9938:1 2G 24 routes Both
Denmark DE-CIX Copenhagen Copenhagen, Denmark 185.0.4.1 2001:7f8:139:0:3:d02:0:1 1G 24 routes Both Speed differs
Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.170.79 2001:7f8:9e:0:3:d02:0:1 1G 24 routes Both Speed differs
Denmark DE-CIX Esbjerg Esbjerg, Denmark 185.0.17.2 2001:7f8:143:0:3:d02:0:1 1G 24 routes Both Speed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.248 2001:7f8::3:d0:0:1 10G 24 routes Both
Germany DE-CIX Hamburg Hamburg, Germany 185.1.210.92 2001:7f8:3d:0:3:d02:0:1 10G 24 routes Both
Finland DE-CIX Helsinki Helsinki, Finland 185.0.5.2 2001:7f8:13a:0:3:d02:0:1 1G 24 routes Both Speed differs
Norway DE-CIX Kristiansand Kristiansand, Norway 185.0.6.3 2001:7f8:13b:0:3:d02:0:1 1G 24 routes Both Speed differs
Germany DE-CIX Leipzig Leipzig, Germany 185.1.245.17 2001:7f8:df:0:3:d02:0:1 1G 24 routes Both Speed differs
Germany DE-CIX Munich Munich, Germany 185.1.208.87 2001:7f8:44:0:3:d02:0:1 1G 24 routes Both Speed differs
Norway DE-CIX Oslo Oslo, Norway 185.0.7.1 2001:7f8:13c:0:3:d02:0:1 1G 24 routes Both Speed differs
Germany MegaIX Hamburg Hamburg, Germany 193.42.155.49 2001:7f8:8:10:3:d02:0:1 10G Yes Both

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

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

Netherlands GNM-IXAmsterdam, Netherlands 741 GlobalConnect Hamburg (HAM2)
Germany Community-IXBerlin, Frankfurt, Germany 25 Portus/IPHH HH2 (Wendenstrasse 408)
Facilities (3)

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

Germany GlobalConnect Hamburg (HAM2)Hamburg 2 of 3
Germany Portus/IPHH HH2 (Wendenstrasse 408)Hamburg 2 of 3
Germany GlobalConnect Hamburg (HAM3)Hamburg No exchange