Whitesky Communications AS62887: PeeringDB fix list
AS62887 · peeringdb.com/net/7604
3 things to fix in Whitesky Communications AS62887's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 21:56 UTC.
Make the changes on Whitesky Communications AS62887'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 Whitesky Communications AS62887's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.51.46.126 IPv6 2605:6c00:303:303::126 Speed Not published RS peer Not published
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 × 100G 100G
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Whitesky Communications AS62887 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.53.200.43 IPv6 2001:504:59::43 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/62887/: 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.