bgpreport

Network · data from 2026-11-12

AS39089 Ugletelecom - AS39089

Registry name: UGLETELECOM-AS STATE UNITARY ENTERPRISE OF THE DONETSK PEOPLE'S REPUBLIC "UGLETELECOM", RU · PeeringDB

20IPv4 routes 40.0% RPKI valid · 40.0% with a route object
0IPv6 routes
12RPKI invalid 12 origin · 0 maxLength
0No ROA 12 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS39089, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39089, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

31.40.157.22/32 Invalid: origin None 1 0%low visibility 4
31.40.157.23/32 Invalid: origin None 1 0%low visibility 4
31.40.157.46/32 Invalid: origin None 1 0%low visibility 4
31.40.157.47/32 Invalid: origin None 1 0%low visibility 4
31.40.157.48/32 Invalid: origin None 1 0%low visibility 4
31.40.157.49/32 Invalid: origin None 1 0%low visibility 4
31.40.157.60/32 Invalid: origin None 1 0%low visibility 4
31.40.157.61/32 Invalid: origin None 1 0%low visibility 4
31.40.157.64/32 Invalid: origin None 1 0%low visibility 4
31.40.157.65/32 Invalid: origin None 1 0%low visibility 4
176.96.184.32/32 Invalid: origin None 1 0%low visibility 4
176.96.184.33/32 Invalid: origin None 1 0%low visibility 4
31.133.56.0/21 Valid RIR databaseRIPE 673 100% 66
31.133.56.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.57.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.58.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.61.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.62.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.63.0/24 Valid RIR databaseRIPE 673 100% 66
31.133.59.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS39089: AS39089:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS39089 isn't in the set, or no route object for AS39089 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS39089 in itNot covered
AS39089:AS-CUSTOMERS RIPElists itself further down3 member sets in no database: AS-DONCLIP, AS-MOLS, AS-MULTSYS 223801,737 Yes 12

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 31 are in fix.csv.

  • ROA: origin12
  • Route object: none12
  • AS-SET: missing member3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin31.40.157.22/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.22/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.23/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.23/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.46/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.46/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.47/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.47/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.48/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.48/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.49/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.49/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.60/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.60/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.61/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.61/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.64/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.64/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin31.40.157.65/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none31.40.157.65/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin176.96.184.32/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none176.96.184.32/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
ROA: origin176.96.184.33/32ROAs covering it name AS206810, not AS39089. If AS39089 should announce it, add a ROA for AS39089.1 of 673
Route object: none176.96.184.33/32No route object for it. Add a route object with origin AS39089 in the RIR database for the space.1 of 673
AS-SET: missing memberAS39089:AS-CUSTOMERSAS39089:AS-CUSTOMERS (RIPE) lists AS-DONCLIP; no IRR database read has it.
AS-SET: missing memberAS39089:AS-CUSTOMERSAS39089:AS-CUSTOMERS (RIPE) lists AS-MOLS; no IRR database read has it.
AS-SET: missing memberAS39089:AS-CUSTOMERSAS39089:AS-CUSTOMERS (RIPE) lists AS-MULTSYS; no IRR database read has it.

Route objects not announced

Route objects with origin AS39089 whose prefix no peer sees AS39089 announce. Many are kept on purpose (backup routes, space announced only in some places).

31.133.60.0/24RIPEValid
176.124.26.0/23RIPEValid
176.124.26.0/24RIPEValid
176.124.27.0/24RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.