Huawei Cloud Global: PeeringDB fix list

AS136907 · peeringdb.com/net/18382

PeeringDB

6 things to fix in Huawei Cloud Global's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on Huawei Cloud 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 (3)

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.53
    IPv62001:7f8:d:fe::53
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.53
    IPv62001:7f8:d:fb::53
    SpeedNot published
    RS peerYes
  3. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.53
    IPv62001:7f8:d:fc::53
    SpeedNot published
    RS peerYes

Correct these entries (3)

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
    Port speed differs100G2 × 10G
    • In the entry with IPv4 80.249.210.185: set Speed to 10000 (10G) (now 100000).
    • In the entry with IPv4 80.249.215.171: set Speed to 10000 (10G) (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. South Africa JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 196.60.96.188: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 196.60.96.88: set Speed to 100000 (100G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:73:0:2:16cb:0:1 2001:7f8:73:0:2:16cb:0:2
    • In the entry with IPv4 185.1.8.87: set IPv6 to 2001:7f8:73:0:2:16cb:0:1 (now empty).
    • In the entry with IPv4 185.1.8.90: set IPv6 to 2001:7f8:73:0:2:16cb:0:2 (now empty).

From ixreport.com/net/136907/: 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.