Network · data from 2026-11-12
AS45929 NEXTHOP-AS-AP - NextHop Pty Ltd
Registry name: NEXTHOP-AS-AP - NextHop Pty Ltd, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45929, 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.
| 45.159.244.0/23 | Valid | None | 672 100% |
| 84.247.24.0/24 | Valid | None | 672 100% |
| 84.247.27.0/24 | Valid | None | 672 100% |
| 94.103.248.0/24 | Valid | Other origin only | 672 100% |
| 94.103.251.0/24 | Valid | Other origin only | 672 100% |
| 136.144.24.0/24 | Valid | None | 672 100% |
| 185.184.132.0/23 | Valid | None | 672 100% |
| 185.205.188.0/24 | Valid | None | 672 100% |
| 45.143.52.0/24 | Valid | Other origin only | 671 100% |
| 45.143.55.0/24 | Valid | Other origin only | 671 100% |
| 45.82.4.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.88.84.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.92.4.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.92.88.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.132.120.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.149.192.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 91.188.204.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.112.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 185.255.36.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 188.240.224.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 193.23.128.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 195.38.4.0/22 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 213.232.92.0/22 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS45929 isn't in PeeringDB, where networks name their AS-SET.
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: none10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.159.244.0/23 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 84.247.24.0/24 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 84.247.27.0/24 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 94.103.248.0/24 | Route objects for it name AS39855. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 94.103.251.0/24 | Route objects for it name AS39855. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 136.144.24.0/24 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 185.184.132.0/23 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 185.205.188.0/24 | No route object for it. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 45.143.52.0/24 | Route objects for it name AS39855. Add a route object with origin AS45929 in the RIR database for the space. |
| Route object: none | 45.143.55.0/24 | Route objects for it name AS39855. Add a route object with origin AS45929 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS45929 is announced.
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.