ixreport

Minnesota Brain Injury Alliance: PeeringDB fix list

AS19418 · peeringdb.com/net/31996

PeeringDB

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

Make the changes on Minnesota Brain Injury Alliance'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 SIX Seattle Seattle, United States · PeeringDB 13
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone206.81.80.146
    • In the entry with IPv6 2001:504:16::4bda: set IPv4 to 206.81.80.146 (now empty).

    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/19418/: 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.