NAVEGAR PROVEDOR

BGP inherited
Cluster stats
Netblocks9
All fragments 24 blocks across 2 clusters
Cluster ID191586659
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-12

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.5.104.0/22 AS266096 BGP ANNOUNCED ● high
45.5.104.0/23 AS266096 BGP ANNOUNCED ● high
45.5.106.0/24 AS266096 BGP ANNOUNCED ● high
45.5.107.0/24 AS266096 BGP ANNOUNCED ● high
2804:3a90::/32 AS266096 BGP ANNOUNCED ● high
2804:3a90::/34 AS266096 BGP ANNOUNCED ● high
2804:3a90:4000::/34 AS266096 BGP ANNOUNCED ● high
2804:3a90:c000::/34 AS266096 BGP ANNOUNCED ● high
2804:3a90::/32 UNKNOWN LACNIC allocated ● medium

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (9)

These blocks are registered to NAVEGAR PROVEDOR but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2804:3a90::/32 /32 authorized for AS266096 — AS266096
2804:3a90::/32 /32 authorized for AS266096 — AS266096
2804:3a90::/34 /34 authorized for AS266096 — AS266096
2804:3a90:4000::/34 /34 authorized for AS266096 — AS266096
2804:3a90:c000::/34 /34 authorized for AS266096 — AS266096
45.5.104.0/22 /22 authorized for AS266096 — AS266096
45.5.104.0/23 /23 authorized for AS266096 — AS266096
45.5.106.0/24 /24 authorized for AS266096 — AS266096
45.5.107.0/24 /24 authorized for AS266096 — AS266096

NIC Handles

AS266096