bgpreport

Network · data from 2026-11-12

AS38770 Tangara Mitrakom

Registry name: TM-AS-ID - PT. Tangara Mitrakom, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38770, 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.
114.134.64.0/21 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.64.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.65.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.66.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.69.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.70.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
114.134.71.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69

AS-SET

AS38770's PeeringDB record names no AS-SET.

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

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none114.134.64.0/21No ROA covers it. Add a ROA for AS38770, maxLength 21.673 of 673
Route object: RIR114.134.64.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.64.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.64.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.65.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.65.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.66.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.66.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.69.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.69.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.70.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.70.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none114.134.71.0/24No ROA covers it. Add a ROA for AS38770, maxLength 24.673 of 673
Route object: RIR114.134.71.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

114.134.64.0/22NTTCOM, RADBNo ROA
114.134.64.0/23NTTCOM, RADBNo ROA
114.134.66.0/23NTTCOM, RADBNo ROA
114.134.67.0/24NTTCOM, RADBNo ROA
114.134.68.0/22NTTCOM, RADBNo ROA
114.134.68.0/23NTTCOM, RADBNo ROA
114.134.68.0/24NTTCOM, RADBNo ROA
114.134.70.0/23NTTCOM, RADBNo ROA
116.68.248.0/21NTTCOMNo ROA
116.68.248.0/22NTTCOMNo ROA
116.68.248.0/23NTTCOMNo ROA
116.68.250.0/23NTTCOMNo ROA
116.68.252.0/22NTTCOMNo ROA
116.68.252.0/23NTTCOMNo ROA
116.68.254.0/23NTTCOMNo ROA
203.1.25.0/24NTTCOMNo 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.