Gcore: PeeringDB fix list

AS199524 · peeringdb.com/net/5499

PeeringDB

18 things to fix in Gcore's PeeringDB record, from what its exchanges publish: 11 to add, 6 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Gcore'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 (11)

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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.

  2. Ghana Accra Internet Exchange LBG Accra, Ghana · PeeringDB 4259From 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.

  3. Belgium BNIX Brussels, Belgium · PeeringDB 59From its website members list
    IPv4194.53.172.47
    IPv62001:7f8:26::a519:9524:1
    SpeedNot published
    RS peerNot published
  4. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.18
    IPv62001:7f8:9e:0:3:b64:0:1
    Speed400000 Mbps (400G)
    RS peerYes
  5. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.28
    IPv62001:7f8:3d:0:3:b64:0:1
    Speed400000 Mbps (400G)
    RS peerYes
  6. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list

    3 connections, so 3 entries:

    IPv4185.1.208.27
    IPv62001:7f8:44:0:3:b64:0:1
    Speed400000 Mbps (400G)
    RS peerYes
    IPv4185.1.208.6
    IPv62001:7f8:44:0:3:b64:0:2
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4185.1.208.195
    IPv62001:7f8:44:0:3:b64:0:3
    Speed100000 Mbps (100G)
    RS peerYes
  7. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.196
    IPv62001:7f8:d:fe::196
    SpeedNot published
    RS peerYes
  8. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.196
    IPv62001:7f8:d:fb::196
    SpeedNot published
    RS peerYes
  9. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.196
    IPv62001:7f8:d:ff::196
    SpeedNot published
    RS peerYes
  10. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.196
    IPv62001:7f8:d:fc::196
    SpeedNot published
    RS peerYes
  11. Canada TorIX Toronto, Canada · PeeringDB 24From its website members list
    IPv4206.108.35.173
    IPv62001:504:1a::35:173
    SpeedNot published
    RS peerNot published

Correct these entries (6)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G800G + 400G
    • In the entry with IPv4 80.81.194.82: set Speed to 800000 (800G) (now 400000).
  2. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 206.82.104.246: set Speed to 200000 (200G) (now 100000).
  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  4. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 196.216.148.89: set Speed to 100000 (100G) (now 10000).
  5. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 103.16.102.193: set Speed to 200000 (200G) (now 100000).
  6. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 185.1.8.114: set Speed to 100000 (100G) (now 40000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Gcore 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.56
    IPv62001:7f8:7a::19:9524: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/199524/: 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.