Orion Blazej Hess: PeeringDB fix list
AS196776 · peeringdb.com/net/16088
2 things to fix in Orion Blazej Hess'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 Orion Blazej Hess'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 Orion Blazej Hess's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.149.232.252 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 IPv4 address missing from PeeringDB 178.216.41.250 178.216.40.91 178.216.41.250 IPv6 address missing from PeeringDB none 2001:7f8:5b::486 2001:7f8:5b::559 Port speed differs 10G 2 × 20G - In the entry with IPv4 178.216.41.250: set IPv6 to 2001:7f8:5b::486 (now empty); set Speed to 20000 (20G) (now 10000).
- Add an entry: IPv4 178.216.40.91, IPv6 2001:7f8:5b::559, speed 20000 (20G), 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/196776/: 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.