bgpreport

Network · data from 2026-11-12

AS136842 PEMERINTAH PROVINSI PAPUA

Registry name: IDNIC-PEMPROV-PAPUA-AS-ID - PEMERINTAH PROVINSI PAPUA, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136842, 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.100.247.0/24 Valid Nonecovered by 103.100.246.0/23 672 100% 67
103.100.246.0/24 Valid Other IRR onlyRADB 673 100% 67
2405:bc0::/33 Valid Other IRR onlyALTDB, RADB 635 100% 67
2405:bc0:8000::/48 Valid Other IRR onlyALTDB, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS136842: AS136842. 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 (AS136842 isn't in the set, or no route object for AS136842 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 objectsAS136842 in itNot covered
AS136842 A single AS number, not a set: AS136842 (this network), 4 route objects.

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

  • Route object: none1
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none103.100.247.0/24No route object for it. A route object for 103.100.246.0/23 with origin AS136842 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136842 in the RIR database for the space.672 of 673
Route object: RIR103.100.246.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2405:bc0::/33Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2405:bc0:8000::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

103.100.246.0/23ALTDB, APNICNo 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.