bgpreport

Network · data from 2026-11-12

AS137130 Punjab National Bank

Registry name: ITDPNB-AS - Punjab National Bank, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137130, 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.
1.7.228.0/24 Invalid: origin Other origin only 20 3%low visibility 9
1.6.219.0/24 Invalid: origin Other origin only 16 2%low visibility 9
1.7.178.0/24 Invalid: origin Other origin only 16 2%low visibility 9
1.7.190.0/24 Invalid: origin Other origin only 16 2%low visibility 9
103.109.224.0/24 Valid RIR databaseAPNIC 673 100% 66
103.109.225.0/24 Valid RIR databaseAPNIC 673 100% 66
103.122.156.0/24 Valid RIR databaseAPNIC 673 100% 66
103.109.226.0/24 Valid RIR databaseAPNIC 672 100% 67
103.109.227.0/24 Valid RIR databaseAPNIC 672 100% 67
2001:df1:1580::/48 Valid RIR databaseAPNIC 636 100% 70
2403:9140::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS137130'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 8 are in fix.csv.

  • ROA: origin4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin1.7.228.0/24ROAs covering it name AS9583, not AS137130. If AS137130 should announce it, add a ROA for AS137130.20 of 673
Route object: none1.7.228.0/24Route objects for it name AS9583. Add a route object with origin AS137130 in the RIR database for the space.20 of 673
ROA: origin1.6.219.0/24ROAs covering it name AS9583, not AS137130. If AS137130 should announce it, add a ROA for AS137130.16 of 673
Route object: none1.6.219.0/24Route objects for it name AS9583. Add a route object with origin AS137130 in the RIR database for the space.16 of 673
ROA: origin1.7.178.0/24ROAs covering it name AS9583, not AS137130. If AS137130 should announce it, add a ROA for AS137130.16 of 673
Route object: none1.7.178.0/24Route objects for it name AS9583. Add a route object with origin AS137130 in the RIR database for the space.16 of 673
ROA: origin1.7.190.0/24ROAs covering it name AS9583, not AS137130. If AS137130 should announce it, add a ROA for AS137130.16 of 673
Route object: none1.7.190.0/24Route objects for it name AS9583. Add a route object with origin AS137130 in the RIR database for the space.16 of 673

Route objects not announced

Every route object with origin AS137130 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.