Network · data from 2026-11-12
AS36321 CSTL - Castle Global Inc.
Registry name: CSTL - Castle Global Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36321, 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.
| 64.124.8.0/24 | Valid | Other origin only | 673 100% |
| 199.83.232.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 66.187.0.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 74.80.208.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 199.184.214.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 2620:4e:e000::/48 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
AS36321 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 4 are in fix.csv.
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 64.124.8.0/24 | Route objects for it name AS26552. Add a route object with origin AS36321 in the RIR database for the space. |
| Route object: RIR | 199.83.232.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36321 whose prefix no peer sees AS36321 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.74.128.0/24 | RADB | No ROA |
| 66.187.0.0/25 | RADB | 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.