Gestor de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial: PeeringDB fix list

AS37529 · peeringdb.com/net/13940

PeeringDB

3 things to fix in Gestor de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Gestor de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial'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 Gestor de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From 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 (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. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.192.234: set Speed to 10000 (10G) (now 1000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 195.66.237.244: set Speed to 5000 (5G) (now 10000).

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