AS27817

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

IP Ranges (15)

⬇ export CSV
CIDR Org name Registry Status Confidence
167.249.41.0/24 AS27817 BGP ANNOUNCED ● high
167.249.42.0/24 AS27817 BGP ANNOUNCED ● high
186.113.12.0/24 AS27817 BGP ANNOUNCED ● high
190.15.1.0/24 AS27817 BGP ANNOUNCED ● high
190.15.5.0/24 AS27817 BGP ANNOUNCED ● high
190.15.16.0/21 AS27817 BGP ANNOUNCED ● high
190.15.17.0/24 AS27817 BGP ANNOUNCED ● high
190.15.24.0/22 AS27817 BGP ANNOUNCED ● high
190.15.28.0/23 AS27817 BGP ANNOUNCED ● high
190.15.30.0/24 AS27817 BGP ANNOUNCED ● high
190.15.31.0/24 AS27817 BGP ANNOUNCED ● high
201.131.90.0/23 AS27817 BGP ANNOUNCED ● high
2001:13f8::/32 AS27817 BGP ANNOUNCED ● high
2801:0:4c0::/48 AS27817 BGP ANNOUNCED ● high
2801:16:a800::/48 AS27817 BGP ANNOUNCED ● high

Network trust

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

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

2801:0:4c0::/48 /48 authorized for AS266736 — AS266736
201.131.90.0/23 /23 authorized for AS266736 — AS266736

NIC Handles

AS27817