SEPE
BGP inherited
Cluster stats
| Netblocks | 3 · 269 IPv4 addresses |
| All fragments | 6 blocks across 3 clusters |
| Cluster ID | 209261502 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 192.187.23.0/24 | SEPE | RIPE | ASSIGNED PA | ● low |
| 194.219.22.136/29 | SEPE | RIPE | ASSIGNED PA | ● low |
| 212.50.151.8/29 | SEPE-NET | 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
(3 of 3)
Possible discrepancies (1)
These blocks are registered to SEPE 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.
| 192.187.23.0/24 /24 | authorized for AS200521 — Ministerio de Transformacion Digital y de la Funcion Publica |
NIC Handles
AR14988-RIPE
DUMY-RIPE
DUMY-RIPE
FI2G-MNT
FORTHNETGR-MNT
SEAP-AGE