Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Alarms, False

Alarms, False calls over time: volume, outcomes, and response speed

Alarms, False: Call Volume

Call volume is the number of events logged in the Seattle Police Department’s Computer-Aided Dispatch (CAD) system. It counts calls from the public (by 911, phone, text or alarm) as well as officer-initiated activity, once per event, grouped by the call type assigned when the call was dispatched, before any investigation. It is not the same as the number of crimes reported.

Included: Every event logged in CAD: calls from the public and events officers logged themselves (1% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
010,00020,0002009: 6,615 alarms, false calls logged in CAD2010: 10,787 alarms, false calls logged in CAD2011: 10,555 alarms, false calls logged in CAD2012: 10,832 alarms, false calls logged in CAD2013: 11,502 alarms, false calls logged in CAD2014: 12,234 alarms, false calls logged in CAD2015: 12,972 alarms, false calls logged in CAD2016: 13,514 alarms, false calls logged in CAD2017: 14,149 alarms, false calls logged in CAD2018: 13,914 alarms, false calls logged in CAD2019: 14,247 alarms, false calls logged in CAD2020: 10,647 alarms, false calls logged in CAD2021: 12,489 alarms, false calls logged in CAD2022: 15,273 alarms, false calls logged in CAD2023: 15,369 alarms, false calls logged in CAD2024: 11,566 alarms, false calls logged in CAD2025: 1,944 alarms, false calls logged in CAD2026: 1,306 alarms, false calls logged in CAD2009n=6,6152011n=10,5552013n=11,5022015n=12,9722017n=14,1492019n=14,2472021n=12,4892023n=15,3692025n=1,9442026n=1,306
alarms, false calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAlarms, false calls logged in CAD
20096,615
201010,787
201110,555
201210,832
201311,502
201412,234
201512,972
201613,514
201714,149
201813,914
201914,247
202010,647
202112,489
202215,273
202315,369
202411,566
20251,944
20261,306
Calls in This Category Are Down 87% From Their 2023 PeakSeattle Police logged 15,369 calls in this category in 2023 and 1,944 in 2025, the most recent full year.

Alarms, False: What Happened When Officers Responded

Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.

Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.

Swipe sideways to see the full chart →
100%50%0%2009 · Arrest / citation: 0.1%2009 · Report taken, no arrest: 1.2%2009 · Resolved on scene: 20.8%2009 · Unable to locate: 2.9%2009 · Other (unfounded / cancelled): 74.9%2010 · Arrest / citation: 0.1%2010 · Report taken, no arrest: 1.0%2010 · Resolved on scene: 21.1%2010 · Unable to locate: 2.7%2010 · Other (unfounded / cancelled): 75.0%2011 · Arrest / citation: 0.2%2011 · Report taken, no arrest: 0.8%2011 · Resolved on scene: 21.7%2011 · Unable to locate: 2.5%2011 · Other (unfounded / cancelled): 74.7%2012 · Arrest / citation: 0.2%2012 · Report taken, no arrest: 0.6%2012 · Resolved on scene: 22.5%2012 · Unable to locate: 2.6%2012 · Other (unfounded / cancelled): 73.9%2013 · Arrest / citation: 0.1%2013 · Report taken, no arrest: 0.7%2013 · Resolved on scene: 17.4%2013 · Unable to locate: 2.5%2013 · Other (unfounded / cancelled): 79.3%2014 · Report taken, no arrest: 0.6%2014 · Resolved on scene: 14.1%2014 · Unable to locate: 3.1%2014 · Other (unfounded / cancelled): 82.2%2015 · Arrest / citation: 0.1%2015 · Report taken, no arrest: 0.8%2015 · Resolved on scene: 15.5%2015 · Unable to locate: 3.2%2015 · Other (unfounded / cancelled): 80.3%2016 · Arrest / citation: 0.1%2016 · Report taken, no arrest: 0.5%2016 · Resolved on scene: 18.3%2016 · Unable to locate: 3.0%2016 · Other (unfounded / cancelled): 78.0%2017 · Arrest / citation: 0.1%2017 · Report taken, no arrest: 0.6%2017 · Resolved on scene: 20.3%2017 · Unable to locate: 3.1%2017 · Other (unfounded / cancelled): 75.9%2018 · Arrest / citation: 0.1%2018 · Report taken, no arrest: 0.5%2018 · Resolved on scene: 24.2%2018 · Unable to locate: 4.5%2018 · Other (unfounded / cancelled): 70.7%2019 · Arrest / citation: 0.1%2019 · Report taken, no arrest: 0.6%2019 · Resolved on scene: 22.5%2019 · Unable to locate: 5.2%2019 · Other (unfounded / cancelled): 71.6%2020 · Report taken, no arrest: 1.1%2020 · Resolved on scene: 26.8%2020 · Unable to locate: 5.3%2020 · Other (unfounded / cancelled): 66.8%2021 · Arrest / citation: 0.2%2021 · Report taken, no arrest: 1.1%2021 · Resolved on scene: 32.6%2021 · Unable to locate: 6.2%2021 · Other (unfounded / cancelled): 59.9%2022 · Arrest / citation: 0.1%2022 · Report taken, no arrest: 0.8%2022 · Resolved on scene: 34.5%2022 · Unable to locate: 8.1%2022 · Other (unfounded / cancelled): 56.6%2023 · Arrest / citation: 0.1%2023 · Report taken, no arrest: 0.6%2023 · Resolved on scene: 30.2%2023 · Unable to locate: 8.0%2023 · Other (unfounded / cancelled): 61.2%2024 · Arrest / citation: 0.1%2024 · Report taken, no arrest: 0.6%2024 · Resolved on scene: 31.3%2024 · Unable to locate: 9.7%2024 · Other (unfounded / cancelled): 58.4%2025 · Arrest / citation: 0.3%2025 · Report taken, no arrest: 1.0%2025 · Resolved on scene: 30.5%2025 · Unable to locate: 19.7%2025 · Other (unfounded / cancelled): 48.5%2026 · Arrest / citation: 0.2%2026 · Report taken, no arrest: 0.8%2026 · Resolved on scene: 35.4%2026 · Unable to locate: 22.3%2026 · Other (unfounded / cancelled): 41.4%2009n=6,6152011n=10,5552013n=11,5022015n=12,9722017n=14,1492019n=14,2472021n=12,4892023n=15,3692025n=1,9442026n=1,306
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
20096,6150.1%1.2%20.8%2.9%74.9%
201010,7870.1%1.0%21.1%2.7%75.0%
201110,5550.2%0.8%21.7%2.5%74.7%
201210,8320.2%0.6%22.5%2.6%73.9%
201311,5020.1%0.7%17.4%2.5%79.3%
201412,234—0.6%14.1%3.1%82.2%
201512,9720.1%0.8%15.5%3.2%80.3%
201613,5140.1%0.5%18.3%3.0%78.0%
201714,1490.1%0.6%20.3%3.1%75.9%
201813,9140.1%0.5%24.2%4.5%70.7%
201914,2470.1%0.6%22.5%5.2%71.6%
202010,647—1.1%26.8%5.3%66.8%
202112,4890.2%1.1%32.6%6.2%59.9%
202215,2730.1%0.8%34.5%8.1%56.6%
202315,3690.1%0.6%30.2%8.0%61.2%
202411,5660.1%0.6%31.3%9.7%58.4%
20251,9440.3%1.0%30.5%19.7%48.5%
20261,3060.2%0.8%35.4%22.3%41.4%
22% of Calls in This Category End “Unable to Locate,” Up From 3%Report-taken outcomes moved from 0% of calls in 2016 to 1% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Alarms, False: How Long It Took

Response time is how long it took, from the moment a called-in event was queued with dispatch, until the first officer arrived on scene. Dispatch delay is the first part of that wait: the time before an officer was assigned and sent. Both lines show the average, which a small number of very long waits pull up, so it runs higher than the typical (median) call.

Included: Only events called in by the public and dispatched to an officer. The averages use those with a recorded officer arrival. The n= under each bar is the number of called-in events. Excluded: Events officers logged themselves (on view), which are 1% of events in this category, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min100 min200 min2009: 30.6 min2010: 24.5 min2011: 22.6 min2012: 30.0 min2013: 32.7 min2014: 38.6 min2015: 54.6 min2016: 49.8 min2017: 52.9 min2018: 68.4 min2019: 62.8 min2020: 50.6 min2021: 69.8 min2022: 81.1 min2023: 116.0 min2024: 134.8 min2025: 56.3 min2026: 42.5 min2009: 38.4 min2010: 32.2 min2011: 30.6 min2012: 38.5 min2013: 41.1 min2014: 48.2 min2015: 65.3 min2016: 60.8 min2017: 63.9 min2018: 79.4 min2019: 75.1 min2020: 62.2 min2021: 81.3 min2022: 92.6 min2023: 128.8 min2024: 145.6 min2025: 70.9 min2026: 52.1 min2009n=6,4692011n=10,3012013n=11,3312015n=12,8052017n=13,9882019n=14,1112021n=12,3942023n=15,2602025n=1,9122026n=1,286
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20096,46930.6 min38.4 min
201010,56224.5 min32.2 min
201110,30122.6 min30.6 min
201210,59530.0 min38.5 min
201311,33132.7 min41.1 min
201412,06038.6 min48.2 min
201512,80554.6 min65.3 min
201613,38049.8 min60.8 min
201713,98852.9 min63.9 min
201813,78468.4 min79.4 min
201914,11162.8 min75.1 min
202010,53550.6 min62.2 min
202112,39469.8 min81.3 min
202215,18381.1 min92.6 min
202315,260116.0 min128.8 min
202411,489134.8 min145.6 min
20251,91256.3 min70.9 min
20261,28642.5 min52.1 min
The Average Call Gets an Officer in 52 MinutesAverage response time has decreased 14% in the past 10 years, from 61 minutes in 2016 to 52 in 2026.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Alarms, False: How Long It Took, in Full

The same response times, broken into bands so the slowest calls are visible. Each bar shows the share of called-in events by how long the first officer took to arrive after the event was queued, including the ones that took hours. “No recorded response” means no arrival was ever logged.

Included: Only events called in by the public and dispatched to an officer, including those with no recorded arrival (shown as “No recorded response”). Excluded: Events officers logged themselves (on view), which are 1% of events in this category, because they have no wait. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
100%50%0%2009 · No recorded response: 10.3%2009 · 0–5 min: 10.9%2009 · 5–30 min: 47.0%2009 · 30–60 min: 14.5%2009 · 1–4 hr: 16.2%2009 · 4–8 hr: 1.0%2009 · Over 8 hr: 0.1%2010 · No recorded response: 10.7%2010 · 0–5 min: 13.3%2010 · 5–30 min: 49.6%2010 · 30–60 min: 12.9%2010 · 1–4 hr: 12.8%2010 · 4–8 hr: 0.8%2010 · Over 8 hr: 0.0%2011 · No recorded response: 11.4%2011 · 0–5 min: 14.7%2011 · 5–30 min: 49.6%2011 · 30–60 min: 12.0%2011 · 1–4 hr: 11.6%2011 · 4–8 hr: 0.7%2011 · Over 8 hr: 0.0%2012 · No recorded response: 10.9%2012 · 0–5 min: 13.0%2012 · 5–30 min: 46.1%2012 · 30–60 min: 13.2%2012 · 1–4 hr: 15.3%2012 · 4–8 hr: 1.3%2012 · Over 8 hr: 0.1%2013 · No recorded response: 10.2%2013 · 0–5 min: 11.4%2013 · 5–30 min: 46.0%2013 · 30–60 min: 14.0%2013 · 1–4 hr: 16.8%2013 · 4–8 hr: 1.5%2013 · Over 8 hr: 0.1%2014 · No recorded response: 10.3%2014 · 0–5 min: 10.1%2014 · 5–30 min: 43.5%2014 · 30–60 min: 14.3%2014 · 1–4 hr: 19.2%2014 · 4–8 hr: 2.3%2014 · Over 8 hr: 0.2%2015 · No recorded response: 9.5%2015 · 0–5 min: 9.5%2015 · 5–30 min: 38.9%2015 · 30–60 min: 14.0%2015 · 1–4 hr: 22.6%2015 · 4–8 hr: 4.5%2015 · Over 8 hr: 1.0%2016 · No recorded response: 10.0%2016 · 0–5 min: 9.0%2016 · 5–30 min: 38.5%2016 · 30–60 min: 14.5%2016 · 1–4 hr: 23.6%2016 · 4–8 hr: 3.9%2016 · Over 8 hr: 0.4%2017 · No recorded response: 8.9%2017 · 0–5 min: 8.3%2017 · 5–30 min: 37.9%2017 · 30–60 min: 15.1%2017 · 1–4 hr: 25.3%2017 · 4–8 hr: 4.4%2017 · Over 8 hr: 0.3%2018 · No recorded response: 9.0%2018 · 0–5 min: 7.4%2018 · 5–30 min: 34.8%2018 · 30–60 min: 14.7%2018 · 1–4 hr: 26.6%2018 · 4–8 hr: 6.4%2018 · Over 8 hr: 1.1%2019 · No recorded response: 9.6%2019 · 0–5 min: 7.0%2019 · 5–30 min: 35.3%2019 · 30–60 min: 15.0%2019 · 1–4 hr: 26.8%2019 · 4–8 hr: 5.4%2019 · Over 8 hr: 0.9%2020 · No recorded response: 9.8%2020 · 0–5 min: 9.1%2020 · 5–30 min: 39.1%2020 · 30–60 min: 14.2%2020 · 1–4 hr: 23.2%2020 · 4–8 hr: 4.0%2020 · Over 8 hr: 0.6%2021 · No recorded response: 10.6%2021 · 0–5 min: 5.5%2021 · 5–30 min: 34.5%2021 · 30–60 min: 15.2%2021 · 1–4 hr: 27.1%2021 · 4–8 hr: 5.7%2021 · Over 8 hr: 1.5%2022 · No recorded response: 10.8%2022 · 0–5 min: 4.7%2022 · 5–30 min: 30.8%2022 · 30–60 min: 15.0%2022 · 1–4 hr: 29.9%2022 · 4–8 hr: 7.1%2022 · Over 8 hr: 1.7%2023 · No recorded response: 10.8%2023 · 0–5 min: 3.7%2023 · 5–30 min: 26.1%2023 · 30–60 min: 14.3%2023 · 1–4 hr: 30.5%2023 · 4–8 hr: 10.3%2023 · Over 8 hr: 4.3%2024 · No recorded response: 10.4%2024 · 0–5 min: 2.7%2024 · 5–30 min: 23.4%2024 · 30–60 min: 13.9%2024 · 1–4 hr: 32.9%2024 · 4–8 hr: 11.3%2024 · Over 8 hr: 5.4%2025 · No recorded response: 10.9%2025 · 0–5 min: 8.2%2025 · 5–30 min: 41.6%2025 · 30–60 min: 12.2%2025 · 1–4 hr: 20.2%2025 · 4–8 hr: 5.3%2025 · Over 8 hr: 1.6%2026 · No recorded response: 10.7%2026 · 0–5 min: 11.3%2026 · 5–30 min: 43.0%2026 · 30–60 min: 13.4%2026 · 1–4 hr: 17.9%2026 · 4–8 hr: 2.9%2026 · Over 8 hr: 0.8%2009n=6,4692011n=10,3012013n=11,3312015n=12,8052017n=13,9882019n=14,1112021n=12,3942023n=15,2602025n=1,9122026n=1,286
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
20096,46910.3%10.9%47.0%14.5%16.2%1.0%0.1%
201010,56210.7%13.3%49.6%12.9%12.8%0.8%0.0%
201110,30111.4%14.7%49.6%12.0%11.6%0.7%0.0%
201210,59510.9%13.0%46.1%13.2%15.3%1.3%0.1%
201311,33110.2%11.4%46.0%14.0%16.8%1.5%0.1%
201412,06010.3%10.1%43.5%14.3%19.2%2.3%0.2%
201512,8059.5%9.5%38.9%14.0%22.6%4.5%1.0%
201613,38010.0%9.0%38.5%14.5%23.6%3.9%0.4%
201713,9888.9%8.3%37.9%15.1%25.3%4.4%0.3%
201813,7849.0%7.4%34.8%14.7%26.6%6.4%1.1%
201914,1119.6%7.0%35.3%15.0%26.8%5.4%0.9%
202010,5359.8%9.1%39.1%14.2%23.2%4.0%0.6%
202112,39410.6%5.5%34.5%15.2%27.1%5.7%1.5%
202215,18310.8%4.7%30.8%15.0%29.9%7.1%1.7%
202315,26010.8%3.7%26.1%14.3%30.5%10.3%4.3%
202411,48910.4%2.7%23.4%13.9%32.9%11.3%5.4%
20251,91210.9%8.2%41.6%12.2%20.2%5.3%1.6%
20261,28610.7%11.3%43.0%13.4%17.9%2.9%0.8%
Fewer Calls Wait Over an Hour: 22%, Down From 28%22% of calls took more than an hour to get a response in 2026, compared with 28% in 2016.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2009 and 2026 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each year is the number of events logged that year in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.