ixreport

SPEEDYNETPR: PeeringDB fix list

AS62913 · peeringdb.com/net/32919

PeeringDB

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

Make the changes on SPEEDYNETPR'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
    IPv6 address in PeeringDB, not in the export2001:504:40:108::1:191none
    Port speed differs10G100G
    • In the entry with IPv4 206.41.108.191: set IPv6 to (empty) (now 2001:504:40:108::1:191); set Speed to 100000 (100G) (now 10000).

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