ixreport

NU Informationssysteme

AS50050 · NU

NU Informationssysteme GmbH

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
5To fix in PeeringDB
6Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

5 things to fix in NU Informationssysteme's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on NU Informationssysteme'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 (5)

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 BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:19:1::c382:1
    Port speed differs10G2G
    • In the entry with IPv4 193.178.185.83: set IPv6 to 2001:7f8:19:1::c382:1 (now empty); set Speed to 2000 (2G) (now 10000).

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

  2. Germany MegaIX Berlin Berlin, Germany · PeeringDB 209
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:5:0:c382:0:1
    • In the entry with IPv4 194.9.117.3: set IPv6 to 2001:7f8:8:5:0:c382:0:1 (now empty).

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

  3. Germany MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8::c382:0:1
    • In the entry with IPv4 194.146.118.9: set IPv6 to 2001:7f8:8::c382:0:1 (now empty).

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

  4. Germany MegaIX Frankfurt Frankfurt, Germany · PeeringDB 676
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:20:0:c382:0:1
    • In the entry with IPv4 62.69.146.7: set IPv6 to 2001:7f8:8:20:0:c382:0:1 (now empty).

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

  5. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:13::a505:50:1
    • In the entry with IPv4 193.239.116.174: set IPv6 to 2001:7f8:13::a505:50:1 (now empty).

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

Exchanges over time

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

Map

Where NU Informationssysteme'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 50G across 5 exchanges.

Germany BCIX Berlin, Germany 193.178.185.83 10G 13 routes Both IPv6 not in PeeringDBSpeed differs
Germany MegaIX Berlin Berlin, Germany 194.9.117.3 10G Yes Both IPv6 not in PeeringDB
Germany MegaIX Dusseldorf Dusseldorf, Germany 194.146.118.9 10G Yes Both IPv6 not in PeeringDB
Germany MegaIX Frankfurt Frankfurt, Germany 62.69.146.7 10G Yes Both IPv6 not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.116.174 10G Yes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where NU Informationssysteme lists itself in PeeringDB, but don't have NU Informationssysteme 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 Speedbone Berlin
Germany DE-CIX LeipzigLeipzig, Germany 26 Datacenter Leipzig - envia TEL GmbH
Germany Community-IXBerlin, Frankfurt, Germany 25 Speedbone Berlin
Australia ixFabricGlobal, Australia 2 Speedbone Berlin
Facilities (6)

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

Germany Speedbone BerlinBerlin 3 of 6
Germany euNetworks Colocation BerlinBerlin 2 of 2
Germany Datacenter Leipzig - envia TEL GmbHTaucha 0 of 1
Germany Colocation Leipzig Mitte (ZNK) - PŸUR BusinessLeipzig No exchange
Germany euNetworks Colocation LeipzigLeipzig No exchange
Germany EXA Edge DC DresdenDresden No exchange