ixreport

tk_telecom_60072: PeeringDB fix list

AS60072

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

AS60072 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

On the exchange's own member list, but not in tk_telecom_60072's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.226.170
    IPv62a03:5f80:4::226:170
    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.184
    IPv62001:7f8:20:101::208:184
    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.

  3. Russia MSK-IX Samara Samara, Russia · PeeringDB 379From its IX-F export
    IPv4193.232.135.41
    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/60072/: 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.