Infinitron Global Communications: PeeringDB fix list

AS14447 · peeringdb.com/net/39598

PeeringDB

3 things to fix in Infinitron Global Communications's PeeringDB record, from what its exchanges publish: 2 to add, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Infinitron Global Communications'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 Infinitron Global Communications'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.84
    IPv62001:504:9e::84
    Speed1000 Mbps (1G)
    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.110
    IPv62001:504:98::110
    Speed1000 Mbps (1G)
    RS peerNot published

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Infinitron Global Communications has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Taiwan NRIX Taipei City, Taiwan · PeeringDB 4299Not on its website members list
    IPv4–
    IPv62001:ded:c000::33
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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