UGLETELECOM
Handle
Cluster stats
| Netblocks | 7 |
| Registered in | Russia (4) · AG (1) |
| All fragments | 14 blocks across 2 clusters |
| Cluster ID | 213187302 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.44.186.124/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.172/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.0.13.181/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.153.225/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 193.27.37.195/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 193.27.38.17/32 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:172/128 | UGLETELECOM | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “UGLETELECOM” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Ugletelecom - AS39089 7 blocks
Network trust
what's this?
RPKI hygiene: F
how networks compare →
14.3%
of checked blocks have valid RPKI ROA coverage
(1 of 7)
No discrepancies found among checked blocks.
NIC Handles
AS206810