Amarutu Technology Ltd.: PeeringDB fix list
AS206264 · peeringdb.com/net/7809
4 things to fix in Amarutu Technology Ltd.'s PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Amarutu Technology Ltd.'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 20G 800G - In the entry with IPv4 80.81.193.211: set Speed to 800000 (800G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 3 × 100G 2 × 100G 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 100G 12.5G - In the entry with IPv4 185.0.21.65: set Speed to 12500 (12.5G) (now 100000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.1.222.10 185.1.222.10 185.1.223.49 IPv6 address missing from PeeringDB 2001:7f8:b7::a520:6264:1 2001:7f8:b7::a520:6264:1 2001:7f8:b7::a520:6264:2 Port speed differs 100G 2 × 100G - Add an entry: IPv4 185.1.223.49, IPv6 2001:7f8:b7::a520:6264:2, speed 100000 (100G), 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.
From ixreport.com/net/206264/: 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.