bgpreport

Network · data from 2026-11-12

AS137661 RISL-AS-IN - Rajcomp Info Services Ltd.

Registry name: RISL-AS-IN - Rajcomp Info Services Ltd., IN · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS137661, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137661, 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.

2403:89c0:2::/48 No ROA Nonecovered by 2403:89c0::/32 636 100% 70
2403:89c0:1::/48 No ROA Nonecovered by 2403:89c0::/32 635 100% 70
103.122.39.0/24 Valid RIR databaseAPNIC 673 100% 66
103.122.37.0/24 Valid RIR databaseAPNIC 670 100% 67
103.122.36.0/24 Valid RIR databaseAPNIC 669 99% 67
103.122.38.0/24 Valid RIR databaseAPNIC 669 99% 67

AS-SET

AS137661 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2403:89c0:2::/48No ROA covers it. Add a ROA for AS137661, maxLength 48.636 of 636
Route object: none2403:89c0:2::/48No route object for it. A route object for 2403:89c0::/32 with origin AS137661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137661 in the RIR database for the space.636 of 636
ROA: none2403:89c0:1::/48No ROA covers it. Add a ROA for AS137661, maxLength 48.635 of 636
Route object: none2403:89c0:1::/48No route object for it. A route object for 2403:89c0::/32 with origin AS137661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137661 in the RIR database for the space.635 of 636

Route objects not announced

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

103.122.36.0/22APNICValid
103.122.36.0/23APNICValid
103.122.38.0/23APNICValid
2403:89c0::/32APNICNo ROA

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.