NETMAR: PeeringDB fix list
AS50121 · peeringdb.com/net/13734
2 things to fix in NETMAR's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on NETMAR'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 NETMAR's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.149.233.82 IPv6 – Speed Not published RS peer Not published 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 IPv6 address missing from PeeringDB none 2001:7f8:5b::454 Port speed differs 2G 10G - In the entry with IPv4 178.216.41.202: set IPv6 to 2001:7f8:5b::454 (now empty); set Speed to 10000 (10G) (now 2000).
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/50121/: 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.