Autonomous system
AS10032 HGC-AS-AP BDX DC Services HK Limited
Unclassified APNIC
Summary
BDx DC Services (HK)
datacenter colocation hosting hong-kong
HGC-AS-AP is now held by BDX DC Services (HK) Limited, the Hong Kong data-centre operator trading as BDx. The handle is a fossil: this AS was Hutchison GlobalCenter, the data-centre arm of Hutchison Global Communications, and it kept the old name after the colocation business was carved out from the telco.
What it's used for
- Colocation and interconnection at BDx's Hong Kong campuses (HKG1 in Cavendish, HKG2 on Kung Yip Street, Kwai Chung), serving OTT, financial, professional-services, enterprise, telecom and government tenants.
- Addressing for managed and cross-connected services inside those facilities, plus the legacy HGC-era customer assignments that came with the business.
Notable
- The kind here is hosting/colocation, not the eyeball ISP the handle suggests. HGC's consumer and carrier network is a different AS; this one shows 47 IPv4 prefixes carrying 15,616 addresses, two IPv6 /48s, and only 10 observed neighbours. A Hong Kong retail ISP would have far more addresses; a transit carrier would have far more neighbours. A modest, heavily deaggregated block behind a short peering list is exactly a data-centre AS announcing customer assignments.
- The prefixes bear that out — a single
203.129.64.0/19anchor surrounded by scattered /24s from218.189.0.0,118.103.0.0and43.252.0.0space, the classic pattern of per-tenant allocations carved out of an operator's legacy ranges.
Interesting
- A good reminder that the handle is evidence of history, not of ownership: read
HGC-AS-APas "this used to be HGC's", not "this is HGC".
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Hong Kong Internet Exchange | Hong Kong, China | 123.255.90.110 |
Transit providers
6 upstream, 0 downstream and 9 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS9381 | HKBN Enterprise Solutions HK Limited | 1,976 |
| AS9304 | HGC Global Communications Limited | 563 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | 113 |
| AS24482 | SG.GS | 38 |
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | 36 |
| AS8359 | MTS PJSC | 2 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 25 prefixes · 15.62K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| HK | Hong Kong | 27 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS10032- Registry name
- HGC-AS-AP
- Registrant
- BDX DC Services (HK) Limited
- Abuse contact
- nilamadhab.mishra@bdxworld.com
- Registered
- 2008-09-04
- Last changed
- 2024-08-08
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 22% valid · 11 valid, 38 with no ROA
- ROAs
- 31 authorising AS10032
- ASPA
- no ASPA record
- IRR
- 96% registered · 47 of 49 announcements
- Route objects
- 350 naming AS10032
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 431 networks and 1,768 prefixes, as published 2026-10-12. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere