Arpitel: PeeringDB fix list
AS42764 · peeringdb.com/net/20906
3 things to fix in Arpitel's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Arpitel'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 (2)
On the exchange's own member list, but not in Arpitel's PeeringDB record. Add one entry per connection with these values.
-
IPv4 217.29.67.40 IPv6 2001:7f8:b:100:1d1:a5d4:2764:40 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 193.201.28.187 IPv6 2001:7f8:10::4:2764 Speed 10000 Mbps (10G) RS peer Yes 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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 217.29.67.40 is AS204366 MU Network 217.29.67.40 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/42764/: 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.