Alibaba
AS45102
Alibaba Group
Tools: Where can I peer with Alibaba? · Where should Alibaba peer next? · Compare Alibaba with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
14 things to fix in Alibaba's PeeringDB record, from what its exchanges publish: 2 to add, 9 to correct, 3 to check. As of 2026-11-19 12:40 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 (2)
On the exchange's own member list, but not in Alibaba's PeeringDB record. Add one entry per connection with these values.
-
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.
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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2402: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2404:c8:0:a:0:4:5102:1 Port speed differs 10G 20G - 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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.239.118.179 193.239.118.179 193.239.118.233 193.239.119.25 IPv6 address missing from PeeringDB none 2001:7f8:13::a504:5102:1 2001:7f8:13::a504:5102:2 2001:7f8:13::a504:5102:3 - In the entry with IPv4 193.239.118.179: set IPv6 to 2001:7f8:13::a504:5102:1 (now empty).
- Add an entry: IPv4 193.239.119.25, IPv6 2001:7f8:13::a504:5102:2, RS peer yes.
- Add an entry: IPv4 193.239.118.233, IPv6 2001:7f8:13::a504:5102:3, 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB 2001:de8:12:100::123 2001: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).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001: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.
-
IPv4 103.162.254.98 IPv6 – Speed 10000 Mbps (10G) -
DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474Not on its IX-F export
IPv4 103.119.232.98 IPv6 2403:4ac0::b02e:0:1 Speed 10000 Mbps (10G) -
IPv4 210.171.225.71 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 | 47 |
| Nov 18, 2026 | 47 |
| Nov 17, 2026 | 47 |
| Nov 16, 2026 | 47 |
| Nov 15, 2026 | 47 |
| Nov 14, 2026 | 47 |
| Nov 13, 2026 | 47 |
| Nov 12, 2026 | 47 |
| Nov 11, 2026 | 47 |
| Nov 10, 2026 | 47 |
| Nov 9, 2026 | 47 |
| Nov 8, 2026 | 46 |
| Nov 7, 2026 | 46 |
| Nov 6, 2026 | 46 |
| Nov 5, 2026 | 46 |
| Nov 4, 2026 | 47 |
| Nov 3, 2026 | 47 |
| Nov 2, 2026 | 47 |
| Nov 1, 2026 | 47 |
| Oct 31, 2026 | 47 |
| Oct 30, 2026 | 47 |
| Oct 29, 2026 | 47 |
| Oct 28, 2026 | 47 |
| Oct 27, 2026 | 46 |
| Oct 26, 2026 | 46 |
| Oct 25, 2026 | 46 |
| Oct 24, 2026 | 46 |
| Oct 23, 2026 | 46 |
| Oct 22, 2026 | 46 |
| Oct 21, 2026 | 46 |
| Oct 20, 2026 | 47 |
| Oct 19, 2026 | 47 |
| Oct 18, 2026 | 47 |
| Oct 17, 2026 | 47 |
| Oct 16, 2026 | 47 |
| Oct 15, 2026 | 47 |
| Oct 14, 2026 | 47 |
| Oct 13, 2026 | 47 |
| Oct 12, 2026 | 47 |
| Oct 11, 2026 | 47 |
| Oct 10, 2026 | 47 |
| Oct 9, 2026 | 47 |
| Oct 8, 2026 | 47 |
| Oct 7, 2026 | 47 |
| Oct 6, 2026 | 47 |
| Oct 5, 2026 | 47 |
| Oct 4, 2026 | 47 |
| Oct 3, 2026 | 46 |
Map
Where Alibaba'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.
| AIX Tapos, Depok, Indonesia | 100G | Both | |
| AMS-IX Bangkok Bangkok, Thailand | 10G | Both IPv6 not in PeeringDB | |
| BBIX Hong Kong Hong Kong, Hong Kong | 2 × 100G | PeeringDB | |
| BBIX Manila Manila, Philippines | 100G | PeeringDB | |
| BBIX Singapore Singapore, Singapore | 200G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 2 × 300G | Both | |
| BIX Jakarta Jakarta, Indonesia | 10G | PeeringDB | |
| center3 IX Jeddah Jeddah, Saudi Arabia | 2 × 10G | PeeringDB | |
| CIX-ATL Atlanta, United States | 2 × 100G | Both | |
| DCI Indonesia DCI-IX Bekasi, Indonesia | 100G | PeeringDB | |
| DE-CIX ASEAN Singapore, Singapore | 10G | PeeringDB only | |
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 300G | Both IPv6 not in PeeringDB | |
| DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia | 10G | Both | |
| DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 10G | PeeringDB only | |
| DE-CIX Mumbai Mumbai, India | Website list only | ||
| Digital Edge EPIX Jakarta Jakarta, Indonesia | 100G | PeeringDB | |
| EdgeNXT Jakarta, Indonesia | 100G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 2 × 300G | PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 2 × 300G | PeeringDB | |
| Equinix Palo Alto Palo Alto, United States | 100G | PeeringDB | |
| Equinix San Jose San Jose, United States | 2 × 200G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 400G | PeeringDB | |
| ERA-IX Amsterdam Amsterdam, Netherlands | Website list only | ||
| ERA-IX Frankfurt Frankfurt, Germany | 100G | Both | |
| ESpanix Madrid Lower LAN Madrid, Spain | 10G | PeeringDB | |
| France-IX Paris Paris, France | 100G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 10G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 2 × 300G | Both | |
| IIX-Jakarta Jakarta, Indonesia | 10G | Both IPv6 not in PeeringDB | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 100G | PeeringDB only | |
| JKT-IX Jakarta, Indonesia | 10G | Both IPv6 not in PeeringDBSpeed differs | |
| JPIX TOKYO Tokyo, Japan | 100G | PeeringDB only | |
| JPNAP Tokyo Tokyo, Japan | 2 × 200G | PeeringDB | |
| JTIX (Thailand) Nonthaburi, Thailand | 10G | PeeringDB | |
| KINX Seoul, South Korea | 2 × 10G | PeeringDB | |
| LINX LON1 London, United Kingdom | 2 × 10G | Both IPv6 not in PeeringDB | |
| LONAP London, United Kingdom | 10G | Both | |
| MSK-IX Moscow Moscow, Russia | 2 × 10G | Both IPv6 not in PeeringDB | |
| MyIX Kuala Lumpur, Malaysia | 100G | Both | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| OpenIXP / NiCE Indonesia, Indonesia | 10G | PeeringDB | |
| SAIX Saudi Arabia Riyadh Riyadh, Saudi Arabia | 100G | Both | |
| SGIX Singapore, Singapore | 2 × 300G | Both IPv6 not in PeeringDB | |
| THAILAND IX (TH-IX) Bangkok, Thailand | 10G | Both | |
| TorIX Toronto, Canada | 10G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 10G | Both IPv6 not in PeeringDB | |
| VANIX Vancouver, Canada | 10G | Both |
These exchanges have a switch in a facility where Alibaba lists itself in PeeringDB, but don't have Alibaba 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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| FogIXPAvers, Switzerland | 532 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Equinix ParisParis, France | 239 | |
| NIX.CZPrague, Czechia | 225 | |
| DE-CIX MadridMadrid, Spain | 224 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| CXC JakartaJakarta, Indonesia | 201 | |
| THINX WarsawWarsaw, Poland | 194 | |
| DE-CIX JakartaJakarta, Indonesia | 177 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Equinix TokyoTokyo, Japan | 127 | |
| BIXBudapest, Hungary | 122 | |
| ILIXSurabaya, Indonesia | 122 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| OMNIIX INDONESIABatam, Jakarta, Indonesia | 111 | |
| SFMIXSan Francisco, United States | 100 | |
| BBIX US-WestWest Coast, United States | 87 | |
| BKNIX (Thailand)Bangkok, Thailand | 80 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| NVIXAshburn, United States | 78 | |
| B-IXSofia, Bulgaria | 77 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| IXPlay Global PeersMadrid, Spain | 63 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| ESpanix Madrid Upper LANMadrid, Spain | 57 | |
| LINX NoVAAshburn, Reston, Manassas, United States | 57 | |
| Maharlika IXManila, Philippines | 57 | |
| Any2EastWashington DC, Reston, Boston, New York, Atlanta, United States | 50 | |
| BBIX ThailandBangkok, Thailand | 50 | |
| MegaIX AshburnAshburn, United States | 49 | |
| PyramIXCairo, Egypt | 48 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| PIT MXQueretaro, Mexico | 46 | |
| CENTRO-IXPekanbaru - Jakarta, Indonesia | 39 | |
| CIX-NoVAAshburn, Reston, Washington DC, United States | 34 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| Japan Community IXJapan, Japan | 32 | |
| DE-CIX MexicoMexico City, Mexico | 28 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| nine - six in ParisParis, France | 24 | |
| DIX-IETokyo, Japan | 22 | |
| TRUE-IXBangkok, Thailand | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| IAIXHong Kong, Hong Kong | 20 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| Vitro Internet ExchangePasig, Philippines | 19 | |
| 1-ES FREEMadrid, Spain | 18 | |
| CNI-IXJakarta, Indonesia | 18 | |
| DACS-IX EastWashington DC, United States | 15 | |
| GNM-IX SGSingapore, Singapore | 15 | |
| Japan Community IX - INIXPJapan, Japan | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| Pacific WaveWest Coast, United States | 14 | |
| PCTA-IX LuzonPasig City, Philippines | 14 | |
| CSL Thai-IX MalaysiaBangkok, Thailand | 13 | |
| GPMIXLampung Timur, Indonesia | 13 | |
| PhIXManila, Philippines | 12 | |
| SOXSingapore, Singapore | 12 | |
| AKIXZurich, Switzerland | 11 | |
| KOIXSeoul, South Korea | 9 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| IFORTE XchangeJakarta, Indonesia | 7 | |
| Konek Internet Exchangegeneral santos city, Philippines | 7 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| Ciallo~(∠·ω< )⌒ IX - HKHong Kong, Hong Kong | 4 | |
| GNM-IX USNew York, United States | 4 | |
| TievoluIXFrankfurt, Germany | 4 | |
| SYMPHONY THAI - IX BANGKOK - 1Bangkok, Thailand | 3 | |
| ixFabricGlobal, Australia | 2 |
Facilities (30)
The buildings Alibaba lists in PeeringDB, and how many of the exchanges in each it's on.
Recent changes Search them
- Oct 19, 2026 [PDB] AS45102 Alibaba now in PeeringDB at IX.br (PTT.br) São Paulo
- Oct 6, 2026 [IXF] AS45102 Alibaba dropped from DE-CIX ASEAN's IX-F list (still in PeeringDB)
- Oct 6, 2026 [IXF] AS45102 Alibaba dropped from DE-CIX Malaysia's IX-F list (still in PeeringDB)
- Oct 6, 2026 [WEB] AS45102 Alibaba dropped from DE-CIX ASEAN's website list (still in PeeringDB and on its IX-F list)