AS265798

Handle
Cluster stats
Netblocks19
Cluster ID204420552
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 (19)

⬇ export CSV
CIDR Org name Registry Status Confidence
38.211.32.0/24 AS265798 BGP ANNOUNCED ● high
131.221.64.0/24 AS265798 BGP ANNOUNCED ● high
131.221.64.0/22 AS265798 BGP ANNOUNCED ● high
131.221.65.0/24 AS265798 BGP ANNOUNCED ● high
131.221.66.0/24 AS265798 BGP ANNOUNCED ● high
131.221.67.0/24 AS265798 BGP ANNOUNCED ● high
138.117.14.0/24 AS265798 BGP ANNOUNCED ● high
138.117.15.0/24 AS265798 BGP ANNOUNCED ● high
138.204.158.0/24 AS265798 BGP ANNOUNCED ● high
138.204.159.0/24 AS265798 BGP ANNOUNCED ● high
201.158.96.0/24 AS265798 BGP ANNOUNCED ● high
2803:cb80::/32 AS265798 BGP ANNOUNCED ● high
2803:cb80:1::/48 AS265798 BGP ANNOUNCED ● high
2803:cb80:10::/48 AS265798 BGP ANNOUNCED ● high
2803:cb80:80::/44 AS265798 BGP ANNOUNCED ● high
2803:cb80:cfd::/48 AS265798 BGP ANNOUNCED ● high
2803:cb80:fffe::/48 AS265798 BGP ANNOUNCED ● high
2803:cb80:ffff::/48 AS265798 BGP ANNOUNCED ● high
2803:cb80::/32 UNKNOWN LACNIC allocated ● medium

Network trust

what's this?
RPKI hygiene: B how networks compare →
94.7% of checked blocks have valid RPKI ROA coverage (18 of 19)
Possible discrepancies (1)

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

138.117.15.0/24 /24 authorized for AS272870 — AS272870

NIC Handles

AS265798