ixreport

TELEPORT LLC: PeeringDB fix list

AS58310 · peeringdb.com/net/29999

PeeringDB

2 things to fix in TELEPORT LLC's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    3 connections, so 3 entries:

    IPv4178.18.224.44
    IPv62a03:5f80:4::224:44
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.136
    IPv62a03:5f80:4::224:136
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.145
    IPv62a03:5f80:4::224:145
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.208.48
    IPv6–
    SpeedNot published
    RS peerYes

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

From ixreport.com/net/58310/: 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.