bgpreport

Network · data from 2026-11-12

AS131749 Arthatama Adhiprima Persada

Registry name: MEDIAINDOCYBER-AS-ID - PT. Arthatama Adhiprima Persada, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131749, 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.
2402:be80::/35 Valid Nonecovered by 2402:be80::/34 2 0%low visibility 4
2402:be80:2000::/35 Valid Nonecovered by 2402:be80::/34 2 0%low visibility 4
2402:be80:4000::/35 Valid Nonecovered by 2402:be80:4000::/34 2 0%low visibility 4
2402:be80:6000::/35 Valid Nonecovered by 2402:be80:4000::/34 2 0%low visibility 4
2402:be80:8000::/35 Valid Nonecovered by 2402:be80:8000::/34 2 0%low visibility 4
2402:be80:a000::/35 Valid Nonecovered by 2402:be80:8000::/34 2 0%low visibility 4
2402:be80:c000::/35 Valid Nonecovered by 2402:be80:c000::/34 2 0%low visibility 4
2402:be80:e000::/35 Valid Nonecovered by 2402:be80:c000::/34 2 0%low visibility 4
103.31.132.0/22 Valid RIR databaseAPNIC, NTTCOM 673 100% 68
103.31.132.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 68
103.31.132.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.31.133.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.31.134.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.31.134.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
103.31.135.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
2402:be80::/32 Valid RIR databaseAPNIC 635 100% 69
2402:be80:d9ab::/48 Valid RIR databaseAPNIC 635 100% 69
2402:be80::/33 Valid RIR databaseAPNIC 634 100% 69
2402:be80:8000::/33 Valid RIR databaseAPNIC 634 100% 69
2402:be80:c000::/34 Valid RIR databaseAPNIC 41 6%low visibility 29
2402:be80:4000::/34 Valid RIR databaseAPNIC 40 6%low visibility 29
2402:be80:8000::/34 Valid RIR databaseAPNIC 37 6%low visibility 30
2402:be80::/34 Valid RIR databaseAPNIC 34 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS131749: AS131749:AS-INDOCYBER. 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 (AS131749 isn't in the set, or no route object for AS131749 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 objectsAS131749 in itNot covered
AS131749:AS-INDOCYBER APNIC 4124 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 12 are in fix.csv.

  • Route object: none8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2402:be80::/35No route object for it. A route object for 2402:be80::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:2000::/35No route object for it. A route object for 2402:be80::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:4000::/35No route object for it. A route object for 2402:be80:4000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:6000::/35No route object for it. A route object for 2402:be80:4000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:8000::/35No route object for it. A route object for 2402:be80:8000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:a000::/35No route object for it. A route object for 2402:be80:8000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:c000::/35No route object for it. A route object for 2402:be80:c000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636
Route object: none2402:be80:e000::/35No route object for it. A route object for 2402:be80:c000::/34 with origin AS131749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131749 in the RIR database for the space.2 of 636

Route objects not announced

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

2402:be80::/48APNICInvalid: maxLength
2402:be80:1::/48APNICInvalid: maxLength
2402:be80:2::/48APNICInvalid: maxLength
2402:be80:3::/48APNICInvalid: maxLength

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.