Network · data from 2026-11-12
AS139661 TTPL-AS-AP - Toll Transport Pty Ltd.
Registry name: TTPL-AS-AP - Toll Transport Pty Ltd., AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139661, 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.
| 203.9.35.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.11.81.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 203.9.116.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.117.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 203.9.119.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 203.9.121.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 203.9.122.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.123.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.124.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.125.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.126.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.127.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 203.9.114.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS139661 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 20 are in fix.csv.
- ROA: none13
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.9.35.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| Route object: RIR | 203.9.35.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.11.81.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| Route object: RIR | 203.11.81.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.9.116.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.117.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.119.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.121.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.122.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.123.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.124.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.125.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.126.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.127.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
| ROA: none | 203.9.114.0/24 | No ROA covers it. Add a ROA for AS139661, maxLength 24. |
Route objects not announced
Route objects with origin AS139661 whose prefix no peer sees AS139661 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.9.115.0/24 | APNIC, RADB | No ROA |
| 203.9.118.0/24 | APNIC | No ROA |
| 203.9.120.0/24 | APNIC | No ROA |
| 203.9.122.0/23 | RADB | No ROA |
| 203.9.124.0/22 | 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.