SG.GS: PeeringDB fix list

AS24482 · peeringdb.com/net/3608

PeeringDB

17 things to fix in SG.GS's PeeringDB record, from what its exchanges publish: 1 to add, 16 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on SG.GS'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 SG.GS'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.

Correct these entries (16)

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. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 203.159.68.176: set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.170.211: set Speed to 100000 (100G) (now 2000).
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 80.81.193.18: set Speed to 100000 (100G) (now 50000).
  4. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.210.188: set Speed to 100000 (100G) (now 2000).
  5. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.131.39: set Speed to 10000 (10G) (now 1000).
  6. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.208.194: set Speed to 100000 (100G) (now 2000).
  7. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 178.216.40.194: set Speed to 20000 (20G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  8. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 89.46.145.0: set Speed to 20000 (20G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  9. 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, so PeeringDB also suggests this change on the network's PeeringDB page.

  10. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G
    • In the entry with IPv4 195.66.244.69: set Speed to 2000 (2G) (now 1000).
  11. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.72163.223.201.72
    IPv6 address differs2400:efa0::2:4482:12001:df0:a940::2:4482:1
    • In the entry with IPv4 103.121.64.72: set IPv4 to 163.223.201.72 (now 103.121.64.72); set IPv6 to 2001:df0:a940::2:4482:1 (now 2400:efa0::2:4482:1).
  12. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 217.29.66.158: set Speed to 10000 (10G) (now 1000).
  13. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs1G2T
    • In the entry with IPv4 194.68.128.226: set Speed to 2000000 (2T) (now 1000).
  14. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs1G2T
    • In the entry with IPv4 194.68.123.226: set Speed to 2000000 (2T) (now 1000).
  15. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs10G1.25G
    • In the entry with IPv4 185.0.21.39: set Speed to 1250 (1.25G) (now 10000).
  16. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 103.16.102.30: set Speed to 100000 (100G) (now 200000).

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