LG Uplus: PeeringDB fix list

AS3786 · peeringdb.com/net/3932

PeeringDB

5 things to fix in LG Uplus's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 20:58 UTC.

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

  1. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95From 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 (4)

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 × 20G100G + 20G
    • In the entry with IPv4 80.81.194.234: set Speed to 100000 (100G) (now 20000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.66 178.18.236.180178.18.236.10 178.18.236.66 178.18.236.180
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:66 2a03:5f80:4:2::236:1802a03:5f80:4:2::236:10 2a03:5f80:4:2::236:66 2a03:5f80:4:2::236:180
    Port speed differs2 × 10G2 × 100G + 10G
    • In the entry with IPv4 178.18.236.180: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 178.18.236.66: set Speed to 100000 (100G) (now 10000).
    • Add an entry: IPv4 178.18.236.10, IPv6 2a03:5f80:4:2::236:10, speed 10000 (10G), RS peer yes.

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

  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.117.168193.239.117.168 193.239.119.238
    IPv6 address missing from PeeringDB2001:7f8:13::a500:3786:22001:7f8:13::a500:3786:1 2001:7f8:13::a500:3786:2
    • Add an entry: IPv4 193.239.119.238, IPv6 2001:7f8:13::a500:3786:1, RS peer yes.

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

  4. United States SIX Seattle Seattle, United States · PeeringDB 13
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:504:16::eca 2001:504:16::564:eca2001:504:16::eca 2001:504:16::564:0:eca
    • In the entry with IPv4 206.81.82.52: set IPv6 to 2001:504:16::564:0:eca (now 2001:504:16::564:eca).

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

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