Maxnet Digital: PeeringDB fix list
AS141275 · peeringdb.com/net/26932
3 things to fix in Maxnet Digital's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Maxnet Digital'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 (1)
On the exchange's own member list, but not in Maxnet Digital's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 Port speed differs 20G 40G - In the entry with IPv4 45.120.248.93: set Speed to 40000 (40G) (now 20000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Maxnet Digital has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.27.171.178 IPv6 2401:7500:fff6::18b Speed 5000 Mbps (5G)
From ixreport.com/net/141275/: 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.