Network · data from 2026-11-12
AS58396 DETELNET
Registry name: DETELNETWORKS-ID - PT. DEWATA TELEMATIKA, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58396, 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.23.141.0/24 | Invalid: origin | Other origin only | 13 2%low visibility |
| 2400:9c80::/48 | Valid | Nonecovered by 2400:9c80::/32 | 635 100% |
| 2400:9c80:4::/48 | Valid | Nonecovered by 2400:9c80::/32 | 635 100% |
| 2400:9c80:2000::/48 | Valid | Nonecovered by 2400:9c80::/32 | 635 100% |
| 2400:9c80:d7e1::/48 | Valid | Nonecovered by 2400:9c80::/32 | 635 100% |
| 27.54.116.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 27.54.117.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 27.54.118.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.11.21.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.11.222.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS58396: AS58396:AS-DETELNETWORKS-ID. 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 (AS58396 isn't in the set, or no route object for AS58396 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 | AS58396 in it | Not covered |
|---|---|---|---|---|---|
| AS58396:AS-DETELNETWORKS-ID | APNIC1 member set in no database: AS-JELAJAHID-ID | 157 | 1 | Yes | 1 |
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 15 are in fix.csv.
- ROA: origin1
- Route object: none5
- AS-SET: missing member1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.23.141.0/24 | ROAs covering it name AS58401, not AS58396. If AS58396 should announce it, add a ROA for AS58396. |
| Route object: none | 103.23.141.0/24 | Route objects for it name AS23947, AS58401. Add a route object with origin AS58396 in the RIR database for the space. |
| Route object: none | 2400:9c80::/48 | No route object for it. A route object for 2400:9c80::/32 with origin AS58396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58396 in the RIR database for the space. |
| Route object: none | 2400:9c80:4::/48 | No route object for it. A route object for 2400:9c80::/32 with origin AS58396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58396 in the RIR database for the space. |
| Route object: none | 2400:9c80:2000::/48 | No route object for it. A route object for 2400:9c80::/32 with origin AS58396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58396 in the RIR database for the space. |
| Route object: none | 2400:9c80:d7e1::/48 | No route object for it. A route object for 2400:9c80::/32 with origin AS58396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58396 in the RIR database for the space. |
| AS-SET: missing member | AS58396:AS-DETELNETWORKS-ID | AS58396:AS-DETELNETWORKS-ID (APNIC) lists AS-JELAJAHID-ID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS58396 whose prefix no peer sees AS58396 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.11.222.0/23 | NTTCOM | No ROA |
| 103.225.172.0/23 | APNIC, RADB | Valid |
| 103.225.172.0/24 | APNIC, RADB | Valid |
| 2400:9c80::/32 | RADB | Valid |
| 2400:9c80:2::/48 | RADB | Valid |
| 2400:9c80:a::/48 | RADB | Valid |
| 2400:9c80:200::/40 | RADB | Valid |
| 2400:9c80:400::/38 | 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.