AS264837

Handle
Cluster stats
Netblocks15
Cluster ID204731866
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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 (15)

⬇ export CSV
CIDR Org name Registry Status Confidence
38.52.136.0/21 AS264837 BGP ANNOUNCED ● high
38.52.136.0/24 AS264837 BGP ANNOUNCED ● high
38.52.138.0/24 AS264837 BGP ANNOUNCED ● high
38.52.139.0/24 AS264837 BGP ANNOUNCED ● high
38.52.140.0/24 AS264837 BGP ANNOUNCED ● high
38.52.141.0/24 AS264837 BGP ANNOUNCED ● high
38.52.142.0/24 AS264837 BGP ANNOUNCED ● high
38.52.143.0/24 AS264837 BGP ANNOUNCED ● high
38.150.88.0/22 AS264837 BGP ANNOUNCED ● high
170.81.144.0/24 AS264837 BGP ANNOUNCED ● high
170.81.145.0/24 AS264837 BGP ANNOUNCED ● high
170.81.146.0/24 AS264837 BGP ANNOUNCED ● high
170.81.147.0/24 AS264837 BGP ANNOUNCED ● high
170.81.146.128/27 UNKNOWN LACNIC reallocated ● medium
2803:22c0::/32 UNKNOWN LACNIC allocated ● medium

Network trust

what's this?
RPKI hygiene: D how networks compare →
46.7% of checked blocks have valid RPKI ROA coverage (7 of 15)
Possible discrepancies (2)

These blocks are registered to AS264837 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.

38.150.88.0/22 /22 authorized for AS272118 — AS272118
170.81.147.0/24 /24 authorized for AS272118 — AS272118

NIC Handles

AS264837