bgpreport

Network · data from 2026-11-12

AS137670 CANBANK-AS - Canara Bank

Registry name: CANBANK-AS - Canara Bank, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137670, 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.
186.244.165.0/24 Invalid: origin Other origin only 139 21% 52
103.122.53.0/24 No ROA None 673 100% 67
2404:a800:3002::/48 No ROA None 636 100% 70
2001:df6:8101::/48 No ROA None 634 100% 68
103.129.204.0/24 No ROA RIR databaseAPNIC 673 100% 66
2001:df6:8100::/48 No ROA RIR databaseAPNIC 636 100% 70
59.144.189.0/24 Valid RIR databaseAPNIC 673 100% 66
59.145.68.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

AS137670 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 10 are in fix.csv.

  • ROA: origin1
  • ROA: none5
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin186.244.165.0/24ROAs covering it name AS9498, not AS137670. If AS137670 should announce it, add a ROA for AS137670.139 of 673
Route object: none186.244.165.0/24Route objects for it name AS9498. Add a route object with origin AS137670 in the RIR database for the space.139 of 673
ROA: none103.122.53.0/24No ROA covers it. Add a ROA for AS137670, maxLength 24.673 of 673
Route object: none103.122.53.0/24No route object for it. Add a route object with origin AS137670 in the RIR database for the space.673 of 673
ROA: none2404:a800:3002::/48No ROA covers it. Add a ROA for AS137670, maxLength 48.636 of 636
Route object: none2404:a800:3002::/48No route object for it. Add a route object with origin AS137670 in the RIR database for the space.636 of 636
ROA: none2001:df6:8101::/48No ROA covers it. Add a ROA for AS137670, maxLength 48.634 of 636
Route object: none2001:df6:8101::/48No route object for it. Add a route object with origin AS137670 in the RIR database for the space.634 of 636
ROA: none103.129.204.0/24No ROA covers it. Add a ROA for AS137670, maxLength 24.673 of 673
ROA: none2001:df6:8100::/48No ROA covers it. Add a ROA for AS137670, maxLength 48.636 of 636

Route objects not announced

Every route object with origin AS137670 is announced.

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.