Network · data from 2026-11-12

AS136826 IDNIC-TITIKTM-AS-ID - PT TITIK TERANG MAKMUR

Registry name: IDNIC-TITIKTM-AS-ID - PT TITIK TERANG MAKMUR, ID · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 33.3% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

5No ROA 4 with no route object for this origin

4Low visibility seen by under 10% of full-table peers

2Route objects not announced registered with origin AS136826, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136826, 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.224.82.22/32	Invalid: origin	None	0 0%low visibility	1
150.129.82.0/23	No ROA	Other origin only	127 19%	48
112.142.192.0/21	No ROA	None	83 12%	39
102.220.88.0/22	No ROA	Other origin only	48 7%low visibility	30
211.102.152.0/22	No ROA	Other IRR onlyRADB	2 0%low visibility	2
211.102.156.0/22	No ROA	Other IRR onlyRADB	2 0%low visibility	2

103.224.82.22/32

Invalid: origin

None

0 0%low visibility

150.129.82.0/23

No ROA

Other origin only

127 19%

112.142.192.0/21

No ROA

None

83 12%

102.220.88.0/22

No ROA

Other origin only

48 7%low visibility

211.102.152.0/22

No ROA

Other IRR onlyRADB

2 0%low visibility

211.102.156.0/22

No ROA

Other IRR onlyRADB

2 0%low visibility

AS-SET

AS136826 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

ROA: origin1
ROA: none5
Route object: none4
Route object: RIR2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	103.224.82.22/32	ROAs covering it name AS932, AS6134, AS55933, not AS136826. If AS136826 should announce it, add a ROA for AS136826.	0 of 673
Route object: none	103.224.82.22/32	No route object for it. Add a route object with origin AS136826 in the RIR database for the space.	0 of 673
ROA: none	150.129.82.0/23	No ROA covers it. Add a ROA for AS136826, maxLength 23.	127 of 673
Route object: none	150.129.82.0/23	Route objects for it name AS24544, AS55933, AS133731. Add a route object with origin AS136826 in the RIR database for the space.	127 of 673
ROA: none	112.142.192.0/21	No ROA covers it. Add a ROA for AS136826, maxLength 21.	83 of 673
Route object: none	112.142.192.0/21	No route object for it. Add a route object with origin AS136826 in the RIR database for the space.	83 of 673
ROA: none	102.220.88.0/22	No ROA covers it. Add a ROA for AS136826, maxLength 22.	48 of 673
Route object: none	102.220.88.0/22	Route objects for it name AS328543. Add a route object with origin AS136826 in the RIR database for the space.	48 of 673
ROA: none	211.102.152.0/22	No ROA covers it. Add a ROA for AS136826, maxLength 22.	2 of 673
Route object: RIR	211.102.152.0/22	Route object only in RADB. Add it in the RIR database for the space.	2 of 673
ROA: none	211.102.156.0/22	No ROA covers it. Add a ROA for AS136826, maxLength 22.	2 of 673
Route object: RIR	211.102.156.0/22	Route object only in RADB. Add it in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

103.224.82.22/32

ROAs covering it name AS932, AS6134, AS55933, not AS136826. If AS136826 should announce it, add a ROA for AS136826.

0 of 673

Route object: none

103.224.82.22/32

No route object for it. Add a route object with origin AS136826 in the RIR database for the space.

0 of 673

ROA: none

150.129.82.0/23

No ROA covers it. Add a ROA for AS136826, maxLength 23.

127 of 673

Route object: none

150.129.82.0/23

Route objects for it name AS24544, AS55933, AS133731. Add a route object with origin AS136826 in the RIR database for the space.

127 of 673

ROA: none

112.142.192.0/21

No ROA covers it. Add a ROA for AS136826, maxLength 21.

83 of 673

Route object: none

112.142.192.0/21

No route object for it. Add a route object with origin AS136826 in the RIR database for the space.

83 of 673

ROA: none

102.220.88.0/22

No ROA covers it. Add a ROA for AS136826, maxLength 22.

48 of 673

Route object: none

102.220.88.0/22

Route objects for it name AS328543. Add a route object with origin AS136826 in the RIR database for the space.

48 of 673

ROA: none

211.102.152.0/22

No ROA covers it. Add a ROA for AS136826, maxLength 22.

2 of 673

Route object: RIR

211.102.152.0/22

Route object only in RADB. Add it in the RIR database for the space.

2 of 673

ROA: none

211.102.156.0/22

No ROA covers it. Add a ROA for AS136826, maxLength 22.

2 of 673

Route object: RIR

211.102.156.0/22

Route object only in RADB. Add it in the RIR database for the space.

2 of 673

Route objects not announced

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


103.118.212.0/22	RADB	Valid
103.118.216.0/22	RADB	Valid

103.118.212.0/22

RADB

Valid

103.118.216.0/22

RADB

Valid

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.