Axera AS34758: PeeringDB fix list
AS34758 · peeringdb.com/net/5442
2 things to fix in Axera AS34758'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 Axera AS34758'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 IPv4 address missing from PeeringDB 80.81.195.8 80.81.195.8 80.81.195.20 IPv6 address missing from PeeringDB 2001:7f8::87c6:0:2 2001:7f8::87c6:0:1 2001:7f8::87c6:0:2 Port speed differs 10G 800G + 100G - In the entry with IPv4 80.81.195.8: set IPv6 to 2001:7f8::87c6:0:1 (now 2001:7f8::87c6:0:2); set Speed to 100000 (100G) (now 10000).
- Add an entry: IPv4 80.81.195.20, IPv6 2001:7f8::87c6:0:2, speed 800000 (800G), RS peer yes.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Axera AS34758 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.97.43 IPv6 2001:7f8:b9::43:1 Speed 10000 Mbps (10G)
From ixreport.com/net/34758/: 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.