Network · data from 2026-11-12
AS24211 Detik Ini Juga
Registry name: DETIK-AS-ID - PT. Detik Ini JUga, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24211, 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.
| 2402:a000::/34 | Valid | Nonecovered by 2402:a000::/32 | 636 100% |
| 2402:a000:8000::/34 | Valid | Nonecovered by 2402:a000::/32 | 636 100% |
| 2402:a000:c000::/34 | Valid | Nonecovered by 2402:a000::/32 | 636 100% |
| 203.190.240.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 203.190.242.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 203.190.247.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.49.220.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.49.222.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.190.244.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.190.246.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.49.220.0/22 | Valid | RIR databaseAPNIC, RADB | 35 5%low visibility |
| 203.190.240.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 35 5%low visibility |
AS-SET
AS24211'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 17 are in fix.csv.
- Route object: none3
- Route object: RIR3
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2402:a000::/34 | No route object for it. A route object for 2402:a000::/32 with origin AS24211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24211 in the RIR database for the space. |
| Route object: none | 2402:a000:8000::/34 | No route object for it. A route object for 2402:a000::/32 with origin AS24211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24211 in the RIR database for the space. |
| Route object: none | 2402:a000:c000::/34 | No route object for it. A route object for 2402:a000::/32 with origin AS24211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24211 in the RIR database for the space. |
| Route object: RIR | 203.190.240.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.242.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.190.247.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24211 whose prefix no peer sees AS24211 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.190.240.0/22 | RADB | Valid |
| 203.190.240.0/24 | NTTCOM, RADB | Valid |
| 203.190.241.0/24 | NTTCOM, RADB | Valid |
| 203.190.242.0/24 | NTTCOM, RADB | Valid |
| 203.190.243.0/24 | NTTCOM, RADB | Valid |
| 203.190.244.0/24 | NTTCOM, RADB | Valid |
| 203.190.245.0/24 | NTTCOM, RADB | Valid |
| 203.190.246.0/24 | NTTCOM, RADB | Valid |
| 2402:a000::/32 | APNIC, RADB | Valid |
| 2402:a000::/48 | APNIC, RADB | Valid |
| 2402:a000:fffe::/48 | APNIC, 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.