bgpreport

Network · data from 2026-11-12

AS138106 Lintas Telematika Nusantara

Registry name: LTN-AS-ID - PT Lintas Telematika Nusantara, ID · PeeringDB

7IPv4 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
2Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS138106, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138106, 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.126.9.0/24 Valid Other IRR onlyRADB 673 100% 70
103.126.10.0/24 Valid Other IRR onlyRADB 673 100% 70
103.126.11.0/24 Valid Other IRR onlyRADB 673 100% 70
114.199.92.0/24 Valid Other IRR onlyRADB 673 100% 68
103.126.8.0/24 Valid Other IRR onlyRADB 35 5%low visibility 29
161.248.116.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.126.8.0/22 Valid RIR databaseAPNIC, RADB 35 5%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS138106: AS138106:AS-CONE. 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 (AS138106 isn't in the set, or no route object for AS138106 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 objectsAS138106 in itNot covered
AS138106:AS-CONE RADB 118 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.

  • Route object: RIR5
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR103.126.9.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.126.10.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.126.11.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR114.199.92.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.126.8.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
AS-SET: own ASNAS138106:AS-CONEAS138106 isn't in AS138106:AS-CONE (RADB) once expanded. Add AS138106 to it.

Route objects not announced

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

103.126.8.0/23RADBValid
103.126.10.0/23RADBValid
2404:40::/32RADBNo 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.