Network · data from 2026-11-12
AS40355 SUNDANCE-NET - Sundance International LLC
Registry name: SUNDANCE-NET - Sundance International LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40355, 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.
| 199.244.91.0/24 | Valid | Nonecovered by 199.244.88.0/22 | 673 100% |
| 199.244.88.0/24 | Valid | Nonecovered by 199.244.88.0/22 | 671 100% |
| 199.244.89.0/24 | Valid | Nonecovered by 199.244.88.0/22 | 671 100% |
| 199.244.90.0/24 | Valid | Other origin onlycovered by 199.244.88.0/22 | 479 71% |
| 205.153.99.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.38.229.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.38.230.0/24 | Valid | RIR databaseARIN | 673 100% |
| 205.153.96.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.38.228.0/24 | Valid | RIR databaseARIN | 671 100% |
| 216.38.231.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS40355 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 11 are in fix.csv.
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 199.244.91.0/24 | No route object for it. A route object for 199.244.88.0/22 with origin AS40355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40355 in the RIR database for the space. |
| Route object: none | 199.244.88.0/24 | No route object for it. A route object for 199.244.88.0/22 with origin AS40355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40355 in the RIR database for the space. |
| Route object: none | 199.244.89.0/24 | No route object for it. A route object for 199.244.88.0/22 with origin AS40355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40355 in the RIR database for the space. |
| Route object: none | 199.244.90.0/24 | Route objects for it name AS42926. A route object for 199.244.88.0/22 with origin AS40355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40355 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40355 whose prefix no peer sees AS40355 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.244.88.0/22 | ARIN, RADB | Valid |
| 205.153.96.0/22 | ARIN | Valid |
| 205.153.97.0/24 | ARIN | Valid |
| 205.153.98.0/24 | ARIN | Valid |
| 216.38.228.0/22 | ARIN | Invalid: origin |
| 2001:470:11c::/48 | ARIN | Valid |
| 2607:e680::/32 | ARIN | 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.