Intendo: PeeringDB fix list
AS34691 · peeringdb.com/net/22636
4 things to fix in Intendo's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Intendo'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 (4)
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 Port speed differs 1G 10G - In the entry with IPv4 217.29.66.92: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:10::b3:4691 Port speed differs 2 × 1G 10G + 1G - In the entry with IPv4 193.201.29.15: set IPv6 to 2001:7f8:10::b3:4691 (now empty); set Speed to 10000 (10G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:23:ffff::105 - In the entry with IPv4 194.116.96.105: set IPv6 to 2001:7f8:23:ffff::105 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.115.31: set Speed to 10000 (10G) (now 1000).
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/34691/: 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.