GUP DNR UGLETELECOM

GUP DNR "UGLETELECOM"
BGP inherited
Cluster stats
Netblocks8
All fragments 110 blocks across 46 clusters
Cluster ID205570643
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-13

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.40.157.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.96.184.0/22 GUP DNR "UGLETELECOM" RIPE ASSIGNED PA ● high
176.96.184.0/22 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.96.184.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.96.185.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.96.186.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.96.187.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high
176.124.22.0/24 GUP DNR "UGLETELECOM" BGP ANNOUNCED ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (2)

These blocks are registered to GUP DNR "UGLETELECOM" 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.

176.96.186.0/24 /24 authorized for AS48276 — IPSvyaz OOO
176.96.187.0/24 /24 authorized for AS48276 — IPSvyaz OOO

NIC Handles

AS206810 DUMY-RIPE DUMY-RIPE LEVEL-MSK-MNT MTRX-ALCHEVSK-MNT ORG-USTA2-RIPE TIMERNET-MNT Timer-mnt Timer-mnt