ROS Telecom
BGP inherited
Cluster stats
| Netblocks | 10 |
| All fragments | 62 blocks across 25 clusters |
| Cluster ID | 204851821 |
| 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 | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
10
-16 netblocks since 2026-07-05
2026-07-05
peak 26
2026-07-13
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 187.16.217.187/32 | ROS Telecom | PEERINGDB | ASSIGNED | ● high |
| 187.16.221.238/32 | ROS Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::217:187/128 | ROS Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::221:238/128 | ROS Telecom | PEERINGDB | ASSIGNED | ● high |
| 79.134.205.128/30 | ROS-LAN | RIPE | ASSIGNED PA | ● low |
| 79.134.209.192/30 | ROS-LAN | RIPE | ASSIGNED PA | ● low |
| 194.247.73.192/26 | ROS-UK | RIPE | ASSIGNED PA | ● low |
| 194.247.83.204/30 | ROS-GOV-UK | RIPE | ASSIGNED PA | ● low |
| 213.147.49.224/28 | ROS-MED | RIPE | ASSIGNED PA | ● low |
| 213.241.54.184/29 | ROS-ZAK | 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
(10 of 10)
No discrepancies found among checked blocks.
NIC Handles
AS262317
AS5564-MNT
DUMY-RIPE
DUMY-RIPE
MTU-NOC
NETIA-MNT
OBIT-MNT