Exabytes Enterprise MY02: PeeringDB fix list
AS55405 · peeringdb.com/net/18165
2 things to fix in Exabytes Enterprise MY02'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 Exabytes Enterprise MY02'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 differs 2001:df6:480::55 2001:df6:480::d86d:0:1 Port speed differs 1G 20G - In the entry with IPv4 103.162.254.55: set IPv6 to 2001:df6:480::d86d:0:1 (now 2001:df6:480::55); set Speed to 20000 (20G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Exabytes Enterprise MY02 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 218.100.44.125 IPv6 2001:de8:10::39 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/55405/: 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.