bgpreport

Network · data from 2026-11-12

AS150506 PT Pusat Fiber Indonesia

Registry name: IDNIC-PFI-AS-ID - PT Pusat Fiber Indonesia, ID · PeeringDB

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

Announced routes

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

113.59.232.0/24 Invalid: origin Other origin only 7 1%low visibility 5
113.59.233.0/24 Invalid: origin Other origin only 7 1%low visibility 5
113.59.234.0/24 Invalid: origin Other origin only 7 1%low visibility 5
113.59.235.0/24 Invalid: origin Other origin only 7 1%low visibility 5
113.59.236.0/24 Invalid: origin Other origin only 7 1%low visibility 5
202.57.26.0/24 Valid Other IRR onlyRADB 214 32% 55
202.57.27.0/24 Valid Other IRR onlyRADB 213 32% 55

AS-SET

PeeringDB's irr_as_set for AS150506: AS-PFI. 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 (AS150506 isn't in the set, or no route object for AS150506 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 objectsAS150506 in itNot covered
AS-PFI RADB3 member sets in no database: AS-LINTASDATA-AS-ID, AS-PEDJOEANG-ISP, AS63883:AS-CLOUDSERVERS 5042316,793 Yes 5

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

  • ROA: origin5
  • Route object: none5
  • Route object: RIR2
  • AS-SET: missing member3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin113.59.232.0/24ROAs covering it name AS45296, not AS150506. If AS150506 should announce it, add a ROA for AS150506.7 of 673
Route object: none113.59.232.0/24Route objects for it name AS45296. Add a route object with origin AS150506 in the RIR database for the space.7 of 673
ROA: origin113.59.233.0/24ROAs covering it name AS45296, not AS150506. If AS150506 should announce it, add a ROA for AS150506.7 of 673
Route object: none113.59.233.0/24Route objects for it name AS45296. Add a route object with origin AS150506 in the RIR database for the space.7 of 673
ROA: origin113.59.234.0/24ROAs covering it name AS45296, not AS150506. If AS150506 should announce it, add a ROA for AS150506.7 of 673
Route object: none113.59.234.0/24Route objects for it name AS45296. Add a route object with origin AS150506 in the RIR database for the space.7 of 673
ROA: origin113.59.235.0/24ROAs covering it name AS45296, not AS150506. If AS150506 should announce it, add a ROA for AS150506.7 of 673
Route object: none113.59.235.0/24Route objects for it name AS45296. Add a route object with origin AS150506 in the RIR database for the space.7 of 673
ROA: origin113.59.236.0/24ROAs covering it name AS45296, not AS150506. If AS150506 should announce it, add a ROA for AS150506.7 of 673
Route object: none113.59.236.0/24Route objects for it name AS45296. Add a route object with origin AS150506 in the RIR database for the space.7 of 673
Route object: RIR202.57.26.0/24Route object only in RADB. Add it in the RIR database for the space.214 of 673
Route object: RIR202.57.27.0/24Route object only in RADB. Add it in the RIR database for the space.213 of 673
AS-SET: missing memberAS-PFIAS-PFI (RADB) lists AS-LINTASDATA-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-PFIAS-PFI (RADB) lists AS-PEDJOEANG-ISP; no IRR database read has it.
AS-SET: missing memberAS-PFIAS-PFI (RADB) lists AS63883:AS-CLOUDSERVERS; no IRR database read has it.

Route objects not announced

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

103.61.226.0/23APNICValid

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.