No.31, Jin-rong Street
SC-YAAN-YINGJINGJIAOTONGJU
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 256 blocks across 248 clusters |
| Cluster ID | 206810146 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.157.226.88/30 | SC-YAAN-YINGJINGJIAOTONGJU | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 222.213.249.96/30 | SC-YAAN-YINGJINGJIAOTONGJU | APNIC | ASSIGNED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “SC YAAN” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- SC-YAAN-YALIANWANGLUO 3 blocks
- SC-YAAN-CHANGXIANJU 2 blocks
- SC-YAAN-SHIKEJIJUQINGBAOCHU 2 blocks
- SC-YAAN-SHIZHENGFU 2 blocks
- SC-YAAN-SHIWEIJIYAOJU 2 blocks
- SC-YAAN-BAOXINGHUANBAOJU 2 blocks
- SC-YAAN-SHIYIYUAN 1 blocks
- SC-YAAN-SHIMIANYANENGGONGSI 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- YAANET via Iran Telecommunication Company PJS sub-allocation
- GOSUDARSTVENNYAANNUTETNYAKOMPANYA via JSC Kazakhtelecom sub-allocation
- N4-YAANA sub-allocation
- Yaana-Linknet via Danmarks Tekniske Universitet sub-allocation
- Yaana-Routed via Danmarks Tekniske Universitet sub-allocation
- Kalayaanltd London via Virtual1 Limited sub-allocation
- YAAN-SCIENCE-GOV via No.31,Jin-rong Street sub-allocation
- YAAN-WY-NETBAR via No.31,Jin-rong Street sub-allocation
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
No discrepancies found among checked blocks.
NIC Handles
CS408-AP
CS408-AP
MAINT-CHINANET-SC