Cato Networks AS138627: PeeringDB fix list
AS138627 · peeringdb.com/net/21084
2 things to fix in Cato Networks AS138627's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Cato Networks AS138627'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:73:0:2:1d83:0:1 IPv4 address in PeeringDB, not in the export 185.1.8.79 185.1.8.146 185.1.8.79 Port speed differs 10G + 6G 200G - The entry with IPv4 185.1.8.146, IPv6 – isn't in the export: delete it if that connection is gone.
- In the entry with IPv4 185.1.8.79: set IPv6 to 2001:7f8:73:0:2:1d83:0:1 (now empty); set Speed to 200000 (200G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Cato Networks AS138627 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.15.43 IPv6 – Speed 2000 Mbps (2G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/138627/: 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.