Network · data from 2026-11-12
AS24183 DTS New Zealand Limited
Registry name: DTS-ISP-Core1-AP - DTS LTD, NZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24183, 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.
| 202.174.181.0/24 | Invalid: maxLength | Nonecovered by 202.174.176.0/20 | 3 0%low visibility |
| 113.130.123.0/24 | No ROA | None | 671 100% |
| 45.125.168.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.111.76.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.226.32.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.226.35.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.20.0.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 202.68.80.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 202.174.176.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 202.174.176.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 2402:9e00::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9e00:400::/48 | Valid | RIR databaseAPNIC | 337 53% |
| 2402:9e00:401::/48 | Valid | RIR databaseAPNIC | 337 53% |
| 2402:9e00:402::/48 | Valid | RIR databaseAPNIC | 337 53% |
AS-SET
PeeringDB's irr_as_set for AS24183: AS24183:AS-DTSLTD. 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 (AS24183 isn't in the set, or no route object for AS24183 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 | AS24183 in it | Not covered |
|---|---|---|---|---|---|
| AS24183:AS-DTSLTD | APNIC | 13 | 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 12 are in fix.csv.
- ROA: maxLength1
- ROA: none1
- Route object: none2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 202.174.181.0/24 | ROA 202.174.176.0/20 AS24183 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 202.174.181.0/24. |
| Route object: none | 202.174.181.0/24 | No route object for it. A route object for 202.174.176.0/20 with origin AS24183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24183 in the RIR database for the space. |
| ROA: none | 113.130.123.0/24 | No ROA covers it. Add a ROA for AS24183, maxLength 24. |
| Route object: none | 113.130.123.0/24 | No route object for it. Add a route object with origin AS24183 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24183 whose prefix no peer sees AS24183 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.226.32.0/23 | APNIC | Valid |
| 103.226.34.0/24 | APNIC | Valid |
| 202.27.88.0/23 | RADB | No ROA |
| 202.27.90.0/24 | RADB | No ROA |
| 202.36.137.0/24 | RADB | No ROA |
| 202.36.172.0/23 | RADB | No ROA |
| 202.36.173.0/24 | RADB | No ROA |
| 2403:cc00:a000::/36 | 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.