TESCOM
BGP inherited
Cluster stats
| Netblocks | 3 · 289 IPv4 addresses |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 214986413 |
| 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 | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.179.110.160/27 | TESCOM | RIPE | ASSIGNED PA | ● low |
| 80.234.74.0/24 | TESCOM-NET | RIPE | ASSIGNED PA | ● low |
| 212.199.145.24/30 | Tescom-Ltd | 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 TESCOM 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.
| 80.234.74.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
AS9116-MNT
DUMY-RIPE
DUMY-RIPE
SAMTEL-MNT