bgpreport

Network · data from 2026-11-12

AS42867 NIOCI-AS National Iranian Oil Company PJSC

Registry name: NIOCI-AS National Iranian Oil Company PJSC, IR · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object
0IPv6 routes
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
1Route objects not announced registered with origin AS42867, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42867, 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.143.140.0/24 Valid Nonecovered by 194.143.140.0/23 671 100% 67
194.143.140.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
194.143.141.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS42867 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.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none194.143.140.0/24No route object for it. A route object for 194.143.140.0/23 with origin AS42867 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42867 in the RIR database for the space.671 of 673

Route objects not announced

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

94.184.94.0/23RIPEInvalid: origin

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.