China Unicom Global
AS10099 · China Unicom Global
Tools: Where can I peer with China Unicom Global? · Where should China Unicom Global peer next? · Compare China Unicom Global with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in China Unicom Global's PeeringDB record, from what its exchanges publish: 2 to add, 5 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on China Unicom 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 (2)
On the exchange's own member list, but not in China Unicom Global's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.72.211.141 IPv6 2001:504:13::211:141 Speed Not published RS peer Not published -
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 (5)
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 Port speed differs 100G 10G - In the entry with IPv4 203.159.68.164: set Speed to 10000 (10G) (now 100000).
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 Port speed differs 100G 10G - In the entry with IPv4 195.66.231.13: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 196.60.10.154: set Speed to 10000 (10G) (now 100000).
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 IPv4 address missing from PeeringDB 185.1.226.67 185.1.226.67 185.1.226.149 IPv6 address missing from PeeringDB 2001:67c:29f0::1:99:1 2001:67c:29f0::1:99:1 2001:67c:29f0::1:99:2 - Add an entry: IPv4 185.1.226.149, IPv6 2001:67c:29f0::1:99:2, 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 Port speed differs 100G 10G - In the entry with IPv4 185.1.8.144: set Speed to 10000 (10G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If China Unicom Global 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.15.39 IPv6 2001:7f8:7a::100:99:1 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 | 30 |
| Nov 18, 2026 | 30 |
| Nov 17, 2026 | 30 |
| Nov 16, 2026 | 30 |
| Nov 15, 2026 | 30 |
| Nov 14, 2026 | 30 |
| Nov 13, 2026 | 30 |
| Nov 12, 2026 | 30 |
| Nov 11, 2026 | 30 |
| Nov 10, 2026 | 30 |
| Nov 9, 2026 | 30 |
| Nov 8, 2026 | 30 |
| Nov 7, 2026 | 30 |
| Nov 6, 2026 | 30 |
| Nov 5, 2026 | 30 |
| Nov 4, 2026 | 30 |
| Nov 3, 2026 | 30 |
| Nov 2, 2026 | 30 |
| Nov 1, 2026 | 30 |
| Oct 31, 2026 | 30 |
| Oct 30, 2026 | 30 |
| Oct 29, 2026 | 30 |
| Oct 28, 2026 | 30 |
| Oct 27, 2026 | 30 |
| Oct 26, 2026 | 30 |
| Oct 25, 2026 | 30 |
| Oct 24, 2026 | 30 |
| Oct 23, 2026 | 30 |
| Oct 22, 2026 | 30 |
| Oct 21, 2026 | 30 |
| Oct 20, 2026 | 30 |
| Oct 19, 2026 | 30 |
| Oct 18, 2026 | 30 |
| Oct 17, 2026 | 30 |
| Oct 16, 2026 | 30 |
| Oct 15, 2026 | 30 |
| Oct 14, 2026 | 30 |
| Oct 13, 2026 | 30 |
| Oct 12, 2026 | 30 |
| Oct 11, 2026 | 30 |
| Oct 10, 2026 | 30 |
| Oct 9, 2026 | 30 |
| Oct 8, 2026 | 30 |
| Oct 7, 2026 | 30 |
| Oct 6, 2026 | 29 |
| Oct 5, 2026 | 29 |
| Oct 4, 2026 | 29 |
| Oct 3, 2026 | 29 |
Map
Where China Unicom Global'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.
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| Any2West Los Angeles and Silicon Valley, United States | Website list only | ||
| BBIX Manila Manila, Philippines | 10G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 10G | Both | |
| BKNIX (Thailand) Bangkok, Thailand | 100G | Both Speed differs | |
| CNX Phnom Penh, Cambodia | 10G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both | |
| Equinix Hong Kong Hong Kong, Hong Kong | 100G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 10G | PeeringDB | |
| France-IX Paris Paris, France | 10G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 2 × 100G | Both | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 10G | Both | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | Website list only | ||
| JINX Johannesburg, South Africa | 10G | Both | |
| JKT-IX Jakarta, Indonesia | 10G | Both | |
| JPIX TOKYO Tokyo, Japan | 10G | Both | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| KINX Seoul, South Korea | 10G | PeeringDB | |
| KIXP - Nairobi Nairobi, Kenya | 10G | Both | |
| LINX LON1 London, United Kingdom | 100G | Both Speed differs | |
| MSK-IX Moscow Moscow, Russia | 10G | Both | |
| MyIX Kuala Lumpur, Malaysia | 10G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 100G | Both Speed differs | |
| NetIX Sofia, Bulgaria | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both | |
| SH-IX Fujairah, United Arab Emirates | 100G | PeeringDB only | |
| SwissIX Zurich, Switzerland | 10G | Both | |
| THAILAND IX (TH-IX) Bangkok, Thailand | 10G | Both | |
| TPIX-TW Taipei/Taiwan, Taiwan | 10G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 100G | Both Speed differs |
These exchanges have a switch in a facility where China Unicom Global lists itself in PeeringDB, but don't have China Unicom Global 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 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| KleyReXFrankfurt, Germany | 471 | |
| LINX LON2London, United Kingdom | 315 | |
| LONAPLondon, United Kingdom | 311 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| DE-CIX New YorkNew York, United States | 281 | |
| MegaIX SydneySydney, Australia | 267 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| NIX.CZPrague, Czechia | 225 | |
| Equinix SydneySydney, Australia | 219 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| THINX WarsawWarsaw, Poland | 194 | |
| Equinix San JoseSan Jose, United States | 182 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Equinix TokyoTokyo, Japan | 127 | |
| BIXBudapest, Hungary | 122 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| SFMIXSan Francisco, United States | 100 | |
| BBIX US-WestWest Coast, United States | 87 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| B-IXSofia, Bulgaria | 77 | |
| Equinix Palo AltoPalo Alto, United States | 69 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| Equinix LondonLondon, United Kingdom | 53 | |
| TYIXTokyo, Japan | 53 | |
| PyramIXCairo, Egypt | 48 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| Japan Community IXJapan, Japan | 32 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| NYIIX Los AngelesLos Angeles, United States | 21 | |
| IAIXHong Kong, Hong Kong | 20 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| MONICA IX (AS 138121)Jakarta, Indonesia | 19 | |
| GNM-IX SGSingapore, Singapore | 15 | |
| Japan Community IX - INIXPJapan, Japan | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| AMS-IX SingaporeSingapore, Singapore | 14 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| AKIXZurich, Switzerland | 11 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| Impart IXSingapore, Singapore | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| TievoluIXFrankfurt, Germany | 4 |
Facilities (16)
The buildings China Unicom Global lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty Frankfurt FRA1-27Frankfurt | 2 of 30 | |
| Equinix SG1 - SingaporeSingapore | 3 of 11 | |
| Equinix LD8 - London, DocklandsLondon | 2 of 9 | |
| Equinix SV1/SV5/SV10 - Silicon Valley, San JoseSan Jose | 1 of 8 | |
| AT TOKYO (CC1/CC2)Tokyo | 4 of 6 | |
| Equinix HK1 - Hong KongTsuen Wan | 2 of 6 | |
| CoreSite - Los Angeles (LA1) One WilshireLos Angeles | 1 of 5 | |
| Equinix SY1/SY2 - SydneySydney | 2 of 5 | |
| MEGA-i (iAdvantage Hong Kong)Hong Kong | 2 of 4 | |
| Equinix TY9 - TokyoTokyo | 1 of 3 | |
| Equinix DX1 - DubaiDubai | 2 of 2 | |
| SmartHub FujairahFujairah | 2 of 2 | |
| China Unicom (Hong Kong) Global CenterHong Kong | 0 of 1 | |
| DataBank New York (LGA1)New York | 0 of 1 | |
| Nusantara Data Center - JakartaJakarta | 0 of 1 | |
| MCX10Hong Kong | No exchange |
Recent changes Search them
- Oct 20, 2026 [PDB] AS10099 China Unicom Global no longer in PeeringDB at IX.br (PTT.br) São Paulo (still on its website's members list)