Network · data from 2026-11-12
AS140026 PT. KUPANG INTERMEDIA
Registry name: TIMORNET-AS-ID - PT. KUPANG INTERMEDIA, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140026, 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.
| 38.172.143.0/24 | Valid | Other IRR onlyALTDB, RADB | 673 100% |
| 103.149.178.0/24 | Valid | Other IRR onlyALTDB, RADB | 673 100% |
| 103.149.179.0/24 | Valid | Other IRR onlyALTDB, RADB | 672 100% |
| 38.172.142.0/24 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 38.50.166.0/23 | Valid | RIR databaseALTDB, ARIN, RADB | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS140026: AS140026:AS-CONE. 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 (AS140026 isn't in the set, or no route object for AS140026 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 | AS140026 in it | Not covered |
|---|---|---|---|---|---|
| AS140026:AS-CONE | RADB | 10 | 2 | 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 10 are in fix.csv.
- Route object: RIR4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 38.172.143.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.149.178.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.149.179.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 38.172.142.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140026 whose prefix no peer sees AS140026 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.172.142.0/23 | ALTDB, ARIN, RADB | Valid |
| 103.149.178.0/23 | NTTCOM | Valid |
| 2405:ee40::/32 | NTTCOM | No ROA |
| 2405:ee40::/48 | RADB | No ROA |
| 2405:ee40:1400::/48 | RADB | No ROA |
| 2405:ee40:dada::/48 | 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.