bgpreport

Network · data from 2026-11-12

AS134913 Jetway Broadband India Pvt Ltd

Registry name: JETWAYBROADBANDINDIA-AS - JETWAY BROADBAND INDIA PVT LTD, IN · PeeringDB

20IPv4 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
7Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS134913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134913, 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.
27.96.88.0/22 Valid Other IRR onlyRADB 672 100% 67
103.211.112.0/22 Valid Other IRR onlyRADB 672 100% 67
160.238.76.0/22 Valid Other IRR onlyRADB 672 100% 67
103.50.76.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.50.76.0/24 Valid RIR databaseAPNIC 672 100% 67
103.50.77.0/24 Valid RIR databaseAPNIC 672 100% 67
103.50.78.0/24 Valid RIR databaseAPNIC 672 100% 67
103.211.114.0/24 Valid RIR databaseAPNIC 672 100% 67
160.238.76.0/24 Valid RIR databaseAPNIC 672 100% 67
160.238.77.0/24 Valid RIR databaseAPNIC 672 100% 67
27.96.89.0/24 Valid RIR databaseAPNIC 671 100% 67
27.96.90.0/24 Valid RIR databaseAPNIC 671 100% 67
27.96.91.0/24 Valid RIR databaseAPNIC 671 100% 67
2402:57c0::/32 Valid RIR databaseAPNIC 635 100% 67
27.96.88.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.50.79.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.211.112.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.211.113.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.211.115.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
160.238.78.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
160.238.79.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29

AS-SET

AS134913'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 5 are in fix.csv.

  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR27.96.88.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.211.112.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.76.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.50.76.0/23APNICValid
103.50.78.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.