IDC-1
Data as of 2026-08-30
BGP inherited
Cluster stats
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:1b28:dc::/48) |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 235071879 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.253.212.0/24 | IDC-1 | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 2001:1b28:dc::/48 | IDC_1 | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:1b28:dc::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to IDC-1 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 58.253.212.0/24 /24 | authorized for AS17816 — China Unicom |
NIC Handles
CG272-AP
CG272-AP
DUMY-RIPE
DUMY-RIPE
INFONET-MNT
MAINT-CNCGROUP-GD