P4S
BGP inherited
Cluster stats
| Netblocks | 7 |
| Cluster ID | 210178414 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 85.146.194.96/27 | P4S | RIPE | ASSIGNED PA | ● low |
| 85.146.202.48/30 | P4S | RIPE | ASSIGNED PA | ● low |
| 85.146.230.0/27 | P4S | RIPE | ASSIGNED PA | ● low |
| 85.146.230.64/28 | P4S | RIPE | ASSIGNED PA | ● low |
| 159.100.65.176/30 | P4S | RIPE | LEGACY | ● low |
| 159.100.115.80/28 | P4S | RIPE | LEGACY | ● low |
| 212.78.214.64/26 | P4S | 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
(7 of 7)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
TNF-MNT