ixreport

GNX: PeeringDB fix list

AS42156 · peeringdb.com/net/22706

PeeringDB

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

Make the changes on GNX'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 (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 Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G + 4G
    • In the entry with IPv4 195.66.231.126: set Speed to 4000 (4G) (now 10000).

Check these entries (1)

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

  1. United Arab Emirates SH-IX Fujairah, United Arab Emirates · PeeringDB 866Not on its website members list
    IPv4185.1.15.55
    IPv62001:7f8:7a::4:2156:1
    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/42156/: 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.