JINDALNET

BGP inherited
Cluster stats
Netblocks10
Cluster ID210223546
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
119.226.31.12 – 119.226.31.31 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
119.226.47.248/29 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
119.226.48.252/30 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.5.250/32 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.17.88 – 124.30.17.99 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.137.12 – 124.30.137.23 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.182.196 – 124.30.182.207 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.212.160 – 124.30.212.171 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
124.30.239.108 – 124.30.239.119 JINDALNET APNIC ASSIGNED NON-PORTABLE ● low
221.134.154.176 – 221.134.154.187 JINDALNET 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

HS51-AP HS51-AP MAINT-IN-IRINN MAINT-IN-SIFY