bgpreport

Network · data from 2026-11-12

AS137678 Protoact Digital Network

Registry name: PDNPL-AS - Protoact Digital Network Pvt. Ltd., IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137678, 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.185.218.0/24 Invalid: origin Other origin only 5 1%low visibility 5
103.112.20.0/24 No ROA Other origin onlycovered by 103.112.20.0/22 3 0%low visibility 2
103.111.158.0/23 No ROA Other IRR onlyRADB 673 100% 66
103.112.20.0/22 No ROA Other IRR onlyRADB 673 100% 66
2407:1ac0::/32 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:2000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:4000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:6000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:8000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:a000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:c000::/35 No ROA Other IRR onlyRADB 636 100% 67
2407:1ac0:e000::/35 No ROA Other IRR onlyRADB 636 100% 67
103.111.158.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1
103.136.82.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
160.25.24.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.117.202.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
103.195.253.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.111.159.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.112.21.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.112.22.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.112.23.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.117.202.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.117.203.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.136.82.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
103.136.83.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
160.25.24.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2
160.25.25.0/24 Valid RIR databaseAPNIC, RADB 3 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS137678: AS137678:AS-PROTOACT-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS137678 isn't in the set, or no route object for AS137678 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS137678 in itNot covered
AS137678:AS-PROTOACT-TRANSIT RADBlists itself further down 213157 Yes 1
APNIC (also) 101626 Yes 1

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

  • ROA: origin1
  • ROA: none13
  • Route object: none2
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin103.185.218.0/24ROAs covering it name AS150088, not AS137678. If AS137678 should announce it, add a ROA for AS137678.5 of 673
Route object: none103.185.218.0/24Route objects for it name AS150088. Add a route object with origin AS137678 in the RIR database for the space.5 of 673
ROA: none103.112.20.0/24No ROA covers it. Add a ROA for AS137678, maxLength 24.3 of 673
Route object: none103.112.20.0/24Route objects for it name AS137126. A route object for 103.112.20.0/22 with origin AS137678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137678 in the RIR database for the space.3 of 673
ROA: none103.111.158.0/23No ROA covers it. Add a ROA for AS137678, maxLength 23.673 of 673
Route object: RIR103.111.158.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.112.20.0/22No ROA covers it. Add a ROA for AS137678, maxLength 22.673 of 673
Route object: RIR103.112.20.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2407:1ac0::/32No ROA covers it. Add a ROA for AS137678, maxLength 32.636 of 636
Route object: RIR2407:1ac0::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:2000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:2000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:4000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:4000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:6000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:6000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:8000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:8000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:a000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:a000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:c000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:c000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2407:1ac0:e000::/35No ROA covers it. Add a ROA for AS137678, maxLength 35.636 of 636
Route object: RIR2407:1ac0:e000::/35Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none103.111.158.0/24No ROA covers it. Add a ROA for AS137678, maxLength 24.1 of 673
Route object: RIR103.111.158.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

103.112.22.0/23APNIC, RADBValid
103.146.222.0/24APNIC, RADBValid

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.