ixreport

Alibaba: PeeringDB fix list

AS45102 · peeringdb.com/net/6824

PeeringDB

15 things to fix in Alibaba's PeeringDB record, from what its exchanges publish: 3 to add, 9 to correct, 3 to check. As of 2026-10-08 18:53 UTC.

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

  1. 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.

  2. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From 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) São Paulo São Paulo/SP, Brazil · PeeringDB 171From 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 (9)

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 AMS-IX Bangkok Bangkok, Thailand · PeeringDB 4232
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2402:b740:15:388:0:a504:5102:10
    • In the entry with IPv4 103.100.140.120: set IPv6 to 2402:b740:15:388:0:a504:5102:10 (now empty).

    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 Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::b02e:0:1 2001:7f8::b02e:0:2
    • In the entry with IPv4 80.81.194.33: set IPv6 to 2001:7f8::b02e:0:2 (now empty).
    • In the entry with IPv4 80.81.195.60: set IPv6 to 2001:7f8::b02e:0:1 (now empty).
  3. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::137
    • In the entry with IPv4 123.108.9.55: set IPv6 to 2001:7fa:2:5::137 (now empty).

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

  4. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2404:c8:0:a:0:4:5102:1
    Port speed differs10G20G
    • In the entry with IPv4 119.11.184.41: set IPv6 to 2404:c8:0:a:0:4:5102:1 (now empty); set Speed to 20000 (20G) (now 10000).
  5. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::b02e:1 2001:7f8:4::b02e:2
    • In the entry with IPv4 195.66.225.79: set IPv6 to 2001:7f8:4::b02e:1 (now empty).
    • In the entry with IPv4 195.66.227.152: set IPv6 to 2001:7f8:4::b02e:2 (now empty).
  6. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::209:180 2001:7f8:20:101::209:210
    • In the entry with IPv4 195.208.209.180: set IPv6 to 2001:7f8:20:101::209:180 (now empty).
    • In the entry with IPv4 195.208.209.210: set IPv6 to 2001:7f8:20:101::209:210 (now empty).

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

  7. 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::a504:5102:1
    • In the entry with IPv4 193.239.118.179: set IPv6 to 2001:7f8:13::a504:5102: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.

  8. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:de8:12:100::1232001:de8:12:100::123 2001:de8:12:100::127
    • In the entry with IPv4 103.16.102.127: set IPv6 to 2001:de8:12:100::127 (now empty).
  9. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:73::b02e:0:1
    • In the entry with IPv4 185.1.8.47: set IPv6 to 2001:7f8:73::b02e:0:1 (now empty).

Check these entries (3)

In PeeringDB, but on none of the exchange's own lists. If Alibaba has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472Not on its IX-F export or website members list
    IPv4103.162.254.98
    IPv6–
    Speed10000 Mbps (10G)
  2. Malaysia DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474Not on its IX-F export
    IPv4103.119.232.98
    IPv62403:4ac0::b02e:0:1
    Speed10000 Mbps (10G)
  3. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.71
    IPv6–
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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