Servicepipe: PeeringDB fix list

AS201706

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

AS201706 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 Servicepipe's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.192.216
    IPv62001:7f8::3:13ea:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.209.18
    IPv62001:7f8:20:101::209:18
    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 Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export
    IPv4193.232.87.77
    IPv62001:7f8:20:401::87:77
    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/201706/: 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.