bgpreport

Network · data from 2026-11-12

AS56258 PGAS TELEKOMUNIKASI NUSANTARA AS56258

Registry name: PGAS-AS-ID - PT. PGAS TELEKOMUNIKASI NUSANTARA, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56258, 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.28.93.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.243.48.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.243.51.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.28.94.0/24 Valid RIR databaseAPNIC 670 100% 66
103.28.95.0/24 Valid RIR databaseAPNIC 35 5%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS56258: AS56258:AS-PGAS-IX. 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 (AS56258 isn't in the set, or no route object for AS56258 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 objectsAS56258 in itNot covered
AS56258:AS-PGAS-IX RADBlists itself further down13 member sets in no database: AS-BCMEDIA, AS-BOSTI, AS-KDINDO, AS-LINTASDATA-AS-ID, AS-NETCITI … 1,61195118,186 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 17 are in fix.csv.

  • AS-SET: missing member13
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS-BCMEDIA; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS-BOSTI; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS-KDINDO; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS-LINTASDATA-AS-ID; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS-NETCITI; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS135454:AS-AXAGOID; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS150196:AS-ARTHALOKA-ID; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS150238:AS-SHARTEL; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS150249:AS-ATHARVA; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS150501:AS-HCI; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS150552:AS-BAROKAHNET; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS63883:AS-CLOUDSERVERS; no IRR database read has it.
AS-SET: missing memberAS56258:AS-PGAS-IXAS56258:AS-PGAS-IX (RADB) lists AS9251:AS-INTERLINK; no IRR database read has it.

Route objects not announced

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

103.10.223.0/24APNICNo ROA
103.28.104.0/24APNICValid
103.243.48.0/22RADBNo ROA
103.243.49.0/24RADBNo 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.