bgpreport

Network · data from 2026-11-12

AS141983 Rajeg Media Telekomunikasi

Registry name: IDNIC-RAJEGNET-AS-ID - PT Rajeg Media Telekomunikasi, ID · PeeringDB

6IPv4 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
0Route objects not announced registered with origin AS141983, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141983, 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.
2407:9cc0::/32 Valid Other IRR onlyALTDB, RADB 633 100% 69
38.72.138.0/23 Valid RIR databaseALTDB, ARIN, RADB 673 100% 68
38.106.187.0/24 Valid RIR databaseALTDB, ARIN, RADB 673 100% 68
103.167.170.0/23 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
103.167.170.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
103.167.171.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
38.248.19.0/24 Valid RIR databaseALTDB, ARIN, RADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS141983: RADB::AS141983:AS-RAJEGNET. 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 (AS141983 isn't in the set, or no route object for AS141983 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 objectsAS141983 in itNot covered
RADB::AS141983:AS-RAJEGNET RADB7 member sets in no database: AS-JALABYTE-ISP, AS-PEDJOEANG-ISP, AS135465:AS-BTSNET-ID, AS135636:AS-RACKH, AS149744:AS-MISQOT … 4062236,197 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 8 are in fix.csv.

  • Route object: RIR1
  • AS-SET: missing member7
ChangePrefix or setDetailFull-table peers
Route object: RIR2407:9cc0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.633 of 636
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS-JALABYTE-ISP; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS-PEDJOEANG-ISP; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS135465:AS-BTSNET-ID; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS135636:AS-RACKH; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS149744:AS-MISQOT; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS152830:AS-EXATEL; no IRR database read has it.
AS-SET: missing memberRADB::AS141983:AS-RAJEGNETAS141983:AS-RAJEGNET (RADB) lists AS200177:AS-ATLANTIC; no IRR database read has it.

Route objects not announced

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