ixreport

Chen Xinyu: PeeringDB fix list

AS151673 · peeringdb.com/net/33991

PeeringDB

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

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

  1. United Kingdom Kent Internet Exchange Point Kent, United Kingdom · PeeringDB 4316From its IX-F export
    IPv4185.0.24.204
    IPv62001:7f8:aa::204
    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.

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. United States CXIX - Great Lakes NewYork, United States · PeeringDB 4721
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone33.0.0.29
    • In the entry with IPv6 2a0f:7803:fc60:aaaa::1516:73: set IPv4 to 33.0.0.29 (now empty).

    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/151673/: 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.