ixreport

Beehive Telephone Company: PeeringDB fix list

AS32890 · peeringdb.com/net/20696

PeeringDB

2 things to fix in Beehive Telephone Company's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Beehive Telephone Company'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 (2)

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 SLIX - Salt Lake City Internet Exchange Salt Lake City, United States · PeeringDB 829
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 149.112.13.38: set Speed to 10000 (10G) (now 100000).

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

  2. United States SUPRnet Saint George, United States · PeeringDB 363
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv4 206.53.201.33: set Speed to 1000 (1G) (now 100000).

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