bgpreport

Network · data from 2026-11-12

AS35021 E-STOCK-AS MB Information Protection LLC

Registry name: E-STOCK-AS MB Information Protection LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35021, 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.
85.118.176.0/23 No ROA Nonecovered by 85.118.176.0/21 672 100% 67
85.118.181.0/24 No ROA Other origin onlycovered by 85.118.176.0/21 372 55% 64
193.232.39.0/24 No ROA Other origin only 302 45% 62
85.118.176.0/21 No ROA RIR databaseRIPE 673 100% 67
85.118.179.0/24 No ROA RIR databaseRIPE 673 100% 67
85.118.178.0/24 No ROA RIR databaseRIPE 672 100% 67
85.118.180.0/24 No ROA RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none85.118.176.0/23No ROA covers it. Add a ROA for AS35021, maxLength 23.672 of 673
Route object: none85.118.176.0/23No route object for it. A route object for 85.118.176.0/21 with origin AS35021 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35021 in the RIR database for the space.672 of 673
ROA: none85.118.181.0/24No ROA covers it. Add a ROA for AS35021, maxLength 24.372 of 673
Route object: none85.118.181.0/24Route objects for it name AS48009. A route object for 85.118.176.0/21 with origin AS35021 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35021 in the RIR database for the space.372 of 673
ROA: none193.232.39.0/24No ROA covers it. Add a ROA for AS35021, maxLength 24.302 of 673
Route object: none193.232.39.0/24Route objects for it name AS48009. Add a route object with origin AS35021 in the RIR database for the space.302 of 673
ROA: none85.118.176.0/21No ROA covers it. Add a ROA for AS35021, maxLength 21.673 of 673
ROA: none85.118.179.0/24No ROA covers it. Add a ROA for AS35021, maxLength 24.673 of 673
ROA: none85.118.178.0/24No ROA covers it. Add a ROA for AS35021, maxLength 24.672 of 673
ROA: none85.118.180.0/24No ROA covers it. Add a ROA for AS35021, maxLength 24.672 of 673

Route objects not announced

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

85.118.176.0/24RIPENo ROA
85.118.177.0/24RIPENo ROA
85.118.183.0/24RIPENo ROA

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.