Byteplus Pte. Ltd.: PeeringDB fix list
AS150436 · peeringdb.com/net/33739
3 things to fix in Byteplus Pte. Ltd.'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 Byteplus Pte. Ltd.'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 Byteplus Pte. Ltd.'s PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 2 × 200G 2 × 100G - In the entry with IPv4 123.108.11.66: set Speed to 100000 (100G) (now 200000).
- In the entry with IPv4 123.108.11.81: set Speed to 100000 (100G) (now 200000).
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 Byteplus Pte. Ltd. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.16.103.42 IPv6 2001:de8:12:100::103:42 Speed 200000 Mbps (200G) IPv4 103.16.103.69 IPv6 2001:de8:12:100::103:69 Speed 200000 Mbps (200G)
From ixreport.com/net/150436/: 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.