Zoho Corp: PeeringDB fix list

AS397849 · peeringdb.com/net/11293

PeeringDB

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

Make the changes on Zoho Corp's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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 SIX Seattle Seattle, United States · PeeringDB 13
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:504:16::6:1219none
    • In the entry with IPv4 206.81.80.107: set IPv6 to (empty) (now 2001:504:16::6:1219).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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