John Leo Navarro

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
IPv6 8 prefixes (largest 2a0a:280:2100::/40)
Cluster ID214573316
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
2001:504:125:e1::baa/128 John Leo Navarro PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:19:9676:1/128 John Leo Navarro PEERINGDB ASSIGNED ● high
2001:7f8:11f:be00:199:676:0:1/128 John Leo Navarro PEERINGDB ASSIGNED ● high
2a06:a005:1877::/48 John Leo Navarro BGP ANNOUNCED ● high
2a0a:280:2140::/42 John Leo Navarro BGP ANNOUNCED ● high
2a0a:280:21c0::/42 John Leo Navarro BGP ANNOUNCED ● high
2a0e:8f01:1000:46::111/128 John Leo Navarro PEERINGDB ASSIGNED ● high
2a0a:280:2100::/40 John Leo Navarro RIPE ALLOCATED-BY-LIR ● low

IPv6 ranges (8)

Network trust

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

NIC Handles

AS199676 AS199676 DUMY-RIPE DUMY-RIPE FATIHUNLU-MNT ORG-AA2838-RIPE ROUTE48-MNT ROUTE48-MNT jolo22-mnt jolo22-mnt