bgpreport

Network · data from 2026-11-12

AS154466 OJI COMMUNICATIONS PRIVATE LIMITED

Registry name: IRINN-OJI001-AS-IN - OJI COMMUNICATIONS PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154466, 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.
2402:5220::/32 No ROA None 634 100% 68
103.80.155.0/24 Valid RIR databaseAPNIC 672 100% 67
103.204.1.0/24 Valid RIR databaseAPNIC 672 100% 67
103.80.152.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.0.0/24 Valid RIR databaseAPNIC 671 100% 66
144.79.198.0/23 Valid RIR databaseAPNIC 671 100% 66
144.79.198.0/24 Valid RIR databaseAPNIC 671 100% 66
144.79.199.0/24 Valid RIR databaseAPNIC 671 100% 66
103.204.0.0/23 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS154466: AS154466:AS-OJI001. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS154466 isn't in the set, or no route object for AS154466 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS154466 in itNot covered
AS154466:AS-OJI001 APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 7147420,801 Yes 1

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: none1
  • Route object: none1
  • AS-SET: missing member5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2402:5220::/32No ROA covers it. Add a ROA for AS154466, maxLength 32.634 of 636
Route object: none2402:5220::/32No route object for it. Add a route object with origin AS154466 in the RIR database for the space.634 of 636
AS-SET: missing memberAS154466:AS-OJI001AS154466:AS-OJI001 (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS154466:AS-OJI001AS154466:AS-OJI001 (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS154466:AS-OJI001AS154466:AS-OJI001 (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS154466:AS-OJI001AS154466:AS-OJI001 (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS154466:AS-OJI001AS154466:AS-OJI001 (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

2001:df1:2740::/48APNICValid
2400:ff20::/32APNICValid

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.