Network · data from 2026-11-12
AS23734 Netrouting Asia Pacific
Registry name: NETROUTINGINC-AS-AP - Netrouting Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23734, 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.
| 192.142.16.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.165.242.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS23734: AS-NETROUTING:AS-NETROUTING-AP. 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 (AS23734 isn't in the set, or no route object for AS23734 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 | AS23734 in it | Not covered |
|---|---|---|---|---|---|
| AS-NETROUTING:AS-NETROUTING-AP | RIPE | 1 | 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 192.142.16.0/24 | ROAs covering it name AS212238, not AS23734. If AS23734 should announce it, add a ROA for AS23734. |
| Route object: none | 192.142.16.0/24 | Route objects for it name AS212238. Add a route object with origin AS23734 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23734 whose prefix no peer sees AS23734 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.101.0.0/23 | APNIC | Valid |
| 103.101.0.0/24 | APNIC | Valid |
| 103.101.1.0/24 | APNIC | Valid |
| 202.90.16.0/20 | RADB | No ROA |
| 2401:df40:1::/48 | APNIC | 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.