bgpreport

Network · data from 2026-11-12

AS141796 VAYU ONLINE PRIVATE LIMITED

Registry name: VAYULTD-AS-IN - VAYU ONLINE PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141796, 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.
2407:4b40:5::/48 Valid Nonecovered by 2407:4b40::/32 636 100% 70
2407:4b40:ffff::/48 Valid Nonecovered by 2407:4b40::/32 1 0%low visibility 1
103.120.60.0/24 Valid RIR databaseAPNIC 672 100% 66
103.120.61.0/24 Valid RIR databaseAPNIC 672 100% 66
103.165.4.0/24 Valid RIR databaseAPNIC 672 100% 66
103.165.5.0/24 Valid RIR databaseAPNIC 672 100% 66
2407:4b40::/32 Valid RIR databaseAPNIC 636 100% 70
2407:4b40::/48 Valid RIR databaseAPNIC 636 100% 70
2407:4b40:1::/48 Valid RIR databaseAPNIC 636 100% 70
2407:4b40:2::/48 Valid RIR databaseAPNIC 636 100% 70
2407:4b40:3::/48 Valid RIR databaseAPNIC 636 100% 70
2407:4b40:4::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS141796's PeeringDB record names no 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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2407:4b40:5::/48No route object for it. A route object for 2407:4b40::/32 with origin AS141796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141796 in the RIR database for the space.636 of 636
Route object: none2407:4b40:ffff::/48No route object for it. A route object for 2407:4b40::/32 with origin AS141796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141796 in the RIR database for the space.1 of 636

Route objects not announced

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

103.120.60.0/23APNICValid
103.165.4.0/23APNICValid

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.