bgpreport

Network · data from 2026-11-12

AS133095 PUSAT FIBER INDONESIA - NAP

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133095, 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.
202.57.25.0/24 Valid Other IRR onlyRADB 672 100% 68
103.61.226.0/24 Valid Other IRR onlyRADB 670 100% 68
103.61.227.0/24 Valid Other IRR onlyRADB 670 100% 68
202.57.24.0/24 Valid Other IRR onlyRADB 670 100% 68
2001:df7:2140::/48 Valid Other IRR onlyRADB 630 99% 69

AS-SET

PeeringDB's irr_as_set for AS133095: AS-PFI-NAP. 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 (AS133095 isn't in the set, or no route object for AS133095 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 objectsAS133095 in itNot covered
AS-PFI-NAP RADB4 member sets in no database: AS-LINTASDATA-AS-ID, AS-PEDJOEANG-ISP, AS-WKPLUS-ISP, AS63883:AS-CLOUDSERVERS 5122348,049 Yes 0

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

  • Route object: RIR5
  • AS-SET: missing member4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR202.57.25.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.61.226.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.61.227.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.57.24.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2001:df7:2140::/48Route object only in RADB. Add it in the RIR database for the space.630 of 636
AS-SET: missing memberAS-PFI-NAPAS-PFI-NAP (RADB) lists AS-LINTASDATA-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-PFI-NAPAS-PFI-NAP (RADB) lists AS-PEDJOEANG-ISP; no IRR database read has it.
AS-SET: missing memberAS-PFI-NAPAS-PFI-NAP (RADB) lists AS-WKPLUS-ISP; no IRR database read has it.
AS-SET: missing memberAS-PFI-NAPAS-PFI-NAP (RADB) lists AS63883:AS-CLOUDSERVERS; no IRR database read has it.

Route objects not announced

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

103.61.226.0/23APNIC, RADBValid
103.255.54.0/24NTTCOMNo ROA
2001:470:4b0::/48ARINValid
2001:470:612::/48ARINValid

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.