Disclaimer: This site uses publicly accessible data from the City of Seattle. We use artificial intelligence to interpret and visualize the data. We present the data as is. Any further analysis or interpretation of the data is strictly the responsibility of the end user.
Cookies: This site uses cookies and similar browser storage, including Google Analytics, to measure traffic and to remember your choice. You must accept cookies to view this site. See our Privacy Policy.
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 →
Swipe sideways to see the full chart →
swatting calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Swatting calls logged in CAD
2020
3
2021
13
2022
13
2023
7
2024
6
2025
8
2026
18
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 →
Swipe sideways to see the full chart →
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
Period
Events
Report taken, no arrest
Resolved on scene
Unable to locate
Other (unfounded / cancelled)
2020
3
33.3%
33.3%
33.3%
—
2021
13
69.2%
15.4%
15.4%
—
2022
13
53.8%
23.1%
15.4%
7.7%
2023
7
85.7%
—
14.3%
—
2024
6
100.0%
—
—
—
2025
8
50.0%
12.5%
37.5%
—
2026
18
38.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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
Average dispatch delay
Average response time
2020
2
0.8 min
4.8 min
2021
13
48.1 min
52.8 min
2022
10
9.1 min
13.1 min
2023
6
3.7 min
18.2 min
2024
6
8.7 min
103.7 min
2025
8
1.4 min
9.0 min
2026
18
79.0 min
65.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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
Average dispatch delay
Average response time
2020
1
0.8 min
2.6 min
2021
7
1.1 min
3.9 min
2022
6
2.5 min
4.6 min
2023
5
3.8 min
20.0 min
2024
5
1.8 min
8.6 min
2025
8
1.4 min
9.0 min
2026
8
1.6 min
8.8 min
Priority 1 Calls Waited 8.8 Minutes on Average in 2026That is the average across 8 called-in Priority 1 events in 2026. Counts this small can swing a lot from year to year.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
Average dispatch delay
Average response time
2020
1
0.8 min
6.9 min
2021
3
148.6 min
152.2 min
2022
1
1.3 min
2.1 min
2023
0
—
—
2024
0
—
—
2025
0
—
—
2026
5
100.1 min
31.7 min
Priority 2 Calls Waited 32 Minutes on Average in 2026That is the average across 5 called-in Priority 2 events in 2026. Counts this small can swing a lot from year to year.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
Average dispatch delay
Average response time
2020
0
—
—
2021
3
57.5 min
75.0 min
2022
3
25.1 min
33.6 min
2023
1
2.8 min
9.4 min
2024
1
42.8 min
579.2 min
2025
0
—
—
2026
4
227.3 min
227.3 min
Priority 3 Calls Waited 227 Minutes on Average in 2026That is the average across 4 called-in Priority 3 events in 2026. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
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
Period
Called-in events
0–5 min
5–30 min
No recorded response
1–4 hr
30–60 min
Over 8 hr
4–8 hr
2020
2
50.0%
50.0%
—
—
—
—
—
2021
13
53.9%
15.4%
7.7%
23.1%
—
—
—
2022
10
70.0%
10.0%
—
10.0%
10.0%
—
—
2023
6
—
83.3%
—
—
16.7%
—
—
2024
6
16.7%
66.7%
—
—
—
16.7%
—
2025
8
12.5%
87.5%
—
—
—
—
—
2026
18
16.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.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
0–5 min
5–30 min
30–60 min
2020
1
100.0%
—
—
2021
7
85.7%
14.3%
—
2022
6
83.3%
16.7%
—
2023
5
—
80.0%
20.0%
2024
5
20.0%
80.0%
—
2025
8
12.5%
87.5%
—
2026
8
25.0%
75.0%
—
0% of Priority 1 Calls Took Over an Hour in 2026That is 0% of 8 called-in Priority 1 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
5–30 min
1–4 hr
0–5 min
No recorded response
30–60 min
2020
1
100.0%
—
—
—
—
2021
3
33.3%
66.7%
—
—
—
2022
1
—
—
100.0%
—
—
2023
0
—
—
—
—
—
2024
0
—
—
—
—
—
2025
0
—
—
—
—
—
2026
5
40.0%
—
—
20.0%
40.0%
0% of Priority 2 Calls Took Over an Hour in 2026That is 0% of 5 called-in Priority 2 events. Counts this small can swing a lot from year to year.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of swatting calls. The year with the fewest had only 1, 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
Period
Called-in events
No recorded response
0–5 min
1–4 hr
30–60 min
5–30 min
Over 8 hr
4–8 hr
2020
0
—
—
—
—
—
—
—
2021
3
33.3%
33.3%
33.3%
—
—
—
—
2022
3
—
33.3%
33.3%
33.3%
—
—
—
2023
1
—
—
—
—
100.0%
—
—
2024
1
—
—
—
—
—
100.0%
—
2025
0
—
—
—
—
—
—
—
2026
4
—
—
—
25.0%
25.0%
—
50.0%
50% of Priority 3 Calls Took Over an Hour in 2026That is 50% of 4 called-in Priority 3 events. Counts this small can swing a lot from year to year.
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.
Showing the 12 full calendar months, Sep 2025 through Aug 2026, one bar per month. The current month is left out because it is incomplete.
Small sample: this category had 20 events in this period, with no dispatches in 5 of the 12 months. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each month shows its count.
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 →
Swipe sideways to see the full chart →
swatting calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Swatting calls logged in CAD
Sep 2025
—
Oct 2025
—
Nov 2025
—
Dec 2025
3
Jan 2026
—
Feb 2026
2
Mar 2026
6
Apr 2026
2
May 2026
1
Jun 2026
4
Jul 2026
—
Aug 2026
2
Swatting Calls Totaled 20 Over the Last 12 MonthsSeattle Police logged 6 swatting calls in the busiest month (Mar 2026); 5 of the 12 months had none. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
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
Period
Events
Report taken, no arrest
Resolved on scene
Unable to locate
Other (unfounded / cancelled)
Dec 2025
0
33.3%
33.3%
33.3%
—
Feb 2026
0
—
50.0%
—
50.0%
Mar 2026
0
33.3%
50.0%
—
16.7%
Apr 2026
0
100.0%
—
—
—
May 2026
0
100.0%
—
—
—
Jun 2026
0
—
25.0%
50.0%
25.0%
Aug 2026
0
50.0%
—
50.0%
—
“Unable to Locate” Ended 20% of Swatting Calls Over the Last 12 MonthsReport-taken outcomes were 35% of calls over the period.
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of swatting events are called in. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
3
0.7 min
6.3 min
Jan 2026
0
—
—
Feb 2026
2
1.0 min
8.5 min
Mar 2026
6
78.6 min
89.6 min
Apr 2026
2
1.8 min
33.2 min
May 2026
1
39.2 min
39.3 min
Jun 2026
4
224.9 min
145.0 min
Jul 2026
0
—
—
Aug 2026
2
3.0 min
5.3 min
Called-In Events Averaged 63 Minutes to Get an Officer Over the Last 12 MonthsBased on 20 called-in events with a recorded arrival. Counts this small can swing from one month to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of swatting calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
3
0.7 min
6.3 min
Jan 2026
0
—
—
Feb 2026
2
1.0 min
8.5 min
Mar 2026
2
1.5 min
13.1 min
Apr 2026
1
1.1 min
8.1 min
May 2026
0
—
—
Jun 2026
1
5.4 min
12.7 min
Jul 2026
0
—
—
Aug 2026
1
0.8 min
5.4 min
100% of Called-In Priority 1 Calls Got a Response Within 30 Minutes20% were answered in under 5 minutes over the last 12 months.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of swatting calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
2
10.4 min
31.7 min
Apr 2026
1
2.5 min
58.3 min
May 2026
0
—
—
Jun 2026
1
472.0 min
—
Jul 2026
0
—
—
Aug 2026
1
5.2 min
5.2 min
Priority 2 Calls Averaged 32 Minutes to Get an Officer Over the Last 12 MonthsBased on 4 called-in Priority 2 events with a recorded arrival. Counts this small can swing from one month to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 3 calls are a small share of swatting calls. The month with the fewest had only 1, so averages can swing widely; the n= under each month shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
0
—
—
Jan 2026
0
—
—
Feb 2026
0
—
—
Mar 2026
1
447.5 min
447.6 min
Apr 2026
0
—
—
May 2026
1
39.2 min
39.3 min
Jun 2026
2
211.2 min
211.2 min
Jul 2026
0
—
—
Aug 2026
0
—
—
Priority 3 Calls Averaged 227 Minutes to Get an Officer Over the Last 12 MonthsBased on 4 called-in Priority 3 events with a recorded arrival. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
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 month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
0–5 min
5–30 min
30–60 min
4–8 hr
No recorded response
Sep 2025
0
—
—
—
—
—
Oct 2025
0
—
—
—
—
—
Nov 2025
0
—
—
—
—
—
Dec 2025
3
33.3%
66.7%
—
—
—
Jan 2026
0
—
—
—
—
—
Feb 2026
2
50.0%
50.0%
—
—
—
Mar 2026
6
16.7%
50.0%
16.7%
16.7%
—
Apr 2026
2
—
50.0%
50.0%
—
—
May 2026
1
—
—
100.0%
—
—
Jun 2026
4
—
50.0%
—
25.0%
25.0%
Jul 2026
0
—
—
—
—
—
Aug 2026
2
—
100.0%
—
—
—
10% of Called-In Events Took Over an Hour Over the Last 12 MonthsThat is 10% of 20 called-in events. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of swatting calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
0–5 min
5–30 min
Sep 2025
0
—
—
Oct 2025
0
—
—
Nov 2025
0
—
—
Dec 2025
3
33.3%
66.7%
Jan 2026
0
—
—
Feb 2026
2
50.0%
50.0%
Mar 2026
2
—
100.0%
Apr 2026
1
—
100.0%
May 2026
0
—
—
Jun 2026
1
—
100.0%
Jul 2026
0
—
—
Aug 2026
1
—
100.0%
No Called-In Priority 1 Calls Took Over an Hour to Get a ResponseNone of the 10 called-in events over the last 12 months took more than an hour.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of swatting calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
30–60 min
No recorded response
Sep 2025
0
—
—
—
Oct 2025
0
—
—
—
Nov 2025
0
—
—
—
Dec 2025
0
—
—
—
Jan 2026
0
—
—
—
Feb 2026
0
—
—
—
Mar 2026
2
50.0%
50.0%
—
Apr 2026
1
—
100.0%
—
May 2026
0
—
—
—
Jun 2026
1
—
—
100.0%
Jul 2026
0
—
—
—
Aug 2026
1
100.0%
—
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 MonthsThat is 0% of 5 called-in Priority 2 events. Counts this small can swing from one month to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 3 calls are a small share of swatting calls. The month with the fewest had only 1, so shares can swing widely; the n= under each month shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
4–8 hr
30–60 min
5–30 min
Sep 2025
0
—
—
—
Oct 2025
0
—
—
—
Nov 2025
0
—
—
—
Dec 2025
0
—
—
—
Jan 2026
0
—
—
—
Feb 2026
0
—
—
—
Mar 2026
1
100.0%
—
—
Apr 2026
0
—
—
—
May 2026
1
—
100.0%
—
Jun 2026
2
50.0%
—
50.0%
Jul 2026
0
—
—
—
Aug 2026
0
—
—
—
50% of Priority 3 Calls Took Over an Hour Over the Last 12 MonthsThat is 50% of 4 called-in Priority 3 events. Counts this small can swing from one month to the next.
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.
Showing the 12 most recent full weeks (Monday to Sunday): Jun 15 through Sep 6, 2026, one bar per week, labeled by its first day. The current week is left out because it is incomplete.
Small sample: this category had 3 events in this period, with no dispatches in 9 of the 12 weeks. Percentages and average times can swing widely when counts are this small, so read the trends with caution; the n= under each week shows its count.
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 →
Swipe sideways to see the full chart →
swatting calls logged in CAD
View as table
Call volume — same numbers as the chart above
Period
Swatting calls logged in CAD
Week of Jun 15
—
Week of Jun 22
—
Week of Jun 29
1
Week of Jul 6
—
Week of Jul 13
—
Week of Jul 20
—
Week of Jul 27
—
Week of Aug 3
—
Week of Aug 10
1
Week of Aug 17
—
Week of Aug 24
1
Week of Aug 31
—
Swatting Calls Totaled 3 Over the Last 12 WeeksSeattle Police logged 1 swatting calls in the busiest week (Week of Jun 29); 9 of the 12 weeks had none. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
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
Period
Events
Unable to locate
Report taken, no arrest
Week of Jun 29
0
100.0%
—
Week of Aug 10
0
—
100.0%
Week of Aug 24
0
100.0%
—
“Unable to Locate” Ended 67% of Swatting Calls Over the Last 12 WeeksReport-taken outcomes were 33% of calls over the period.
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Only a small share of swatting events are called in. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
1
5.4 min
12.7 min
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
5.2 min
5.2 min
Week of Aug 17
0
—
—
Week of Aug 24
1
0.8 min
5.4 min
Week of Aug 31
0
—
—
Called-In Events Averaged 7.8 Minutes to Get an Officer Over the Last 12 WeeksBased on 3 called-in events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 1 calls are a small share of swatting calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
1
5.4 min
12.7 min
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
0
—
—
Week of Aug 17
0
—
—
Week of Aug 24
1
0.8 min
5.4 min
Week of Aug 31
0
—
—
Priority 1 Calls Averaged 9.1 Minutes to Get an Officer Over the Last 12 WeeksBased on 2 called-in Priority 1 events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
Small sample: Priority 2 calls are a small share of swatting calls. The week with the fewest had only 1, so averages can swing widely; the n= under each week shows its count.
View as table
How long it took — same numbers as the chart above
Period
Called-in events
Average dispatch delay
Average response time
Week of Jun 15
0
—
—
Week of Jun 22
0
—
—
Week of Jun 29
0
—
—
Week of Jul 6
0
—
—
Week of Jul 13
0
—
—
Week of Jul 20
0
—
—
Week of Jul 27
0
—
—
Week of Aug 3
0
—
—
Week of Aug 10
1
5.2 min
5.2 min
Week of Aug 17
0
—
—
Week of Aug 24
0
—
—
Week of Aug 31
0
—
—
Priority 2 Calls Averaged 5.2 Minutes to Get an Officer Over the Last 12 WeeksBased on 1 called-in Priority 2 events with a recorded arrival. Counts this small can swing from one week to the next.
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
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 →
Swipe sideways to see the full chart →
Average response timeAverage dispatch delay
No Priority 3 Calls Over the Last 12 WeeksThere were no called-in Priority 3 events in the period.
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 →
Swipe sideways to see the full chart →
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 week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
1
100.0%
Week of Jul 6
0
—
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
0
—
Week of Aug 10
1
100.0%
Week of Aug 17
0
—
Week of Aug 24
1
100.0%
Week of Aug 31
0
—
0% of Called-In Events Took Over an Hour Over the Last 12 WeeksThat is 0% of 3 called-in events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 1 calls are a small share of swatting calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
1
100.0%
Week of Jul 6
0
—
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
0
—
Week of Aug 10
0
—
Week of Aug 17
0
—
Week of Aug 24
1
100.0%
Week of Aug 31
0
—
0% of Priority 1 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% of 2 called-in Priority 1 events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Priority 2 calls are a small share of swatting calls. The week with the fewest had only 1, so shares can swing widely; the n= under each week shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
Period
Called-in events
5–30 min
Week of Jun 15
0
—
Week of Jun 22
0
—
Week of Jun 29
0
—
Week of Jul 6
0
—
Week of Jul 13
0
—
Week of Jul 20
0
—
Week of Jul 27
0
—
Week of Aug 3
0
—
Week of Aug 10
1
100.0%
Week of Aug 17
0
—
Week of Aug 24
0
—
Week of Aug 31
0
—
0% of Priority 2 Calls Took Over an Hour Over the Last 12 WeeksThat is 0% of 1 called-in Priority 2 events. Counts this small can swing from one week to the next.
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 →
Swipe sideways to see the full chart →
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
No Priority 3 Calls Over the Last 12 WeeksThere were no called-in Priority 3 events in the period.
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.
“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 month is the number of events logged that month 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.
“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 week is the number of events logged that week 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.