Network · data from 2026-11-12
AS10208 THENET
Registry name: THENET-AS-ID-AP - PT. Millenium Internetindo, ID · PeeringDB
6IPv4 routes
0.0% RPKI valid · 100.0% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
7No ROA
0 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
61Route objects not announced
registered with origin AS10208, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS10208, 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.
| 202.153.128.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.153.140.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 202.153.138.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 669 99% |
| 2406:9600::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 202.153.128.0/21 | No ROA | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.153.140.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
| 202.153.144.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 35 5%low visibility |
AS-SET
AS10208'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 75 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced61
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.153.128.0/19 | No ROA covers it. Add a ROA for AS10208, maxLength 19. |
| Route object: RIR | 202.153.128.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.153.140.0/23 | No ROA covers it. Add a ROA for AS10208, maxLength 23. |
| Route object: RIR | 202.153.140.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.153.138.0/23 | No ROA covers it. Add a ROA for AS10208, maxLength 23. |
| Route object: RIR | 202.153.138.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2406:9600::/32 | No ROA covers it. Add a ROA for AS10208, maxLength 32. |
| Route object: RIR | 2406:9600::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.153.128.0/21 | No ROA covers it. Add a ROA for AS10208, maxLength 21. |
| Route object: RIR | 202.153.128.0/21 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.153.140.0/24 | No ROA covers it. Add a ROA for AS10208, maxLength 24. |
| Route object: RIR | 202.153.140.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.153.144.0/20 | No ROA covers it. Add a ROA for AS10208, maxLength 20. |
| Route object: RIR | 202.153.144.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10208 whose prefix no peer sees AS10208 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.116.90.0/23 | NTTCOM, RADB | No ROA |
| 45.116.90.0/24 | NTTCOM, RADB | No ROA |
| 45.116.91.0/24 | NTTCOM, RADB | No ROA |
| 103.228.248.0/24 | REACH | Invalid: origin |
| 202.153.128.0/20 | NTTCOM, RADB | No ROA |
| 202.153.128.0/22 | NTTCOM, RADB | No ROA |
| 202.153.128.0/23 | NTTCOM, RADB | No ROA |
| 202.153.128.0/24 | NTTCOM, RADB | No ROA |
| 202.153.129.0/24 | NTTCOM, RADB | No ROA |
| 202.153.130.0/23 | NTTCOM, RADB | No ROA |
| 202.153.130.0/24 | NTTCOM, RADB | No ROA |
| 202.153.131.0/24 | NTTCOM, RADB | No ROA |
| 202.153.132.0/22 | NTTCOM, RADB | No ROA |
| 202.153.132.0/23 | NTTCOM, RADB | No ROA |
| 202.153.132.0/24 | NTTCOM, RADB | No ROA |
| 202.153.133.0/24 | NTTCOM, RADB | No ROA |
| 202.153.134.0/23 | NTTCOM, RADB | No ROA |
| 202.153.134.0/24 | NTTCOM, RADB | No ROA |
| 202.153.135.0/24 | NTTCOM, RADB | No ROA |
| 202.153.136.0/21 | NTTCOM, RADB | No ROA |
| 202.153.136.0/22 | NTTCOM, RADB | No ROA |
| 202.153.136.0/23 | NTTCOM, RADB | No ROA |
| 202.153.136.0/24 | NTTCOM, RADB | No ROA |
| 202.153.137.0/24 | NTTCOM, RADB | No ROA |
| 202.153.138.0/24 | NTTCOM, RADB | No ROA |
| 202.153.139.0/24 | NTTCOM, RADB | No ROA |
| 202.153.140.0/22 | NTTCOM, RADB | No ROA |
| 202.153.141.0/24 | NTTCOM, RADB | No ROA |
| 202.153.142.0/23 | NTTCOM, RADB | No ROA |
| 202.153.142.0/24 | NTTCOM, RADB | No ROA |
| 202.153.143.0/24 | NTTCOM, RADB | No ROA |
| 202.153.144.0/21 | NTTCOM, RADB | No ROA |
| 202.153.144.0/22 | NTTCOM, RADB | No ROA |
| 202.153.144.0/23 | NTTCOM, RADB | No ROA |
| 202.153.144.0/24 | NTTCOM, RADB | No ROA |
| 202.153.145.0/24 | NTTCOM, RADB | No ROA |
| 202.153.146.0/23 | NTTCOM, RADB | No ROA |
| 202.153.146.0/24 | NTTCOM, RADB | No ROA |
| 202.153.147.0/24 | NTTCOM, RADB | No ROA |
| 202.153.148.0/22 | NTTCOM, RADB | No ROA |
| 202.153.148.0/23 | NTTCOM, RADB | No ROA |
| 202.153.148.0/24 | NTTCOM, RADB | No ROA |
| 202.153.149.0/24 | NTTCOM, RADB | No ROA |
| 202.153.150.0/23 | NTTCOM, RADB | No ROA |
| 202.153.150.0/24 | NTTCOM, RADB | No ROA |
| 202.153.151.0/24 | NTTCOM, RADB | No ROA |
| 202.153.152.0/21 | NTTCOM, RADB | No ROA |
| 202.153.152.0/22 | NTTCOM, RADB | No ROA |
| 202.153.152.0/23 | NTTCOM, RADB | No ROA |
| 202.153.152.0/24 | NTTCOM, RADB | No ROA |
| 202.153.153.0/24 | NTTCOM, RADB | No ROA |
| 202.153.154.0/23 | NTTCOM, RADB | No ROA |
| 202.153.154.0/24 | NTTCOM, RADB | No ROA |
| 202.153.155.0/24 | NTTCOM, RADB | No ROA |
| 202.153.156.0/22 | NTTCOM, RADB | No ROA |
| 202.153.156.0/23 | NTTCOM, RADB | No ROA |
| 202.153.156.0/24 | NTTCOM, RADB | No ROA |
| 202.153.157.0/24 | NTTCOM, RADB | No ROA |
| 202.153.158.0/23 | NTTCOM, RADB | No ROA |
| 202.153.158.0/24 | NTTCOM, RADB | No ROA |
| 202.153.159.0/24 | NTTCOM, RADB | No 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.