bgpreport

Network · data from 2026-11-12

AS137330 Pisangmas Rayatama Perkasa

Registry name: PMNET-AS-ID - PT Pisangmas Rayatama Perkasa, ID · PeeringDB

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

Announced routes

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

2402:aa40:1::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:2::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:3::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:4::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:5::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:6::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:7::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:8::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:9::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:10::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:11::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:12::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:13::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:14::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:15::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:16::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:17::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:18::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:19::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
2402:aa40:20::/48 Valid Nonecovered by 2402:aa40::/32 3 0%low visibility 3
103.112.136.0/23 Valid Other IRR onlyRADB 672 100% 69
103.112.136.0/24 Valid Other IRR onlyRADB 672 100% 69
103.112.137.0/24 Valid Other IRR onlyRADB 672 100% 69
103.112.138.0/24 Valid Other IRR onlyRADB 672 100% 69
2402:aa40::/32 Valid Other IRR onlyRADB 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS137330: AS137330:AS-SET-PMNET-ID. 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 (AS137330 isn't in the set, or no route object for AS137330 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 objectsAS137330 in itNot covered
AS137330:AS-SET-PMNET-ID In no IRR database read today.

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

  • Route object: none20
  • Route object: RIR5
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2402:aa40:1::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:2::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:3::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:4::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:5::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:6::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:7::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:8::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:9::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:10::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:11::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:12::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:13::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:14::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:15::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:16::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:17::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:18::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:19::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: none2402:aa40:20::/48No route object for it. A route object for 2402:aa40::/32 with origin AS137330 covers it (filters allowing more-specifics accept it). Add a route object with origin AS137330 in the RIR database for the space.3 of 636
Route object: RIR103.112.136.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.112.136.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.112.137.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.112.138.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2402:aa40::/32Route object only in RADB. Add it in the RIR database for the space.3 of 636
AS-SET: not foundAS137330:AS-SET-PMNET-IDPeeringDB names AS137330:AS-SET-PMNET-ID; no IRR database read has it.

Route objects not announced

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