bgpreport

Network · data from 2026-11-12

AS18705 BlackBerry

Registry name: RIMBLACKBERRY - BlackBerry Limited, CA · PeeringDB

7IPv4 routes 85.7% RPKI valid · 28.6% with a route object
4IPv6 routes 0.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 6 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS18705, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18705, 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.

2607:ffc0:c::/48 No ROA Nonecovered by 2607:ffc0::/32 1 0%low visibility 1
193.109.81.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
2401:d100::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1
2607:ffc0::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1
2a03:1b80::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1
68.171.224.0/20 Valid Nonecovered by 68.171.224.0/19 2 0%low visibility 3
74.82.69.0/24 Valid Nonecovered by 74.82.64.0/19 2 0%low visibility 2
208.65.72.0/22 Valid Nonecovered by 208.65.72.0/21 2 0%low visibility 2
208.65.73.0/24 Valid Nonecovered by 208.65.72.0/21 2 0%low visibility 2
208.65.76.0/22 Valid Nonecovered by 208.65.72.0/21 2 0%low visibility 2
68.171.224.0/19 Valid RIR databaseARIN, RADB 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS18705: RADB::AS-BLACKBERRY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS18705 isn't in the set, or no route object for AS18705 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS18705 in itNot covered
RADB::AS-BLACKBERRY RADB 161081 Yes 0

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 42 are in fix.csv.

  • ROA: none5
  • Route object: none6
  • Route object: RIR4
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: none2607:ffc0:c::/48No ROA covers it. Add a ROA for AS18705, maxLength 48.1 of 636
Route object: none2607:ffc0:c::/48No route object for it. A route object for 2607:ffc0::/32 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.1 of 636
ROA: none193.109.81.0/24No ROA covers it. Add a ROA for AS18705, maxLength 24.2 of 673
Route object: RIR193.109.81.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none2401:d100::/32No ROA covers it. Add a ROA for AS18705, maxLength 32.1 of 636
Route object: RIR2401:d100::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636
ROA: none2607:ffc0::/32No ROA covers it. Add a ROA for AS18705, maxLength 32.1 of 636
Route object: RIR2607:ffc0::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636
ROA: none2a03:1b80::/32No ROA covers it. Add a ROA for AS18705, maxLength 32.1 of 636
Route object: RIR2a03:1b80::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: none68.171.224.0/20No route object for it. A route object for 68.171.224.0/19 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.2 of 673
Route object: none74.82.69.0/24No route object for it. A route object for 74.82.64.0/19 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.2 of 673
Route object: none208.65.72.0/22No route object for it. A route object for 208.65.72.0/21 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.2 of 673
Route object: none208.65.73.0/24No route object for it. A route object for 208.65.72.0/21 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.2 of 673
Route object: none208.65.76.0/22No route object for it. A route object for 208.65.72.0/21 with origin AS18705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18705 in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS18705 whose prefix no peer sees AS18705 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.100.168.0/21RADBNo ROA
12.175.140.0/24RADBNo ROA
64.75.31.0/24RADBNo ROA
67.223.64.0/19ARIN, RADBValid
72.5.214.0/24RADBNo ROA
74.82.64.0/19ARIN, RADBValid
93.186.16.0/20RADBNo ROA
103.246.201.0/24RADBNo ROA
103.246.202.0/23RADBNo ROA
131.117.168.0/21RADBNo ROA
173.247.32.0/19RADBValid
173.247.56.0/24RADBValid
173.247.57.0/24RADBValid
173.247.58.0/24RADBValid
178.239.80.0/20RADBNo ROA
195.3.172.0/22BELLNo ROA
206.51.26.0/24RADBNo ROA
206.53.144.0/20ARIN, RADBValid
206.53.152.0/24RADBValid
206.124.112.0/20ARIN, RADBValid
206.124.127.0/24RADBValid
208.65.72.0/21ARIN, RADBValid
208.93.72.0/21RADBValid
208.93.73.0/24RADBValid
216.9.240.0/20ARIN, RADBValid
216.104.235.0/24RADBNo ROA
216.136.156.0/24RADBNo 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.