Network · data from 2026-11-12
AS13340 RIML-CORP-AS-3 - BlackBerry Limited
Registry name: RIML-CORP-AS-3 - BlackBerry Limited, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13340, 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.
| 93.186.16.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.246.201.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.246.202.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 178.239.80.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 195.3.172.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.51.26.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 67.223.67.0/24 | Valid | Nonecovered by 67.223.64.0/19 | 673 100% |
| 68.171.230.0/24 | Valid | Nonecovered by 68.171.224.0/19 | 673 100% |
| 68.171.240.0/21 | Valid | Nonecovered by 68.171.224.0/19 | 673 100% |
| 206.53.152.0/22 | Valid | Nonecovered by 206.53.152.0/21 | 673 100% |
| 206.53.156.0/22 | Valid | Nonecovered by 206.53.152.0/21 | 673 100% |
| 208.65.72.0/24 | Valid | Nonecovered by 208.65.72.0/21 | 673 100% |
| 74.82.72.0/24 | Valid | Nonecovered by 74.82.64.0/19 | 672 100% |
| 74.82.81.0/24 | Valid | Nonecovered by 74.82.64.0/19 | 672 100% |
| 74.82.82.0/24 | Valid | Nonecovered by 74.82.64.0/19 | 672 100% |
| 74.82.86.0/24 | Valid | Nonecovered by 74.82.64.0/19 | 672 100% |
| 74.82.93.0/24 | Valid | Nonecovered by 74.82.64.0/19 | 672 100% |
| 216.9.248.0/22 | Valid | Nonecovered by 216.9.248.0/21 | 2 0%low visibility |
| 208.65.74.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 208.65.78.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 74.82.68.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 67.223.68.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 67.223.64.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 68.171.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 74.82.64.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 173.247.32.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 206.53.144.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.65.72.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.93.72.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.93.73.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.93.74.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 208.93.76.0/23 | Valid | RIR databaseARIN | 673 100% |
| 216.9.240.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.9.248.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 206.53.152.0/21 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
AS-SET
AS13340 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 33 are in fix.csv.
- ROA: none6
- Route object: none12
- Route object: RIR10
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 93.186.16.0/20 | No ROA covers it. Add a ROA for AS13340, maxLength 20. |
| Route object: RIR | 93.186.16.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.246.201.0/24 | No ROA covers it. Add a ROA for AS13340, maxLength 24. |
| Route object: RIR | 103.246.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.246.202.0/23 | No ROA covers it. Add a ROA for AS13340, maxLength 23. |
| Route object: RIR | 103.246.202.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 178.239.80.0/20 | No ROA covers it. Add a ROA for AS13340, maxLength 20. |
| Route object: RIR | 178.239.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 195.3.172.0/22 | No ROA covers it. Add a ROA for AS13340, maxLength 22. |
| Route object: RIR | 195.3.172.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.51.26.0/24 | No ROA covers it. Add a ROA for AS13340, maxLength 24. |
| Route object: RIR | 206.51.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 67.223.67.0/24 | No route object for it. A route object for 67.223.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 68.171.230.0/24 | No route object for it. A route object for 68.171.224.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 68.171.240.0/21 | No route object for it. A route object for 68.171.224.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 206.53.152.0/22 | No route object for it. A route object for 206.53.152.0/21 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 206.53.156.0/22 | No route object for it. A route object for 206.53.152.0/21 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 208.65.72.0/24 | No route object for it. A route object for 208.65.72.0/21 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 74.82.72.0/24 | No route object for it. A route object for 74.82.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 74.82.81.0/24 | No route object for it. A route object for 74.82.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 74.82.82.0/24 | No route object for it. A route object for 74.82.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 74.82.86.0/24 | No route object for it. A route object for 74.82.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 74.82.93.0/24 | No route object for it. A route object for 74.82.64.0/19 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: none | 216.9.248.0/22 | No route object for it. A route object for 216.9.248.0/21 with origin AS13340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13340 in the RIR database for the space. |
| Route object: RIR | 208.65.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 208.65.78.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 74.82.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 67.223.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13340 whose prefix no peer sees AS13340 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.109.81.0/24 | RADB | No ROA |
| 208.93.76.0/24 | ARIN, RADB | Valid |
| 208.93.77.0/24 | ARIN, RADB | Valid |
| 208.93.78.0/23 | ARIN | Valid |
| 2607:ffc0:1000::/36 | 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.