ixreport

GALAXYGATE: PeeringDB fix list

AS397031 · peeringdb.com/net/18218

PeeringDB

2 things to fix in GALAXYGATE's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on GALAXYGATE'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 GALAXYGATE's PeeringDB record. Add one entry per connection with these values.

  1. United States FCIX Fremont, United States · PeeringDB 2163From its website members list
    IPv4206.80.238.139
    IPv62001:504:91::139
    SpeedNot published
    RS peerNot published

Check these entries (1)

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

  1. United States NYIIX New York New York, United States · PeeringDB 14Not on its website members list
    IPv4198.32.160.143
    IPv62001:504:1::a539:7031:1
    Speed20000 Mbps (20G)

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

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