bgpreport

Network · data from 2026-11-12

AS206810 UGLETELECOM

Registry name: UGLETELECOM GUP DNR "UGLETELECOM", RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206810, 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: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.23/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.46/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.47/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.48/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.49/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.60/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.61/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.64/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
31.40.157.65/32 Invalid: maxLength Nonecovered by 31.40.157.0/24 3 0%low visibility 6
176.96.184.32/32 Invalid: maxLength Nonecovered by 176.96.184.0/24 3 0%low visibility 6
176.96.184.33/32 Invalid: maxLength Nonecovered by 176.96.184.0/24 3 0%low visibility 6
31.40.157.0/24 Valid RIR databaseRIPE 673 100% 66
176.96.184.0/22 Valid RIR databaseRIPE 673 100% 66
176.96.184.0/24 Valid RIR databaseRIPE 673 100% 66
176.96.185.0/24 Valid RIR databaseRIPE 673 100% 66
176.96.186.0/24 Valid RIR databaseRIPE 673 100% 66
176.96.187.0/24 Valid RIR databaseRIPE 673 100% 66
176.124.22.0/24 Valid RIR databaseRIPE 668 99% 66

AS-SET

PeeringDB's irr_as_set for AS206810: AS206810: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 (AS206810 isn't in the set, or no route object for AS206810 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 objectsAS206810 in itNot covered
AS206810:AS-CUSTOMERS RIPElists itself further down3 member sets in no database: AS-DONCLIP, AS-MOLS, AS-MULTSYS 235851,825 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 29 are in fix.csv.

  • ROA: maxLength12
  • Route object: none12
  • AS-SET: missing member3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength31.40.157.22/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.22/32.3 of 673
Route object: none31.40.157.22/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.23/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.23/32.3 of 673
Route object: none31.40.157.23/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.46/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.46/32.3 of 673
Route object: none31.40.157.46/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.47/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.47/32.3 of 673
Route object: none31.40.157.47/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.48/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.48/32.3 of 673
Route object: none31.40.157.48/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.49/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.49/32.3 of 673
Route object: none31.40.157.49/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.60/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.60/32.3 of 673
Route object: none31.40.157.60/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.61/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.61/32.3 of 673
Route object: none31.40.157.61/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.64/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.64/32.3 of 673
Route object: none31.40.157.64/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength31.40.157.65/32ROA 31.40.157.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.40.157.65/32.3 of 673
Route object: none31.40.157.65/32No route object for it. A route object for 31.40.157.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength176.96.184.32/32ROA 176.96.184.0/22 AS206810 has maxLength 22; ROA 176.96.184.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.96.184.32/32.3 of 673
Route object: none176.96.184.32/32No route object for it. A route object for 176.96.184.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
ROA: maxLength176.96.184.33/32ROA 176.96.184.0/22 AS206810 has maxLength 22; ROA 176.96.184.0/24 AS206810 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.96.184.33/32.3 of 673
Route object: none176.96.184.33/32No route object for it. A route object for 176.96.184.0/24 with origin AS206810 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206810 in the RIR database for the space.3 of 673
AS-SET: missing memberAS206810:AS-CUSTOMERSAS206810:AS-CUSTOMERS (RIPE) lists AS-DONCLIP; no IRR database read has it.
AS-SET: missing memberAS206810:AS-CUSTOMERSAS206810:AS-CUSTOMERS (RIPE) lists AS-MOLS; no IRR database read has it.
AS-SET: missing memberAS206810:AS-CUSTOMERSAS206810:AS-CUSTOMERS (RIPE) lists AS-MULTSYS; no IRR database read has it.

Route objects not announced

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

176.124.22.0/23RIPEValid
176.124.23.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.