ixreport

SpringIX Route Servers: PeeringDB fix list

AS63203 · peeringdb.com/net/23808

PeeringDB

One thing to fix in SpringIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on SpringIX Route Servers'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 SpringIX Springfield, MO, United States · PeeringDB 3195
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export149.112.4.253 149.112.4.254149.112.4.254
    IPv6 address in PeeringDB, not in the export2001:504:100::253 2001:504:100::2542001:504:100::254
    Port speed differs2 × 10G10G
    • The entry with IPv4 149.112.4.253, IPv6 2001:504:100::253 isn't in the export: delete it if that connection is gone.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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