Tencent Global: PeeringDB fix list

AS132203 · peeringdb.com/net/5005

PeeringDB

6 things to fix in Tencent Global's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Tencent Global'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 (3)

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

  1. India AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export
    IPv4223.31.200.94
    IPv62001:e48:44:100b:a500:13:2203:1
    Speed10000 Mbps (10G)
    RS peerNo

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

  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From 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. Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (3)

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 differs100G10G
    • In the entry with IPv4 195.66.227.125: set Speed to 10000 (10G) (now 100000).
  2. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:13::a513:2203:1
    • In the entry with IPv4 193.239.118.200: set IPv6 to 2001:7f8:13::a513:2203:1 (now empty).

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

  3. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 200G
    • In the entry with IPv4 103.16.102.164: set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 103.16.103.58: set Speed to 200000 (200G) (now 100000).

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