ixreport

XINZHAO Net: PeeringDB fix list

AS204463 · peeringdb.com/net/41569

PeeringDB

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

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

  1. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990From its IX-F export and website members list
    IPv4185.1.184.193
    IPv62001:7f8:134::bf
    Speed1000 Mbps (1G)
    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 (2)

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. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone103.158.187.186
    • In the entry with IPv6 2a0f:5707:ffe3::186: set IPv4 to 103.158.187.186 (now empty).

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

  2. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone192.34.27.89
    • Add an entry: IPv4 192.34.27.89, IPv6 –.

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