bgpreport

Network · data from 2026-11-12

AS211092 UCOM-Q Ucom CJSC

Registry name: UCOM-Q Ucom CJSC, AM · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211092, 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.
185.213.241.0/24 Invalid: origin Other origin only 1 0%low visibility 2

AS-SET

AS211092 isn't in PeeringDB, where networks name their AS-SET.

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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin185.213.241.0/24ROAs covering it name AS198969, not AS211092. If AS211092 should announce it, add a ROA for AS211092.1 of 673
Route object: none185.213.241.0/24Route objects for it name AS198969. Add a route object with origin AS211092 in the RIR database for the space.1 of 673

Route objects not announced

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

37.157.211.0/24RADB, RIPEValid

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.