ixreport

SMARTNET Germany GmbH: PeeringDB fix list

AS203446 · peeringdb.com/net/30663

PeeringDB

3 things to fix in SMARTNET Germany GmbH's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.

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

  1. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 ERA-IX Frankfurt Frankfurt, Germany · PeeringDB 4630
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:15e::7
    • In the entry with IPv4 185.0.27.7: set IPv6 to 2001:7f8:15e::7 (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 that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Germany SmartIXghost Frankfurt, Germany · PeeringDB 4594

    Only the operator's own networks

    IPv4193.192.12.67
    IPv6–
    Speed200000 Mbps (200G)

From ixreport.com/net/203446/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.