BLUE-CHIP
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 7 blocks across 4 clusters |
| Cluster ID | 192952325 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 |
|---|---|---|---|---|
| 212.250.102.0/24 | BLUE-CHIP | RIPE | ASSIGNED PA | ● low |
| 212.250.103.0/24 | BLUE-CHIP | RIPE | ASSIGNED PA | ● low |
| 213.104.8.96/30 | BLUE-CHIP | RIPE | ASSIGNED PA | ● low |
| 213.229.54.136/30 | Blue-Chip | RIPE | ASSIGNED PA | ● 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 BLUE-CHIP 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.
| 212.250.102.0/24 /24 | authorized for AS5089 — Virgin Media Limited |
| 212.250.103.0/24 /24 | authorized for AS5089 — Virgin Media Limited |
NIC Handles
AS5089-MNT
DUMY-RIPE
DUMY-RIPE
PRIO-MNT