Hostrebel, Inc.: PeeringDB fix list
AS211665 · peeringdb.com/net/26258
3 things to fix in Hostrebel, Inc.'s PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Hostrebel, Inc.'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 Hostrebel, Inc.'s PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::3:3ad1:1 Speed Not published RS peer Yes
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 Port speed differs 2 × 10G 4G + 1G - In the entry with IPv4 195.66.228.125: set Speed to 4000 (4G) (now 10000).
- In the entry with IPv4 195.66.228.128: set Speed to 1000 (1G) (now 10000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 5.57.82.224 5.57.82.224 5.57.82.225 IPv6 address missing from PeeringDB 2001:7f8:17::3:3ad1:1 2001:7f8:17::3:3ad1:1 2001:7f8:17::3:3ad1:2 Port speed differs 10G 5G + 1G - In the entry with IPv4 5.57.82.224: set Speed to 1000 (1G) (now 10000).
- Add an entry: IPv4 5.57.82.225, IPv6 2001:7f8:17::3:3ad1:2, speed 5000 (5G), 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/211665/: 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.