ixreport

DataSphere Global Communications

AS209109 · DS Studio, DS Network, DataSphere

DataSphere (H.K) Limited

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
3Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with DataSphere Global Communications? · Where should DataSphere Global Communications peer next? · Compare DataSphere Global Communications with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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.

Exchanges over time

01234Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

In the last 30 days DataSphere Global Communications joined 0 exchanges and left 1. Growing networks

Left

  • STUIX Taipei City Nov 16, 2026 PeeringDB only

Map

Where DataSphere Global Communications'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.

Exchanges

Total port capacity 45.3G across 3 exchanges.

Hong Kong DataSphere Internet Exchange (Hong Kong) Hong Kong, Hong Kong 31.58.86.130 2602:f613::209:109:1 25G Yes PeeringDB
Hong Kong Hong Kong Global Internet Exchange Hong Kong, Hong Kong 138.252.211.21
138.252.211.33
2404:c140:101e::20:9109
2404:c140:101e::2:20:9109
20G 35 routes Not in PeeringDB
Taiwan TPIX-TW Taipei/Taiwan, Taiwan 203.163.223.57 2406:d400:1:133:203:163:223:57 300M Yes PeeringDB

Exchanges in its buildings that it isn't on (18)

These exchanges have a switch in a facility where DataSphere Global Communications lists itself in PeeringDB, but don't have DataSphere Global Communications 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.

United States SIX SeattleSeattle, United States 372 1530 SWIFT - NOCIX
United States KCIXKansas City, United States 216 1530 SWIFT - NOCIX
Bulgaria NetIXSofia, Bulgaria 204 Chief LY Building Taipei
United States MICEMinneapolis, MN, United States 157 1530 SWIFT - NOCIX
Taiwan STUIXTaipei City, Taiwan 131 Chief LY Building Taipei
United States STLIXSaint Louis, MO, United States 108 1530 SWIFT - NOCIX
United States IX-DenverDenver, United States 96 1530 SWIFT - NOCIX
United States HOUIXHouston, United States 81 1530 SWIFT - NOCIX
United States SIX Seattle (Jumbo)Seattle, United States 69 1530 SWIFT - NOCIX
United States F4IX MCIKansas City, United States 67 1530 SWIFT - NOCIX
Hong Kong ixFabric - Hong KongHong Kong, Hong Kong 50 iTech Towers 2
United States HN Internet Exchange (Main)North Kansas City, United States 27 1530 SWIFT - NOCIX
Taiwan FOXTainan, Taiwan 22 Chief LY Building Taipei
United States SpringIXSpringfield, MO, United States 22 1530 SWIFT - NOCIX
United States DesMoinesIXDes Moines, United States 11 1530 SWIFT - NOCIX
United States Global Peer ExchangeWashington, United States 6 Chief LY Building Taipei
United States SIOUIXSioux City, United States 4 1530 SWIFT - NOCIX
United States MOCIXKansas City, United States 3 1530 SWIFT - NOCIX
Facilities (3)

The buildings DataSphere Global Communications lists in PeeringDB, and how many of the exchanges in each it's on.

United States 1530 SWIFT - NOCIXNorth Kansas City 0 of 13
Taiwan Chief LY Building TaipeiTaipei 1 of 5
Hong Kong iTech Towers 2New Territories 2 of 3

Recent changes Search them

  • Nov 16, 2026 [PDB] AS209109 DataSphere Global Communications left STUIX
  • Nov 15, 2026 [IXF] AS209109 DataSphere Global Communications dropped from STUIX's IX-F list (still in PeeringDB)
  • Oct 28, 2026 [PDB] AS209109 DataSphere Global Communications no longer in PeeringDB at Hong Kong Global Internet Exchange (still on its IX-F list and on its website's members list)
  • Oct 27, 2026 [PDB] AS209109 DataSphere Global Communications now in PeeringDB at Hong Kong Global Internet Exchange
  • Oct 27, 2026 [PDB] AS209109 DataSphere Global Communications no longer in PeeringDB at Hong Kong Global Internet Exchange (still on its IX-F list and on its website's members list)