ixreport

GiGstreem: PeeringDB fix list

AS14277 · peeringdb.com/net/29581

PeeringDB

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

Make the changes on GiGstreem'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 (1)

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

  1. United States TPAIX Tampa, United States · PeeringDB 833From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 206.53.202.122: set Speed to 100000 (100G) (now 40000).

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