JAGONET

Data as of 2026-10-11
Handle
This organisation
Netblocks9
IPv6 3 prefixes (largest 2001:7fa:2:5::7d/128)
Also registered under this name 11 netblocks across 3 separate records
Record ID246705564
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.252.146.202/32 JAGONET PEERINGDB ASSIGNED ● high
103.225.173.40/32 JAGONET PEERINGDB ASSIGNED ● high
119.11.185.180/32 JAGONET PEERINGDB ASSIGNED ● high
123.108.8.125/32 JAGONET PEERINGDB ASSIGNED ● high
157.10.16.50/32 JAGONET PEERINGDB ASSIGNED ● high
218.100.41.194/32 JAGONET PEERINGDB ASSIGNED ● high
2001:7fa:2:5::7d/128 JAGONET PEERINGDB ASSIGNED ● high
2400:9c80:0:173::142:347/128 JAGONET PEERINGDB ASSIGNED ● high
2404:2f80:206::5a/128 JAGONET PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Footprint over time

16 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-10-11

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

AS142347