bgpreport

Network · data from 2026-11-12

AS136642 Aerocast Networks

Registry name: AEROCAT-AS-IN - Aerocast Networks Private Limited, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136642, 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.85.140.0/24 Valid None 672 100% 66
103.85.141.0/24 Valid None 672 100% 67
103.97.184.0/24 Valid RIR databaseAPNIC 672 100% 67
103.97.186.0/24 Valid RIR databaseAPNIC 672 100% 67
103.97.187.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS136642'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 6 are in fix.csv.

  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none103.85.140.0/24No route object for it. Add a route object with origin AS136642 in the RIR database for the space.672 of 673
Route object: none103.85.141.0/24No route object for it. Add a route object with origin AS136642 in the RIR database for the space.672 of 673

Route objects not announced

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

103.97.184.0/22APNICValid
103.97.184.0/23APNICValid
103.97.185.0/24APNICValid
103.97.186.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.