bgpreport

Network · data from 2026-11-12

AS141082 Trikamedia

Registry name: IDNIC-TRIKANET-AS-ID - PT Trika Global Media, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141082, 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.
2406:8140::/32 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.251.9.0/24 Valid Nonecovered by 103.251.8.0/23 672 100% 69
103.156.74.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.156.74.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.251.8.0/24 Valid Other IRR onlyRADB 673 100% 69
103.156.75.0/24 Valid Other IRR onlyRADB 672 100% 69
103.251.8.0/23 Valid Other IRR onlyRADB 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS141082: AS141082:AS-TRIKANET. 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 (AS141082 isn't in the set, or no route object for AS141082 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 objectsAS141082 in itNot covered
AS141082:AS-TRIKANET APNIC 3111 No 7

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR6
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none2406:8140::/32No ROA covers it. Add a ROA for AS141082, maxLength 32.2 of 636
Route object: RIR2406:8140::/32Route object only in NTTCOM. Add it in the RIR database for the space.2 of 636
Route object: none103.251.9.0/24No route object for it. A route object for 103.251.8.0/23 with origin AS141082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141082 in the RIR database for the space.672 of 673
Route object: RIR103.156.74.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.156.74.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.251.8.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.156.75.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.251.8.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: own ASNAS141082:AS-TRIKANETAS141082 isn't in AS141082:AS-TRIKANET (APNIC) once expanded. Add AS141082 to it.

Route objects not announced

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