Ostrog.NET: PeeringDB fix list
AS30813 · peeringdb.com/net/11139
2 things to fix in Ostrog.NET's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Ostrog.NET'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 (2)
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 178.216.40.56 178.216.40.56 178.216.40.113 IPv6 address missing from PeeringDB 2001:7f8:5b::56 2001:7f8:5b::56 2001:7f8:5b::113 Port speed differs 40G 2 × 40G - Add an entry: IPv4 178.216.40.113, IPv6 2001:7f8:5b::113, speed 40000 (40G), 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 89.46.144.153 89.46.144.153 89.46.144.178 IPv6 address missing from PeeringDB 2001:678:3ac::153 2001:678:3ac::107 2001:678:3ac::153 Port speed differs 5G 2 × 40G - In the entry with IPv4 89.46.144.153: set Speed to 40000 (40G) (now 5000).
- Add an entry: IPv4 89.46.144.178, IPv6 2001:678:3ac::107, speed 40000 (40G), 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/30813/: 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.