ixreport

Paul Bunyan Communications: PeeringDB fix list

AS14371 · peeringdb.com/net/3134

PeeringDB

2 things to fix in Paul Bunyan Communications's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.

Make the changes on Paul Bunyan Communications'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 MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G200G + 100G
    • In the entry with IPv4 206.108.255.120: set Speed to 200000 (200G) (now 100000).

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

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 TP-IXghost Duluth, United States · PeeringDB 624

    Only one outside network

    IPv4206.223.125.33
    IPv62001:504:29::1e:1
    Speed10000 Mbps (10G)

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