bgpreport

Network · data from 2026-11-12

AS135686 Navyug Networks Info Pvt Ltd

Registry name: NAVYUG-AS-IN - Navyug Networks Info Private Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135686, 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.
103.69.44.0/22 Valid RIR databaseAPNIC 672 100% 67
2406:29c0::/32 Valid RIR databaseAPNIC 635 100% 67
103.69.44.0/23 Valid RIR databaseAPNIC 10 1%low visibility 5
103.69.44.0/24 Valid RIR databaseAPNIC 10 1%low visibility 5
103.69.46.0/23 Valid RIR databaseAPNIC 10 1%low visibility 5
103.69.46.0/24 Valid RIR databaseAPNIC 10 1%low visibility 5

AS-SET

PeeringDB's irr_as_set for AS135686: AS135686:AS-NAVYUG. 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 (AS135686 isn't in the set, or no route object for AS135686 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 objectsAS135686 in itNot covered
AS135686:AS-NAVYUG APNIClists itself further down1 member set in no database: AS136346:AS-FASTTNET 9344 Yes 0

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

  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS135686:AS-NAVYUGAS135686:AS-NAVYUG (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.

Route objects not announced

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

103.69.45.0/24APNICValid
103.69.47.0/24APNICValid

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.