Host Leasing: PeeringDB fix list

AS15280 · peeringdb.com/net/8060

PeeringDB

3 things to fix in Host Leasing'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 Host Leasing'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.

  1. United States FL-IX Miami, United States · PeeringDB 954
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.41.108.66: set Speed to 10000 (10G) (now 100000).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Host Leasing has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States CIX-ATL Atlanta, United States · PeeringDB 1668Not on its IX-F export or website members list
    IPv4206.71.12.66
    IPv62001:504:40:12::1:66
    Speed100000 Mbps (100G)
  2. United States CIX-NoVA Ashburn, Reston, Washington DC, United States · PeeringDB 4796Not on its IX-F export or website members list
    IPv4149.112.69.66
    IPv62001:504:40:69::1:66
    Speed100000 Mbps (100G)

From ixreport.com/net/15280/: 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.