Jalabyte
Cluster stats
Netblocks13
Cluster ID193391871
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

2 weekly snapshots · JSON
13 0 netblocks since 2026-07-05
2026-07-05 peak 13 2026-07-06

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.252.147.135/32 Jalabyte PEERINGDB ASSIGNED ● high
43.254.83.122/32 Jalabyte PEERINGDB ASSIGNED ● high
49.213.56.171/32 Jalabyte PEERINGDB ASSIGNED ● high
103.61.232.139/32 Jalabyte PEERINGDB ASSIGNED ● high
119.11.187.97/32 Jalabyte PEERINGDB ASSIGNED ● high
123.108.11.253/32 Jalabyte PEERINGDB ASSIGNED ● high
157.10.16.57/32 Jalabyte PEERINGDB ASSIGNED ● high
2001:7fa:2:5::40d/128 Jalabyte PEERINGDB ASSIGNED ● high
2001:df1:d440:1::8b/128 Jalabyte PEERINGDB ASSIGNED ● high
2001:df5:7880:0:2:1fc5:0:1/128 Jalabyte PEERINGDB ASSIGNED ● high
2401:91e0:31::139:205:1/128 Jalabyte PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:13:9205:1/128 Jalabyte PEERINGDB ASSIGNED ● high
2404:2f80:206::57/128 Jalabyte PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS139205