Bytefilter LLC: PeeringDB fix list
AS1002 · peeringdb.com/net/30799
3 things to fix in Bytefilter LLC's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Bytefilter LLC's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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 100G 10G - In the entry with IPv4 206.51.7.210: set Speed to 10000 (10G) (now 100000).
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Bytefilter LLC has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.81.81.201 IPv6 2001:504:16::3ea Speed 10000 Mbps (10G) -
SIX Seattle (Jumbo) Seattle, United States · PeeringDB 1285Not on its IX-F export or website members listIPv4 149.112.97.201 IPv6 2001:504:16:1::3ea Speed 10000 Mbps (10G)
From ixreport.com/net/1002/: 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.