ixreport

China Unicom Global: PeeringDB fix list

AS10099 · peeringdb.com/net/7268

PeeringDB

7 things to fix in China Unicom Global's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct, 1 to check. As of 2026-10-08 18:53 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 (1)

On the exchange's own member list, but not in China Unicom Global's PeeringDB record. Add one entry per connection with these values.

  1. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142From its website members list
    IPv4206.72.211.141
    IPv62001:504:13::211:141
    SpeedNot published
    RS peerNot published

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.

  1. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • 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.

  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 195.66.231.13: set Speed to 10000 (10G) (now 100000).
  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • 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.

  4. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.226.67185.1.226.67 185.1.226.149
    IPv6 address missing from PeeringDB2001:67c:29f0::1:99:12001: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.

  5. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • 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.

  1. United Arab Emirates SH-IX Fujairah, United Arab Emirates · PeeringDB 866Not on its website members list
    IPv4185.1.15.39
    IPv62001:7f8:7a::100:99:1
    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/10099/: 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.