bgpreport

Network · data from 2026-11-12

AS137639 JASNET-AS

Registry name: JASNET-AS - Jasnet Networks Private Limited, IN · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS137639, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137639, 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.120.56.0/22 Valid RIR databaseAPNIC 672 100% 67
103.120.56.0/23 Valid RIR databaseAPNIC 672 100% 67
103.120.58.0/23 Valid RIR databaseAPNIC 672 100% 67
2403:5340::/32 Valid RIR databaseAPNIC 635 100% 69
2403:5340::/35 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS137639'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 17 are in fix.csv.

  • Route object: not announced17

Route objects not announced

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

103.120.56.0/24APNICValid
103.120.57.0/24APNICValid
103.120.58.0/24APNICValid
103.120.59.0/24APNICValid
2403:5340::/33APNICValid
2403:5340::/34APNICValid
2403:5340:2000::/35APNICValid
2403:5340:4000::/34APNICValid
2403:5340:4000::/35APNICValid
2403:5340:6000::/35APNICValid
2403:5340:8000::/33APNICValid
2403:5340:8000::/34APNICValid
2403:5340:8000::/35APNICValid
2403:5340:a000::/35APNICValid
2403:5340:c000::/34APNICValid
2403:5340:c000::/35APNICValid
2403:5340:e000::/35APNICValid

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.