bgpreport

Network · data from 2026-11-12

AS209788 CONVEX-REGIONS LLC Cifrovie Seti Urala

Registry name: CONVEX-REGIONS LLC Cifrovie Seti Urala, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209788, 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.
192.54.186.0/23 Invalid: origin Other origin only 84 12% 39
95.183.44.0/23 Valid RIR databaseRIPE 673 100% 66
95.183.46.0/24 Valid RIR databaseRIPE 673 100% 66
188.68.80.0/24 Valid RIR databaseRIPE 673 100% 66
188.68.90.0/24 Valid RIR databaseRIPE 673 100% 66
188.68.91.0/24 Valid RIR databaseRIPE 673 100% 66
188.68.92.0/24 Valid RIR databaseRIPE 673 100% 66
188.68.93.0/24 Valid RIR databaseRIPE 673 100% 66
192.54.76.0/24 Valid RIR databaseRIPE 673 100% 66
192.54.77.0/24 Valid RIR databaseRIPE 673 100% 66
192.54.187.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin192.54.186.0/23ROAs covering it name AS209307, not AS209788. If AS209788 should announce it, add a ROA for AS209788.84 of 673
Route object: none192.54.186.0/23Route objects for it name AS209307. Add a route object with origin AS209788 in the RIR database for the space.84 of 673

Route objects not announced

Every route object with origin AS209788 is announced.

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.