bgpreport

Network · data from 2026-11-12

AS8774 Etype OOO Kompaniya Etype

Registry name: Etype OOO Kompaniya Etype, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8774, 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.113.210.0/24 Valid Nonecovered by 185.113.208.0/22 673 100% 66
109.237.0.0/22 Valid RIR databaseRIPE 673 100% 66
109.237.4.0/22 Valid RIR databaseRIPE 673 100% 66
109.237.8.0/22 Valid RIR databaseRIPE 673 100% 66
109.237.12.0/22 Valid RIR databaseRIPE 673 100% 66
185.113.208.0/23 Valid RIR databaseRIPE 673 100% 66
185.113.211.0/24 Valid RIR databaseRIPE 673 100% 66
195.135.212.0/24 Valid RIR databaseRIPE 673 100% 66
195.135.213.0/24 Valid RIR databaseRIPE 673 100% 66
195.135.214.0/24 Valid RIR databaseRIPE 673 100% 66
195.135.215.0/24 Valid RIR databaseRIPE 673 100% 66
2a05:3740::/29 Valid RIR databaseRIPE 635 100% 68

AS-SET

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

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none185.113.210.0/24No route object for it. A route object for 185.113.208.0/22 with origin AS8774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8774 in the RIR database for the space.673 of 673

Route objects not announced

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

109.237.0.0/20RIPENo ROA
185.113.208.0/22RIPENo ROA
195.135.212.0/22RADB, RIPENo ROA
195.135.212.0/23RIPENo 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.