AS28027

Handle
Cluster stats
Netblocks15
Cluster ID204397217
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
192.188.59.0/24 AS28027 BGP ANNOUNCED ● high
200.9.176.0/24 AS28027 BGP ANNOUNCED ● high
200.10.147.0/24 AS28027 BGP ANNOUNCED ● high
200.10.148.0/24 AS28027 BGP ANNOUNCED ● high
200.10.149.0/24 AS28027 BGP ANNOUNCED ● high
200.10.150.0/24 AS28027 BGP ANNOUNCED ● high
200.10.151.0/24 AS28027 BGP ANNOUNCED ● high
200.126.0.0/20 AS28027 BGP ANNOUNCED ● high
200.126.10.0/24 AS28027 BGP ANNOUNCED ● high
200.126.16.0/22 AS28027 BGP ANNOUNCED ● high
200.126.20.0/23 AS28027 BGP ANNOUNCED ● high
200.126.22.0/24 AS28027 BGP ANNOUNCED ● high
200.126.23.0/24 AS28027 BGP ANNOUNCED ● high
200.126.24.0/21 AS28027 BGP ANNOUNCED ● high
2801:0:20::/48 AS28027 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)
RPKI-inferred operator AS27947
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
Possible discrepancies (1)

These blocks are registered to AS28027 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:20::/48 /48 authorized for AS61468 — AS61468

NIC Handles

AS28027