AWBROADBAND: PeeringDB fix list

AS63296 · peeringdb.com/net/24722

PeeringDB

2 things to fix in AWBROADBAND's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on AWBROADBAND'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 DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:61::f740:0:1
    Port speed differs30G100G
    • In the entry with IPv4 206.53.202.95: set IPv6 to 2001:504:61::f740:0:1 (now empty); set Speed to 100000 (100G) (now 30000).

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. United States FD-IX - Amarilloghost Amarillo, United States · PeeringDB 4534

    Only one outside network

    IPv4149.112.107.6
    IPv6–
    Speed10000 Mbps (10G)

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