Network · data from 2026-11-12
AS11133 SORENSON-99 - Sorenson Communications, Inc.
Registry name: SORENSON-99 - Sorenson Communications, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11133, 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.
| 65.37.249.0/24 | No ROA | Nonecovered by 65.37.240.0/20 | 672 100% |
| 65.37.251.0/24 | No ROA | Nonecovered by 65.37.240.0/20 | 672 100% |
| 65.37.255.0/24 | No ROA | Nonecovered by 65.37.240.0/20 | 672 100% |
| 209.169.226.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.230.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.231.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.238.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.240.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.243.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
| 209.169.244.0/24 | No ROA | Nonecovered by 209.169.224.0/19 | 672 100% |
AS-SET
AS11133 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: none10
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 65.37.249.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 65.37.249.0/24 | No route object for it. A route object for 65.37.240.0/20 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 65.37.251.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 65.37.251.0/24 | No route object for it. A route object for 65.37.240.0/20 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 65.37.255.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 65.37.255.0/24 | No route object for it. A route object for 65.37.240.0/20 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.226.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.226.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.230.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.230.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.231.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.231.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.238.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.238.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.240.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.240.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.243.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.243.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
| ROA: none | 209.169.244.0/24 | No ROA covers it. Add a ROA for AS11133, maxLength 24. |
| Route object: none | 209.169.244.0/24 | No route object for it. A route object for 209.169.224.0/19 with origin AS11133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11133 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11133 whose prefix no peer sees AS11133 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.37.240.0/20 | RADB | No ROA |
| 65.37.254.0/24 | RADB | No ROA |
| 209.169.224.0/19 | 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.