bgpreport

Network · data from 2026-11-12

AS199161 PKO-NHO-AS OOO "PKO NEFTEHIMOBORUDOVANIE"

Registry name: PKO-NHO-AS OOO "PKO NEFTEHIMOBORUDOVANIE", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199161, 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.
194.169.255.0/24 No ROA RIR databaseRIPE 673 100% 67
194.169.255.40/30 No ROA RIR databaseRIPE 3 0%low visibility 2
194.169.255.80/30 No ROA RIR databaseRIPE 3 0%low visibility 2
194.169.255.216/29 No ROA RIR databaseRIPE 3 0%low visibility 2

AS-SET

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

  • ROA: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none194.169.255.0/24No ROA covers it. Add a ROA for AS199161, maxLength 24.673 of 673
ROA: none194.169.255.40/30No ROA covers it. Add a ROA for AS199161, maxLength 30.3 of 673
ROA: none194.169.255.80/30No ROA covers it. Add a ROA for AS199161, maxLength 30.3 of 673
ROA: none194.169.255.216/29No ROA covers it. Add a ROA for AS199161, maxLength 29.3 of 673

Route objects not announced

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

194.169.255.0/28RIPENo ROA
194.169.255.152/30RIPENo ROA
194.169.255.160/28RIPENo ROA
194.169.255.188/30RIPENo ROA
194.169.255.248/29RIPENo 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.