BJ-TELECOM-ADMINIS
BGP inherited
Cluster stats
| Netblocks | 3 · 269 IPv4 addresses |
| All fragments | 17 blocks across 8 clusters |
| Cluster ID | 212419361 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 123.127.227.136/29 | BJ-TELECOM-ADMINIS | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 123.127.228.0/24 | BJ-TELECOM-ADMINIS | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 202.99.2.56/29 | BJ-TELECOM-ADMINIS | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to BJ-TELECOM-ADMINIS 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.
| 123.127.228.0/24 /24 | authorized for AS4808 — China Unicom |
NIC Handles
CH455-AP
MAINT-CNCGROUP-BJ
SY21-AP
Wk349-AP
Wk349-AP
Wk350-AP
Wk350-AP