AS27893
Handle
Cluster stats
| Netblocks | 22 |
| Cluster ID | 207685465 |
| Registry | BGP |
| Customers | find 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 (22)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 150.186.33.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.64.0/18 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.67.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.68.0/22 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.72.0/22 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.76.0/22 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.80.0/23 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.82.0/23 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.84.0/22 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.88.0/21 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.96.0/20 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.112.0/22 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.116.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.117.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.118.0/23 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.120.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.121.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.122.0/23 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.124.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.125.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.126.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
| 190.170.127.0/24 | AS27893 | BGP | ANNOUNCED | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(22 of 22)
RPKI-inferred operator
AS17287
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.
No discrepancies found among checked blocks.
NIC Handles
AS27893