Alibaba Cloud CDN: PeeringDB fix list

AS24429 · peeringdb.com/net/16535

PeeringDB

32 things to fix in Alibaba Cloud CDN's PeeringDB record, from what its exchanges publish: 6 to add, 22 to correct, 4 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Alibaba Cloud CDN'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 (6)

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

  1. Hungary BIX Budapest, Hungary · PeeringDB 55From its IX-F export
    IPv4193.188.137.80
    IPv62001:7f8:35::2:4429:1
    Speed20000 Mbps (20G)
    RS peerYes
  2. 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.

  3. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export and website members list

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

  4. Kyrgyzstan KG-IX Bishkek Bishkek, Kyrgyzstan · PeeringDB 2145From 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.

  5. Indonesia OMNIIX INDONESIA Batam, Jakarta, Indonesia · PeeringDB 4774From 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.

  6. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4103.16.103.94
    IPv62001:de8:12:100::103:94
    Speed100000 Mbps (100G)
    RS peerNo
    IPv4103.16.103.95
    IPv62001:de8:12:100::103:95
    Speed100000 Mbps (100G)
    RS peerNo

Correct these entries (22)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a502:4429:1 2001:7f8:1::a502:4429:2
    • In the entry with IPv4 80.249.211.9: set IPv6 to 2001:7f8:1::a502:4429:1 (now empty).
    • In the entry with IPv4 80.249.212.33: set IPv6 to 2001:7f8:1::a502:4429:2 (now empty).

    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.

  2. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df0:296::a502:4429:1
    • In the entry with IPv4 103.247.139.20: set IPv6 to 2001:df0:296::a502:4429:1 (now empty).

    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.

  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs400G + 200G + 100G + 30G800G + 200G + 100G + 30G
    • In the entry with IPv4 80.81.196.118: set Speed to 800000 (800G) (now 400000).
  4. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:36::282a:0:2
    • In the entry with IPv4 185.1.47.135: set IPv6 to 2001:7f8:36::282a:0:2 (now empty).
  5. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:678:3ac::135
    • In the entry with IPv4 89.46.144.135: set IPv6 to 2001:678:3ac::135 (now empty).

    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.

  6. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:fdc0::2:4429:1 2401:fdc0::2:4429:2
    • In the entry with IPv4 103.104.19.25: set IPv6 to 2401:fdc0::2:4429:2 (now empty).
    • In the entry with IPv4 103.104.19.64: set IPv6 to 2401:fdc0::2:4429:1 (now empty).

    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.

  7. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:96
    • In the entry with IPv4 178.18.226.96: set IPv6 to 2a03:5f80:4::226:96 (now empty).

    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.

  8. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::32 2001:7fa:2:5::354
    • In the entry with IPv4 123.108.11.68: set IPv6 to 2001:7fa:2:5::354 (now empty).
    • In the entry with IPv4 123.108.8.50: set IPv6 to 2001:7fa:2:5::32 (now empty).

    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.

  9. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.66.227.194195.66.227.101 195.66.227.194
    IPv6 address missing from PeeringDBnone2001:7f8:4::5f6d:1 2001:7f8:4::5f6d:2
    Port speed differs40G100G + 40G
    • In the entry with IPv4 195.66.227.194: set IPv6 to 2001:7f8:4::5f6d:1 (now empty).
    • Add an entry: IPv4 195.66.227.101, IPv6 2001:7f8:4::5f6d:2, speed 100000 (100G), RS peer yes.
  10. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df0:a940::2:4429:1
    • In the entry with IPv4 163.223.201.38: set IPv6 to 2001:df0:a940::2:4429:1 (now empty).
  11. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:30::8c
    • In the entry with IPv4 103.26.71.140: set IPv6 to 2001:dea:0:30::8c (now empty).

    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.

  12. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::2c
    • In the entry with IPv4 103.26.68.44: set IPv6 to 2001:dea:0:10::2c (now empty).

    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.

  13. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:b:100:1d1:a5d2:4429:88
    Port speed differs20G30G
    • In the entry with IPv4 217.29.67.88: set IPv6 to 2001:7f8:b:100:1d1:a5d2:4429:88 (now empty); set Speed to 30000 (30G) (now 20000).
  14. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::208:233
    • In the entry with IPv4 195.208.208.233: set IPv6 to 2001:7f8:20:101::208:233 (now empty).

    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.

  15. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::9:177
    • In the entry with IPv4 196.60.9.177: set IPv6 to 2001:43f8:6d0::9:177 (now empty).

    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.

  16. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fe::28
    • In the entry with IPv4 194.68.128.28: set IPv6 to 2001:7f8:d:fe::28 (now empty).
  17. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fb::28
    • In the entry with IPv4 195.69.119.28: set IPv6 to 2001:7f8:d:fb::28 (now empty).
  18. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:ff::28
    • In the entry with IPv4 194.68.123.28: set IPv6 to 2001:7f8:d:ff::28 (now empty).
  19. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fc::28
    • In the entry with IPv4 195.245.240.28: set IPv6 to 2001:7f8:d:fc::28 (now empty).
  20. 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::a502:4429:1
    • In the entry with IPv4 193.239.118.245: set IPv6 to 2001:7f8:13::a502:4429:1 (now empty).

    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.

  21. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a0f:5707:ffe3::156
    • In the entry with IPv4 103.158.187.156: set IPv6 to 2a0f:5707:ffe3::156 (now empty).

    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.

  22. Italy TOP-IX Turin, Italy · PeeringDB 115
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:23:ffff::102
    • In the entry with IPv4 194.116.96.102: set IPv6 to 2001:7f8:23:ffff::102 (now empty).

    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.

Check these entries (4)

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

  1. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277Not on its IX-F export or website members list
    IPv4185.1.192.225
    IPv6–
    Speed10000 Mbps (10G)
  2. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.122
    IPv6–
    Speed20000 Mbps (20G)

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

  3. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95Not on its website members list
    IPv4210.173.177.6
    IPv62001:7fa:7:1:0:2:4429:1
    Speed100000 Mbps (100G)

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

  4. Malaysia MyIX Kuala Lumpur, Malaysia · PeeringDB 250Not on its website members list
    IPv4218.100.44.32
    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/24429/: 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.