bgpreport

Network · data from 2026-11-12

AS131705 PT Aneka Teguh Jaya

Registry name: ANEKANET-AS-ID - PT Aneka Teguh Jaya, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131705, 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.154.179.0/24 Valid None 673 100% 69
2406:5c40:2000::/36 Valid Nonecovered by 2406:5c40::/32 636 100% 70
2406:5c40:9999::/48 Valid Nonecovered by 2406:5c40::/32 636 100% 70
2406:5c40::/36 Valid Nonecovered by 2406:5c40::/32 635 100% 69
2406:5c40:7777::/48 Valid Nonecovered by 2406:5c40::/32 635 100% 69
2406:5c40:1000::/36 Valid Nonecovered by 2406:5c40::/32 634 100% 67
2406:5c40:8888::/48 Valid Nonecovered by 2406:5c40::/32 634 100% 67
103.23.196.0/24 Valid Other IRR onlyRADB 673 100% 70
103.154.178.0/24 Valid Other IRR onlyRADB 669 99% 67
103.23.197.0/24 Valid Other IRR onlyRADB 137 20% 48
103.23.196.0/23 Valid Other IRR onlyRADB 135 20% 46

AS-SET

PeeringDB's irr_as_set for AS131705: APNIC::AS131705:AS-ANEKANET. 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 (AS131705 isn't in the set, or no route object for AS131705 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 objectsAS131705 in itNot covered
APNIC::AS131705:AS-ANEKANET APNIC 2123 No 11

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

  • Route object: none7
  • Route object: RIR4
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none103.154.179.0/24No route object for it. Add a route object with origin AS131705 in the RIR database for the space.673 of 673
Route object: none2406:5c40:2000::/36No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.636 of 636
Route object: none2406:5c40:9999::/48No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.636 of 636
Route object: none2406:5c40::/36No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.635 of 636
Route object: none2406:5c40:7777::/48No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.635 of 636
Route object: none2406:5c40:1000::/36No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.634 of 636
Route object: none2406:5c40:8888::/48No route object for it. A route object for 2406:5c40::/32 with origin AS131705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131705 in the RIR database for the space.634 of 636
Route object: RIR103.23.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.154.178.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.23.197.0/24Route object only in RADB. Add it in the RIR database for the space.137 of 673
Route object: RIR103.23.196.0/23Route object only in RADB. Add it in the RIR database for the space.135 of 673
AS-SET: own ASNAPNIC::AS131705:AS-ANEKANETAS131705 isn't in AS131705:AS-ANEKANET (APNIC) once expanded. Add AS131705 to it.

Route objects not announced

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

103.18.44.0/24APNICInvalid: origin
2406:5c40::/32RADBValid

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.