UNKNOWN

Unresolved
Cluster stats
Netblocks13
All fragments 449,394 blocks across 1,216,049 clusters
Cluster ID204717608
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.190.156.0/23 AS269663 BGP ANNOUNCED ● high
45.190.156.0/22 AS269663 BGP ANNOUNCED ● high
45.190.158.0/23 AS269663 BGP ANNOUNCED ● high
2804:67fc::/32 AS269663 BGP ANNOUNCED ● high
2804:67fc::/33 AS269663 BGP ANNOUNCED ● high
2804:67fc:8000::/33 AS269663 BGP ANNOUNCED ● high
45.190.156.128/29 UNKNOWN LACNIC reassigned ● medium
45.190.156.204/30 UNKNOWN LACNIC reassigned ● medium
45.190.157.32/29 UNKNOWN LACNIC reassigned ● medium
45.190.157.48/28 UNKNOWN LACNIC reassigned ● medium
45.190.157.240/30 UNKNOWN LACNIC reassigned ● medium
45.190.159.0/28 UNKNOWN LACNIC reassigned ● medium
2804:67fc::/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 (13 of 13)
Possible discrepancies (7)

These blocks are registered to UNKNOWN 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:67fc::/32 /32 authorized for AS269663 — AS269663
2804:67fc::/32 /32 authorized for AS269663 — AS269663
2804:67fc::/33 /33 authorized for AS269663 — AS269663
2804:67fc:8000::/33 /33 authorized for AS269663 — AS269663
45.190.156.0/22 /22 authorized for AS269663 — AS269663
45.190.156.0/23 /23 authorized for AS269663 — AS269663
45.190.158.0/23 /23 authorized for AS269663 — AS269663

NIC Handles

AS269663