GFiber: PeeringDB fix list

AS16591 · peeringdb.com/net/5063

PeeringDB

4 things to fix in GFiber's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on GFiber's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in GFiber's PeeringDB record. Add one entry per connection with these values.

  1. United States HOUIX Houston, United States · PeeringDB 2835From its IX-F export and website members list
    IPv4206.83.136.77
    IPv62001:504:9e::77
    Speed200000 Mbps (200G)
    RS peerNot published
  2. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.103
    IPv62001:504:98::103
    Speed200000 Mbps (200G)
    RS peerNot published

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 KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs200G400G
    • In the entry with IPv4 206.51.7.30: set Speed to 400000 (400G) (now 200000).
  2. United States SLIX - Salt Lake City Internet Exchange Salt Lake City, United States · PeeringDB 829
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 149.112.13.19: set Speed to 100000 (100G) (now 40000).

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