Sever Telecom
BGP inherited
Cluster stats
| Netblocks | 8 |
| All fragments | 36 blocks across 6 clusters |
| Cluster ID | 193389300 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-06
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.0.14.72/32 | Sever Telecom | PEERINGDB | ASSIGNED | ● high |
| 185.0.45.106/32 | Sever Telecom | PEERINGDB | ASSIGNED | ● high |
| 185.1.153.106/32 | Sever Telecom | PEERINGDB | ASSIGNED | ● high |
| 193.27.37.24/32 | Sever Telecom | PEERINGDB | ASSIGNED | ● high |
| 37.202.15.0/24 | Sever-Telecom | RIPE | ASSIGNED PA | ● low |
| 185.141.232.0/23 | Sever-Telecom | RIPE | ASSIGNED PA | ● low |
| 185.141.235.0/24 | Sever-Telecom | RIPE | ASSIGNED PA | ● low |
| 212.113.113.0/24 | Sever-Telecom | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
25.0%
of checked blocks have valid RPKI ROA coverage
(2 of 8)
No discrepancies found among checked blocks.
NIC Handles
AS214173
DUMY-RIPE
DUMY-RIPE
FACTORIAL-MNT
Sever-Telecom
VF1-MNT
vitaliy_v_selin