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

Swatting

Swatting calls over time: volume, outcomes, and response speed

Swatting: 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 (7% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
010202020: 3 swatting calls logged in CAD2021: 13 swatting calls logged in CAD2022: 13 swatting calls logged in CAD2023: 7 swatting calls logged in CAD2024: 6 swatting calls logged in CAD2025: 8 swatting calls logged in CAD2026: 18 swatting calls logged in CAD2020n=32022n=132024n=62026n=18
swatting calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodSwatting calls logged in CAD
20203
202113
202213
20237
20246
20258
202618
Swatting Calls Are Rare: Only 68 on RecordSeattle Police logged 68 swatting calls between 2020 and 2026, with a high of 18 in 2026. Counts this small are too thin to read as a trend.

Swatting: 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%2020 · Report taken, no arrest: 33.3%2020 · Resolved on scene: 33.3%2020 · Unable to locate: 33.3%2021 · Report taken, no arrest: 69.2%2021 · Resolved on scene: 15.4%2021 · Unable to locate: 15.4%2022 · Report taken, no arrest: 53.8%2022 · Resolved on scene: 23.1%2022 · Unable to locate: 15.4%2022 · Other (unfounded / cancelled): 7.7%2023 · Report taken, no arrest: 85.7%2023 · Unable to locate: 14.3%2024 · Report taken, no arrest: 100.0%2025 · Report taken, no arrest: 50.0%2025 · Resolved on scene: 12.5%2025 · Unable to locate: 37.5%2026 · Report taken, no arrest: 38.9%2026 · Resolved on scene: 27.8%2026 · Unable to locate: 16.7%2026 · Other (unfounded / cancelled): 16.7%2020n=32022n=132024n=62026n=18
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
PeriodEventsReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
2020333.3%33.3%33.3%—
20211369.2%15.4%15.4%—
20221353.8%23.1%15.4%7.7%
2023785.7%—14.3%—
20246100.0%———
2025850.0%12.5%37.5%—
20261838.9%27.8%16.7%16.7%
18% of Swatting Calls End “Unable to Locate”Across 2020 to 2026, report-taken outcomes were 59% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Swatting: 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 7% of swatting events, 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 min60 min120 min2020: 0.8 min2021: 48.1 min2022: 9.1 min2023: 3.7 min2024: 8.7 min2025: 1.4 min2026: 79.0 min2020: 4.8 min2021: 52.8 min2022: 13.1 min2023: 18.2 min2024: 103.7 min2025: 9.0 min2026: 65.1 min2020n=22022n=102024n=62026n=18
Average response timeAverage dispatch delay
Small sample: Only a small share of swatting events are called in. The year with the fewest had only 2, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
202020.8 min4.8 min
20211348.1 min52.8 min
2022109.1 min13.1 min
202363.7 min18.2 min
202468.7 min103.7 min
202581.4 min9.0 min
20261879.0 min65.1 min
78% of Called-In Swatting Calls Get a Response Within 30 Minutes32% were answered in under 5 minutes, across all years on record.
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.

Swatting: 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 7% of swatting events, 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%2020 · 0–5 min: 50.0%2020 · 5–30 min: 50.0%2021 · No recorded response: 7.7%2021 · 0–5 min: 53.9%2021 · 5–30 min: 15.4%2021 · 1–4 hr: 23.1%2022 · 0–5 min: 70.0%2022 · 5–30 min: 10.0%2022 · 30–60 min: 10.0%2022 · 1–4 hr: 10.0%2023 · 5–30 min: 83.3%2023 · 30–60 min: 16.7%2024 · 0–5 min: 16.7%2024 · 5–30 min: 66.7%2024 · Over 8 hr: 16.7%2025 · 0–5 min: 12.5%2025 · 5–30 min: 87.5%2026 · No recorded response: 5.6%2026 · 0–5 min: 16.7%2026 · 5–30 min: 50.0%2026 · 30–60 min: 16.7%2026 · 4–8 hr: 11.1%2020n=22022n=102024n=62026n=18
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of swatting events are called in. The year with the fewest had only 2, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in events0–5 min5–30 minNo recorded response1–4 hr30–60 minOver 8 hr4–8 hr
2020250.0%50.0%—————
20211353.9%15.4%7.7%23.1%———
20221070.0%10.0%—10.0%10.0%——
20236—83.3%——16.7%——
2024616.7%66.7%———16.7%—
2025812.5%87.5%—————
20261816.7%50.0%5.6%—16.7%—11.1%
11% of Called-In Swatting Calls Wait Over an Hour for a ResponseAcross 2020 to 2026, 11% of called-in events took more than an hour to get a response.
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. 2020 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.