ixreport

DataSphere Global Communications: PeeringDB fix list

AS209109 · peeringdb.com/net/19531

One thing to fix in DataSphere Global Communications's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on DataSphere Global Communications'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 DataSphere Global Communications's PeeringDB record. Add one entry per connection with these values.

  1. Hong Kong Hong Kong Global Internet Exchange Hong Kong, Hong Kong · PeeringDB 4625From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4–
    IPv62404:c140:101e::20:9109
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4–
    IPv62404:c140:101e::2:20:9109
    Speed20000 Mbps (20G)
    RS peerYes

    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.

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