Network · data from 2026-11-12
AS24195 Dhecyber Flow Indonesia - ISP
Registry name: DHECYBER-AS-ID - PT. Dhecyber Flow Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24195, 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.
| 118.91.128.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 118.91.130.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 118.91.133.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.67.8.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 202.67.10.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 202.67.12.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 202.67.14.0/23 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 670 100% |
| 118.91.128.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 118.91.129.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 118.91.130.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 118.91.131.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 118.91.132.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 118.91.132.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.8.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.67.8.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.9.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.10.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.11.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.12.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.67.12.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.13.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.14.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 202.67.15.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 670 100% |
| 2401:4200::/32 | Valid | RIR databaseAPNIC, NTTCOM | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS24195: AS24195:AS-DHECYBER-NET. 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 (AS24195 isn't in the set, or no route object for AS24195 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.
| Name | Database | ASNs | Sets | AS24195 in it | Not covered |
|---|---|---|---|---|---|
| AS24195:AS-DHECYBER-NET | RADB | 2 | 1 | Yes | 0 |
| APNIC (also) | 3 | 1 | Yes | 0 |
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 36 are in fix.csv.
- Route object: RIR7
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 118.91.128.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 118.91.130.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 118.91.133.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.67.8.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.67.10.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.67.12.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.67.14.0/23 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24195 whose prefix no peer sees AS24195 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 117.103.8.0/21 | NTTCOM, RADB | No ROA |
| 118.91.128.0/20 | APNIC, NTTCOM, RADB | No ROA |
| 118.91.128.0/21 | APNIC, NTTCOM, RADB | Valid |
| 118.91.128.0/22 | NTTCOM, RADB | Valid |
| 118.91.132.0/22 | NTTCOM, RADB | Valid |
| 118.91.134.0/23 | NTTCOM, RADB | Valid |
| 118.91.134.0/24 | APNIC, NTTCOM, RADB | Valid |
| 118.91.135.0/24 | APNIC, NTTCOM, RADB | Valid |
| 118.91.136.0/21 | NTTCOM, RADB | No ROA |
| 118.91.136.0/22 | APNIC, NTTCOM, RADB | No ROA |
| 118.91.136.0/23 | NTTCOM, RADB | No ROA |
| 118.91.136.0/24 | NTTCOM, RADB | No ROA |
| 118.91.137.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 118.91.138.0/23 | NTTCOM, RADB | No ROA |
| 118.91.138.0/24 | NTTCOM, RADB | No ROA |
| 118.91.139.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 202.67.7.0/24 | NTTCOM, RADB | No ROA |
| 202.67.8.0/21 | APNIC, NTTCOM, RADB | Valid |
| 202.67.32.0/20 | NTTCOM, RADB | No ROA |
| 202.93.224.0/20 | NTTCOM, RADB | No ROA |
| 202.93.240.0/21 | NTTCOM, RADB | No ROA |
| 202.123.224.0/20 | NTTCOM, RADB | No ROA |
| 202.148.0.0/19 | NTTCOM, RADB | No ROA |
| 202.159.0.0/17 | NTTCOM, RADB | No ROA |
| 202.160.254.0/24 | NTTCOM, RADB | No ROA |
| 202.180.48.0/21 | RADB | No ROA |
| 203.201.160.0/20 | NTTCOM, RADB | No ROA |
| 2401:4200::/48 | NTTCOM | Valid |
| 2401:4200:0:ff::/64 | APNIC | Invalid: maxLength |
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.