RBU_STATIC-HYDERABAD
Unresolved
Cluster stats
| Netblocks | 5 |
| All fragments | 52 blocks across 12 clusters |
| Cluster ID | 193261230 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.17.44.0/22 | RBU_STATIC-HYDERABAD | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.17.48.0/21 | RBU_STATIC-HYDERABAD | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.17.88.0/23 | RBU_STATIC-HYDERABAD | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.17.92.0/23 | RBU_STATIC-HYDERABAD | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.17.102.0/23 | RBU_STATIC-HYDERABAD | 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
(5 of 5)
RPKI-inferred operator
Tata Communications Limited
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
MAINT-VSNL-AP
TC651-AP
TC651-AP