Network · data from 2026-11-12
AS32059 TRADESTATION-1 - TradeStation Securities, Inc
Registry name: TRADESTATION-1 - TradeStation Securities, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32059, 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.
| 8.17.18.0/24 | No ROA | None | 673 100% |
| 63.99.207.0/24 | No ROA | None | 673 100% |
| 63.99.254.0/24 | No ROA | None | 673 100% |
| 199.58.59.0/24 | No ROA | Other origin only | 673 100% |
| 199.58.60.0/24 | No ROA | Other origin only | 673 100% |
| 199.58.61.0/24 | No ROA | Other origin only | 673 100% |
| 199.58.62.0/24 | No ROA | Other origin only | 673 100% |
| 65.211.211.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.58.57.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 199.58.63.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS32059 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 23 are in fix.csv.
- ROA: none10
- Route object: none7
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.17.18.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 8.17.18.0/24 | No route object for it. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 63.99.207.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 63.99.207.0/24 | No route object for it. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 63.99.254.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 63.99.254.0/24 | No route object for it. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 199.58.59.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 199.58.59.0/24 | Route objects for it name AS46633. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 199.58.60.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 199.58.60.0/24 | Route objects for it name AS46633. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 199.58.61.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 199.58.61.0/24 | Route objects for it name AS46633. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 199.58.62.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: none | 199.58.62.0/24 | Route objects for it name AS46633. Add a route object with origin AS32059 in the RIR database for the space. |
| ROA: none | 65.211.211.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: RIR | 65.211.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.58.57.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: RIR | 199.58.57.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 199.58.63.0/24 | No ROA covers it. Add a ROA for AS32059, maxLength 24. |
| Route object: RIR | 199.58.63.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32059 whose prefix no peer sees AS32059 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.74.235.0/24 | RADB | No ROA |
| 72.5.192.0/24 | RADB | No ROA |
| 74.201.12.0/24 | 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.