CityLink ISP: PeeringDB fix list

AS47236 · peeringdb.com/net/14827

PeeringDB

One thing to fix in CityLink ISP's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

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

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

    4 connections, so 4 entries:

    IPv4178.18.225.208
    IPv62a03:5f80:4::225:208
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.12
    IPv62a03:5f80:4::225:12
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.169
    IPv62a03:5f80:4::226:169
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.161
    IPv62a03:5f80:4::224:161
    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.

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