portland
PORTLAND
Registry
Cluster stats
| Netblocks | 4 |
| All fragments | 56 blocks across 21 clusters |
| Cluster ID | 192208287 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.90.148.188/30 | portland | RIPE | ASSIGNED PA | ● low |
| 217.38.67.216/29 | PORTLAND | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:c171::/48 | PORTLAND | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:c171::/56 | PORTLAND | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to PORTLAND 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.
| 2a00:2381:c171::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:c171::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
NV-MNT-RIPE