HATS NETWORK: PeeringDB fix list
AS203314 · peeringdb.com/net/30755
4 things to fix in HATS NETWORK's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on HATS NETWORK'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 (3)
On the exchange's own member list, but not in HATS NETWORK'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:1a32:1 Speed Not published RS peer Yes -
IPv4 185.0.24.205 IPv6 2001:7f8:aa::205 Speed 10000 Mbps (10G) 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.
-
IPv4 23.154.164.171 IPv6 2602:f429:31::2c Speed 1000 Mbps (1G) 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.
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 10G 1G - In the entry with IPv4 103.158.187.66: set Speed to 1000 (1G) (now 10000).
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/203314/: 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.