INDOTRANS

Handle
Cluster stats
Netblocks9
All fragments 22 blocks across 3 clusters
Cluster ID208804055
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.30.172.178/32 INDOTRANS PEERINGDB ASSIGNED ● high
103.225.173.15/32 INDOTRANS PEERINGDB ASSIGNED ● high
119.11.184.180/32 INDOTRANS PEERINGDB ASSIGNED ● high
123.108.8.235/32 INDOTRANS PEERINGDB ASSIGNED ● high
218.100.27.223/32 INDOTRANS PEERINGDB ASSIGNED ● high
2001:7fa:2:5::eb/128 INDOTRANS PEERINGDB ASSIGNED ● high
2001:7fa:f::6f/128 INDOTRANS PEERINGDB ASSIGNED ● high
2400:9c80:0:173::452:89/128 INDOTRANS PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:4:5289:1/128 INDOTRANS PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “INDOTRANS” — 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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
55.6% of checked blocks have valid RPKI ROA coverage (5 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS45289