AS264126

Handle
Cluster stats
Netblocks14
Cluster ID204716138
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
138.59.202.0/24 AS265938 BGP ANNOUNCED ● high
164.163.44.0/22 AS265938 BGP ANNOUNCED ● high
164.163.44.0/23 AS265938 BGP ANNOUNCED ● high
164.163.46.0/23 AS265938 BGP ANNOUNCED ● high
2804:4028::/32 AS265938 BGP ANNOUNCED ● high
2804:4028:100::/40 AS265938 BGP ANNOUNCED ● high
138.59.200.0/22 AS264126 BGP ANNOUNCED ● medium
138.59.200.0/24 AS264126 BGP ANNOUNCED ● medium
138.59.200.0/23 AS264126 BGP ANNOUNCED ● medium
138.59.201.0/24 AS264126 BGP ANNOUNCED ● medium
2804:22d8:8000::/34 AS264126 BGP ANNOUNCED ● medium
2804:22d8:8100::/40 AS264126 BGP ANNOUNCED ● medium
2804:22d8:c000::/34 AS264126 BGP ANNOUNCED ● medium
2804:4028::/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 (14 of 14)
Possible discrepancies (6)

These blocks are registered to AS264126 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:4028::/32 /32 authorized for AS265938 — AS265938
2804:4028::/32 /32 authorized for AS265938 — AS265938
2804:4028:100::/40 /40 authorized for AS265938 — AS265938
164.163.44.0/22 /22 authorized for AS265938 — AS265938
164.163.44.0/23 /23 authorized for AS265938 — AS265938
164.163.46.0/23 /23 authorized for AS265938 — AS265938

NIC Handles

AS264126 AS265938