ByteArk: PeeringDB fix list
AS59238 · peeringdb.com/net/18704
3 things to fix in ByteArk's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on ByteArk'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 ByteArk'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::e766:1 Speed Not published RS peer Yes
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 200M 250M - In the entry with IPv4 103.247.139.77: set Speed to 250 (250M) (now 200).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If ByteArk has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 210.171.225.194 IPv6 2001:de8:8::5:9238:1 Speed 500 Mbps (500M) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/59238/: 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.