IRTEL
Cluster stats
| Netblocks | 20 |
| All fragments | 22 blocks across 3 clusters |
| Cluster ID | 191880743 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
20
0 netblocks since 2026-07-05
2026-07-05
peak 20
2026-07-06
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.103.128.0/23 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 87.103.132.128/25 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.96.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.99.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.101.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.102.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.104.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.105.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.106.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.107.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.109.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.112.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.113.0/25 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.114.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.115.0/24 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.116.0/23 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.118.0/23 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.120.0/23 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.124.0/25 | IRTEL | RIPE | ASSIGNED PA | ● low |
| 195.46.125.0/24 | IRTEL | 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
(20 of 20)
Possible discrepancies (17)
These blocks are registered to IRTEL 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.
| 195.46.116.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.118.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.120.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
| 87.103.128.0/23 /23 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.96.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.101.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.104.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.105.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.106.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.107.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.109.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.115.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.99.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.102.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
| 195.46.114.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
+2 more — see the REST API
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT