Alibaba Cloud CDN
AS24429 · Taobao/Tmall/Alipay/Youku/Lazada/AliExpress/UCweb
Tools: Where can I peer with Alibaba Cloud CDN? · Where should Alibaba Cloud CDN peer next? · Compare Alibaba Cloud CDN with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
30 things to fix in Alibaba Cloud CDN's PeeringDB record, from what its exchanges publish: 6 to add, 21 to correct, 3 to check. As of 2026-11-19 12:40 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.
-
IPv4 193.188.137.80 IPv6 2001:7f8:35::2:4429:1 Speed 20000 Mbps (20G) RS peer Yes -
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
2 connections, so 2 entries:
IPv4 103.16.103.94 IPv6 2001:de8:12:100::103:94 Speed 300000 Mbps (300G) RS peer No IPv4 103.16.103.95 IPv6 2001:de8:12:100::103:95 Speed 300000 Mbps (300G) RS peer No
Correct these entries (21)
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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has Port speed differs 400G + 200G + 100G + 30G 1.2T + 200G + 100G + 30G - In the entry with IPv4 80.81.196.118: set Speed to 1200000 (1.2T) (now 400000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a03: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.66.227.194 195.66.227.101 195.66.227.194 IPv6 address missing from PeeringDB none 2001:7f8:4::5f6d:1 2001:7f8:4::5f6d:2 Port speed differs 40G 100G + 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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).
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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:b:100:1d1:a5d2:4429:88 Port speed differs 20G 30G - 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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:fe::28 - In the entry with IPv4 194.68.128.28: set IPv6 to 2001:7f8:d:fe::28 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:fb::28 - In the entry with IPv4 195.69.119.28: set IPv6 to 2001:7f8:d:fb::28 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:ff::28 - In the entry with IPv4 194.68.123.28: set IPv6 to 2001:7f8:d:ff::28 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:fc::28 - In the entry with IPv4 195.245.240.28: set IPv6 to 2001:7f8:d:fc::28 (now empty).
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a0f: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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 (3)
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.
-
IPv4 185.1.192.225 IPv6 – Speed 10000 Mbps (10G) -
IPv4 210.171.225.122 IPv6 – Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 218.100.44.32 IPv6 – Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 61 |
| Nov 18, 2026 | 60 |
| Nov 17, 2026 | 60 |
| Nov 16, 2026 | 60 |
| Nov 15, 2026 | 60 |
| Nov 14, 2026 | 60 |
| Nov 13, 2026 | 60 |
| Nov 12, 2026 | 60 |
| Nov 11, 2026 | 60 |
| Nov 10, 2026 | 60 |
| Nov 9, 2026 | 60 |
| Nov 8, 2026 | 60 |
| Nov 7, 2026 | 60 |
| Nov 6, 2026 | 60 |
| Nov 5, 2026 | 60 |
| Nov 4, 2026 | 60 |
| Nov 3, 2026 | 60 |
| Nov 2, 2026 | 60 |
| Nov 1, 2026 | 60 |
| Oct 31, 2026 | 60 |
| Oct 30, 2026 | 60 |
| Oct 29, 2026 | 60 |
| Oct 28, 2026 | 60 |
| Oct 27, 2026 | 60 |
| Oct 26, 2026 | 60 |
| Oct 25, 2026 | 59 |
| Oct 24, 2026 | 59 |
| Oct 23, 2026 | 59 |
| Oct 22, 2026 | 59 |
| Oct 21, 2026 | 60 |
| Oct 20, 2026 | 61 |
| Oct 19, 2026 | 61 |
| Oct 18, 2026 | 61 |
| Oct 17, 2026 | 61 |
| Oct 16, 2026 | 61 |
| Oct 15, 2026 | 61 |
| Oct 14, 2026 | 61 |
| Oct 13, 2026 | 61 |
| Oct 12, 2026 | 61 |
| Oct 11, 2026 | 60 |
| Oct 10, 2026 | 60 |
| Oct 9, 2026 | 60 |
| Oct 8, 2026 | 60 |
| Oct 7, 2026 | 60 |
| Oct 6, 2026 | 60 |
| Oct 5, 2026 | 60 |
| Oct 4, 2026 | 60 |
| Oct 3, 2026 | 60 |
In the last 30 days Alibaba Cloud CDN joined 1 exchange and left 0. Growing networks
Joined
- France-IX Marseille Marseille Nov 19, 2026 PeeringDB only
Map
Where Alibaba Cloud CDN's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| 1-DE FREE Frankfurt, Germany | 100G | PeeringDB | |
| 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 100G | Both | |
| AMS-IX Amsterdam, Netherlands | 100G + 20G | Both IPv6 not in PeeringDB | |
| AMS-IX Hong Kong Hong Kong, Hong Kong | 20G | Both IPv6 not in PeeringDB | |
| BBIX Manila Manila, Philippines | 100G | PeeringDB | |
| BBIX Osaka Osaka, Japan | 40G | PeeringDB | |
| BBIX Thailand Bangkok, Thailand | 20G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 200G | Both | |
| BIX Budapest, Hungary | 20G | Not in PeeringDB | |
| center3 IX Jeddah Jeddah, Saudi Arabia | 2 × 500G | PeeringDB | |
| center3 IX Riyadh Riyadh, Saudi Arabia | 2 × 800G | PeeringDB | |
| CSL Thai-IX Bangkok Bangkok, Thailand | 100G + 20G | PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 400G + 200G + 100G + 30G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 10G | PeeringDB only | |
| DE-CIX Marseille Marseille, France | 20G | Both IPv6 not in PeeringDB | |
| EPIX.Warszawa Warsaw, Poland | 100G | Both IPv6 not in PeeringDB | |
| Equinix Ashburn Ashburn, United States | 40G + 20G | PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 2 × 200G | PeeringDB | |
| Equinix Paris Paris, France | 10G | PeeringDB | |
| Equinix San Jose San Jose, United States | 2 × 20G + 10G | PeeringDB | |
| Equinix Seattle Seattle, United States | 20G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 300G + 2 × 200G | PeeringDB | |
| ESpanix Madrid Lower LAN Madrid, Spain | 20G | PeeringDB | |
| France-IX Marseille Marseille, France | 100G | PeeringDB | |
| France-IX Paris Paris, France | 20G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 2 × 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 20G | Both IPv6 not in PeeringDB | |
| HKIX Hong Kong, Hong Kong | 200G | Both | |
| IAIX Hong Kong, Hong Kong | 10G | PeeringDB | |
| IIX-Jakarta Jakarta, Indonesia | 2 × 100G | Both IPv6 not in PeeringDB | |
| IRAQ-IXP Baghdad, Iraq | 10G | PeeringDB | |
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | Not in PeeringDB | ||
| IXPN Lagos Lagos, Nigeria | 40G | Both | |
| JPIX OSAKA Osaka, Japan | 20G | PeeringDB | |
| JPIX TOKYO Tokyo, Japan | 20G | PeeringDB only | |
| JPNAP Tokyo Tokyo, Japan | 100G | PeeringDB | |
| KG-IX Bishkek Bishkek, Kyrgyzstan | Not in PeeringDB | ||
| LINX LON1 London, United Kingdom | 40G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| Maharlika IX Manila, Philippines | 100G | Both IPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | Both IPv6 not in PeeringDB | ||
| MegaIX Sydney Sydney, Australia | Both IPv6 not in PeeringDB | ||
| MIX-IT Milan, Italy | 20G | Both IPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 100G | Both IPv6 not in PeeringDB | |
| MyIX Kuala Lumpur, Malaysia | 100G | PeeringDB only | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 40G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 20G | Both IPv6 not in PeeringDB | |
| OMNIIX INDONESIA Batam, Jakarta, Indonesia | Not in PeeringDB | ||
| OpenIXP / NiCE Indonesia, Indonesia | 40G | PeeringDB | |
| PIT Bolivia La Paz, Bolivia | 40G | Both | |
| SAIX Saudi Arabia Riyadh Riyadh, Saudi Arabia | 2 × 500G | Both | |
| SGIX Singapore, Singapore | 2 × 300G | Not in PeeringDB | |
| STUIX Taipei City, Taiwan | 10G | Both IPv6 not in PeeringDB | |
| THAILAND IX (TH-IX) Bangkok, Thailand | 100G | Both | |
| TOP-IX Turin, Italy | 10G | Both IPv6 not in PeeringDB | |
| TPIX-TW Taipei/Taiwan, Taiwan | 20G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 100G | Both |
These exchanges have a switch in a facility where Alibaba Cloud CDN lists itself in PeeringDB, but don't have Alibaba Cloud CDN as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| FogIXPAvers, Switzerland | 532 | |
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| AR-IX Cabase - ArgentinaArgentina, Argentina | 372 | |
| SIX SeattleSeattle, United States | 372 | |
| Frys-IXFryslân, Netherlands | 338 | |
| LINX LON2London, United Kingdom | 315 | |
| LONAPLondon, United Kingdom | 311 | |
| DE-CIX New YorkNew York, United States | 281 | |
| IX Australia Sydney (NSW-IX)Sydney, Australia | 270 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| Equinix ChicagoChicago, United States | 257 | |
| PITER-IX Saint-PetersburgSaint-Petersburg, Russia | 246 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| PITER-IX MoscowMoscow, Russia | 243 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| NIX.CZPrague, Czechia | 225 | |
| Equinix SydneySydney, Australia | 219 | |
| JINXJohannesburg, South Africa | 215 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| FL-IXMiami, United States | 199 | |
| THINX WarsawWarsaw, Poland | 194 | |
| NYIIX New YorkNew York, United States | 186 | |
| Equinix MiamiMiami, United States | 175 | |
| PITER-IX FrankfurtFrankfurt, Germany | 172 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| PIT Santiago - PIT ChileSantiago, Chile | 150 | |
| InterLAN-IXBucharest, Romania | 149 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Eurasia Peering IXMoscow, Russia | 136 | |
| Equinix TokyoTokyo, Japan | 127 | |
| MINAP MilanMilan, Italy | 118 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| Equinix New YorkNew York, United States | 106 | |
| IX Australia Melbourne (VIC-IX)Melbourne, Australia | 106 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| SFMIXSan Francisco, United States | 100 | |
| BBIX US-WestWest Coast, United States | 87 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| STHIX - StockholmStockholm, Sweden | 84 | |
| Equinix Los AngelesLos Angeles, United States | 83 | |
| SONIX StockholmStockholm, Sweden | 81 | |
| BKNIX (Thailand)Bangkok, Thailand | 80 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| NVIXAshburn, United States | 78 | |
| BALT-IXVilnius, Lithuania | 77 | |
| EdgeIX - MelbourneMelbourne, Australia | 73 | |
| Equinix Palo AltoPalo Alto, United States | 69 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| W-IXMoscow, Russia | 66 | |
| IXPlay Global PeersMadrid, Spain | 63 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| PIT - Colombia - BogotaBogota, Colombia | 60 | |
| DE-CIX Sao PauloSao Paulo, Brazil | 58 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| SOLIX MTU1500Stockholm, Sweden | 58 | |
| ESpanix Madrid Upper LANMadrid, Spain | 57 | |
| LINX NoVAAshburn, Reston, Manassas, United States | 57 | |
| Equinix MelbourneMelbourne, Australia | 55 | |
| Equinix LondonLondon, United Kingdom | 53 | |
| TYIXTokyo, Japan | 53 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| MegaIX AshburnAshburn, United States | 49 | |
| CXIX - Great LakesNewYork, United States | 46 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| PIT MXQueretaro, Mexico | 46 | |
| DE-CIX Kuala LumpurKuala Lumpur, Malaysia | 45 | |
| ixFabric - New YorkNew York, United States | 44 | |
| RoNIXBucharest, Romania | 43 | |
| CIX-NoVAAshburn, Reston, Washington DC, United States | 34 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| Balcan-IXBucharest, Romania | 29 | |
| DE-CIX MexicoMexico City, Mexico | 28 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| nine - six in ParisParis, France | 24 | |
| PIT - Argentina - Buenos AiresBuenos Aires, Argentina | 23 | |
| FOXTainan, Taiwan | 22 | |
| MegaIX New YorkNew York, United States | 22 | |
| TRUE-IXBangkok, Thailand | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| Chile IX by PIT.netSantiago, Chile | 20 | |
| Equinix Rio de JaneiroRio de Janeiro, Brazil | 20 | |
| EG-IXCairo, Egypt | 19 | |
| Vitro Internet ExchangePasig, Philippines | 19 | |
| 1-ES FREEMadrid, Spain | 18 | |
| SOLIX MTU4470Stockholm, Sweden | 18 | |
| AMS-IX BangkokBangkok, Thailand | 17 | |
| CSL Thai-IX SingaporeBangkok, Thailand | 16 | |
| DE-CIX Rio de JaneiroRio de Janeiro, Brazil | 16 | |
| DACS-IX EastWashington DC, United States | 15 | |
| DE-CIX MalaysiaKuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 15 | |
| MegaIX SeattleSeattle, United States | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| PCTA-IX LuzonPasig City, Philippines | 14 | |
| CSL Thai-IX MalaysiaBangkok, Thailand | 13 | |
| PhIXManila, Philippines | 12 | |
| AKIXZurich, Switzerland | 11 | |
| JTIX (Thailand)Nonthaburi, Thailand | 11 | |
| KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden | 11 | |
| PIT ARBuenos Aires, Argentina | 11 | |
| MegaIX MiamiMiami, United States | 10 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| Konek Internet Exchangegeneral santos city, Philippines | 7 | |
| MegaIX DenverDenver, United States | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| PTT São João M.São João de Meriti, Brazil | 5 | |
| Ciallo~(∠·ω< )⌒ IX - HKHong Kong, Hong Kong | 4 | |
| Equinix DenverDenver, United States | 4 | |
| GNM-IX USNew York, United States | 4 | |
| JINX VoiceJohannesburg, South Africa | 4 | |
| SYMPHONY THAI - IX BANGKOK - 1Bangkok, Thailand | 3 | |
| Any2FloridaMiami/Orlando, United States | 2 | |
| ixFabricGlobal, Australia | 2 |
Facilities (37)
The buildings Alibaba Cloud CDN lists in PeeringDB, and how many of the exchanges in each it's on.
Recent changes Search them
- Nov 19, 2026 [PDB] AS24429 Alibaba Cloud CDN added to France-IX Marseille