Campus Alert Archive
UO

Phoned shooting threat clears the recreation center; assessed as a swatting hoax

AI-generated · every claim is source-linked
ORswattingemergency notificationhigh confidence
Compare →
Confirmed HoaxDetermined to be a hoax. The institutional response is documented because it reveals how the alert system performed under a perceived real threat.

At approximately 11:10 AM PDT on May 6, 2026, a staff member at the University of Oregon's Student Recreation Center received a call from a blocked, unlisted number from a person who threatened to carry out a shooting and immediately hung up. UO Police Department officers cleared the building, interviewed the staffer, and conducted interior and exterior sweeps. UO issued a campus-wide alert just after 1 PM, followed by an all-clear at 1:54 PM PDT. Officials determined the call's lack of specificity was consistent with the Purgatory-linked swatting wave that had targeted dozens of US universities during the prior nine months.

Alerts
3
Response
—
Killed
—
Injured
—
Institution
University of Oregon
Public R1 · OR
All UO cases →
~23,000 studentsUO Alerts
Official alert policy
Read when and how UO says it will use UO Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

3 messages in sequence · 2 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

Some messages in this sequence are documented (their existence, timing, and channel are sourced) but their exact wording is not preserved in the public record. Those entries appear as placeholders; only confirmed text is displayed.

INITIAL ALERTMulti-channel
Verified verbatim64 chars
UO Alert Eugene BE AWARE: Student Rec Center. Swatting Incident.
Verify this quote
UO Division of Safety and Risk Services official alert archive (BE AWARE Student Rec Center)safety.uoregon.edufind archived copies
Run-hide-fight language has become the [default UO Alert framing](https://safety.uoregon.edu/alerts) for any reported armed-threat incident, regardless of swatting suspicion, the alert is written for the worst case
UO's spring-term timing put the May 6 incident squarely in the [final-exams approach window](https://registrar.uoregon.edu/calendars/academic), a period when rec-center traffic is typically elevated and when alert audiences are at maximum vigilance
ALL CLEARMulti-channel+54 min
Verified verbatim223 chars
Swatting is a criminal hoax where a caller falsely reports an emergency to law enforcement. UOPD has assessed the situation at the Student Recreation Center and the threat was unfounded. The SRC continues normal operations.
Verify this quote
University of Oregon Division of Safety and Risk Services official alert archive, 'UO Alert Eugene ALL CLEAR: Student Rec Center Swatting Incident' page, published 1:54 p.m. PDT May 6, 2026safety.uoregon.edufind archived copies
Verbatim body text of the UO official archive page for the ALL CLEAR notification, published at 1:54 p.m. PDT on May 6, 2026 (page title: 'UO Alert Eugene ALL CLEAR: Student Rec Center Swatting Incident')
The body text defines swatting, confirms UOPD's assessment, and restores operations, UO's standard post-swatting all-clear template by mid-2026
The 44-minute envelope from initial BE AWARE alert (just after 1 p.m.) to all-clear (1:54 p.m. PDT) is consistent with the rapid clearing described by KVAL and NBC16
Message elements

How the first alert is built

To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

UO Alert Eugene BE AWARE: Student Rec Center. Swatting Incident.

  • Sourcepresent25/25

    Final assessment

    Unanimous: signed 'UO Alert Eugene', the University of Oregon's branded alert system.

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads
    1. present: Signed 'UO Alert Eugene'.
    2. present: Branded "UO Alert Eugene".
    3. present: Signed 'UO Alert Eugene'.
    4. present: Branded 'UO Alert Eugene' (University of Oregon).
    5. present: Branded 'UO Alert Eugene' signature.
    6. present: UO Alert Eugene branded signature.
    7. present: Branded 'UO Alert' signature.
    8. present: Labeled 'UO Alert Eugene'.
    9. present: "UO Alert Eugene" branded signature.
    10. present: Branded 'UO Alert Eugene' signature identifies the sender.
    11. present: Signed "UO Alert Eugene".
    12. present: UO Alert Eugene is the branded alert signature.
    13. present: Branded UO Alert Eugene signature.
    14. present: "UO Alert Eugene" branded signature.
    15. present: Signed 'UO Alert Eugene'.
    16. present: 'UO Alert Eugene' branded signature
    17. present: Branded 'UO Alert Eugene'.
    18. present: Signed 'UO Alert Eugene'.
    19. present: Signed 'UO Alert Eugene'.
    20. present: Branded 'UO Alert Eugene' signature.
    21. present: Signed 'UO Alert Eugene'.
    22. present: 'UO Alert Eugene' branded signature.
    23. present: Signed 'UO Alert Eugene'.
    24. present: UO Alert Eugene signature.
    25. present: Signed "UO Alert Eugene".
  • Hazardpresent25/25

    Final assessment

    Unanimous: names a 'Swatting Incident' as the hazard.

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads
    1. present: Names 'Swatting Incident'.
    2. present: Names the hazard as a "Swatting Incident".
    3. present: Names 'Swatting Incident' specifically.
    4. present: Names 'Swatting Incident'.
    5. present: States 'Swatting Incident'.
    6. present: Swatting Incident named.
    7. present: Names a 'Swatting Incident'.
    8. present: States 'Swatting Incident'.
    9. present: "Swatting Incident" named.
    10. present: States 'Swatting Incident'.
    11. present: States "Swatting Incident".
    12. present: Swatting Incident named.
    13. present: States Swatting Incident.
    14. present: "Swatting Incident" named.
    15. present: 'Swatting Incident'.
    16. present: 'Swatting Incident'
    17. present: Names 'Swatting Incident'.
    18. present: States 'Swatting Incident'.
    19. present: States 'Swatting Incident'.
    20. present: Names 'Swatting Incident'.
    21. present: Names 'Swatting Incident'.
    22. present: 'Swatting Incident'.
    23. present: States 'Swatting Incident'.
    24. present: Swatting Incident.
    25. present: States "Swatting Incident".
  • Locationpresent25/25

    Final assessment

    Unanimous: names the 'Student Rec Center' as the site.

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads
    1. present: States 'Student Rec Center'.
    2. present: Gives "Student Rec Center".
    3. present: Gives 'Student Rec Center'.
    4. present: Student Rec Center.
    5. present: Names 'Student Rec Center'.
    6. present: Student Rec Center.
    7. present: Names 'Student Rec Center'.
    8. present: Names 'Student Rec Center'.
    9. present: "Student Rec Center".
    10. present: Names 'Student Rec Center'.
    11. present: Names "Student Rec Center".
    12. present: Student Rec Center.
    13. present: Names Student Rec Center.
    14. present: "Student Rec Center".
    15. present: 'Student Rec Center'.
    16. present: 'Student Rec Center'
    17. present: Names 'Student Rec Center'.
    18. present: Names 'Student Rec Center'.
    19. present: Names 'Student Rec Center'.
    20. present: Student Rec Center given.
    21. present: Gives 'Student Rec Center'.
    22. present: 'Student Rec Center'.
    23. present: Names 'Student Rec Center'.
    24. present: Student Rec Center.
    25. present: Names "Student Rec Center".
  • Guidanceabsent7/25

    Final assessment

    Majority found 'BE AWARE' too vague to count as a specific protective action; a sizable minority credited it as a caution-level instruction, but most read it as generic.

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads
    1. absent: Only says 'BE AWARE', no specific protective action instructed.
    2. absent: Only says "BE AWARE", which is not a specific protective action.
    3. present: Instructs 'BE AWARE', a caution-level protective directive.
    4. absent: 'BE AWARE' is not a specific protective action instruction.
    5. present: Instructs 'BE AWARE'.
    6. absent: "BE AWARE" is not a specific protective action instruction.
    7. absent: Says 'BE AWARE' but gives no specific protective action.
    8. absent: 'BE AWARE' is vague and does not instruct a specific protective action.
    9. absent: "BE AWARE" gives no specific protective action.
    10. absent: 'BE AWARE' is a vague advisory, not a specific protective action.
    11. absent: Only says "BE AWARE", not a specific protective action.
    12. absent: Only says BE AWARE, no specific protective action instructed.
    13. present: Instructs BE AWARE, an alertness instruction.
    14. absent: Only "BE AWARE" is generic, no specific protective action instructed.
    15. absent: 'BE AWARE' is not an instructed protective action.
    16. present: 'BE AWARE' as caution instruction
    17. present: Instructs 'BE AWARE', an advisory-level instruction.
    18. absent: Only says 'BE AWARE', no specific protective instruction.
    19. absent: 'BE AWARE' is not a specific protective action.
    20. absent: Only 'BE AWARE', not a specific protective action instruction.
    21. present: Instructs 'BE AWARE'.
    22. present: 'BE AWARE' functions as a caution instruction.
    23. absent: No specific protective action instructed, only 'BE AWARE'.
    24. absent: 'BE AWARE' is not a specific protective action.
    25. absent: Only says "BE AWARE", no specific protective action instructed.
  • Timeabsent0/25

    Final assessment

    Unanimous: no clock time, date, or recency marker is given.

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads
    1. absent: No clock time or date given.
    2. absent: No clock time, date, or recency marker is given.
    3. absent: No time or date reference given.
    4. absent: No time or date given.
    5. absent: No clock time or recency marker given.
    6. absent: No time given.
    7. absent: No clock time or date given.
    8. absent: No time or recency indicator given.
    9. absent: No time or date given.
    10. absent: No clock time, date, or recency word given.
    11. absent: No clock time or recency marker given.
    12. absent: No time reference given.
    13. absent: No clock time or date given.
    14. absent: No time reference given.
    15. absent: No time given.
    16. absent: No time given
    17. absent: No clock time or recency word given.
    18. absent: No time or date given.
    19. absent: No clock time or date given.
    20. absent: No time or recency marker given.
    21. absent: No clock time or date given.
    22. absent: No time/date given.
    23. absent: No clock time or date given.
    24. absent: No time or date given.
    25. absent: No clock time or recency marker given.
  • Impactabsent0/25

    Final assessment

    Unanimous: no stated consequence or severity is conveyed.

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads
    1. absent: No stated consequence conveyed.
    2. absent: No statement of potential harm or severity is included.
    3. absent: No stated consequence given.
    4. absent: No stated consequence or severity.
    5. absent: No stated consequence conveyed.
    6. absent: No stated consequence conveyed.
    7. absent: No statement of potential harm or severity.
    8. absent: No stated consequence given.
    9. absent: No stated consequence conveyed.
    10. absent: No stated consequence or severity.
    11. absent: No stated consequence given.
    12. absent: No stated consequence or severity.
    13. absent: No stated consequence given.
    14. absent: No stated consequence or severity.
    15. absent: No stated consequence.
    16. absent: No stated consequence
    17. absent: No stated consequence or severity.
    18. absent: No stated consequence.
    19. absent: No stated consequence or severity.
    20. absent: No stated consequence.
    21. absent: No stated consequence.
    22. absent: No stated consequence.
    23. absent: No stated consequence described.
    24. absent: No stated consequence given.
    25. absent: No stated consequence or severity conveyed.

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

By May 2026, the Purgatory-linked swatting wave (chronicled by The Trace, CNN, and ABC News as a coordinated cybercriminal operation targeting US universities since August 2025) had hit more than thirty campuses. The University of Oregon's Student Recreation Center became the May 6, 2026 target. According to UOPD's account quoted by the Daily Emerald and Lookout Eugene-Springfield, a staff member at the Rec Center received a call at approximately 11:10 AM PDT from a blocked, unlisted number. The caller threatened to carry out a shooting and immediately hung up. UOPD officers interviewed the staffer, swept the building's interior and exterior, and determined the threat lacked specificity. UO sent a campus-wide alert shortly after 1 PM, followed by an all-clear at 1:54 PM PDT that explicitly named the incident as a swatting hoax. The case is notable on several dimensions: first, the target was an athletic-recreation venue rather than the classroom-bomb-threat archetype that dominated earlier swatting waves; second, the 44-minute alert envelope (initial to all-clear) was at the fast end of the 2025-2026 response cycle; third, UO explicitly characterized the call as a swatting hoax in its public messaging, reflecting institutional confidence built up over the prior nine months as federal investigators identified the Purgatory group. The Daily Emerald's coverage placed the incident in continuity with the prior June 2024 UO Rec Center robbery, a different (real) crime, same building, to underline that the Rec Center had become a focus of both real and hoaxed threats.
Analysis

Key Findings

By May 2026, the Purgatory-linked swatting wave had progressed from hesitant institutional language ('reported threat') to explicit naming ('swatting hoax') in all-clear messaging, a maturation of campus-response vocabulary
The 44-minute initial-to-all-clear envelope was at the fast end of the 2025-2026 swatting-response cycle, reflecting institutional learning across the wave
Athletic-recreation facilities (Rec Center, gym, pool) joined classrooms and libraries as primary swatting targets, broadening the campus communication burden across non-academic settings
UOPD's stated rationale ('lack of specificity') has become the de facto field test for distinguishing swatting from credible threats during initial assessment
Outcome
No threat found. Building cleared and reopened the same afternoon. UOPD characterized the incident as a swatting hoax consistent with the 'Purgatory'-style threat pattern targeting US campuses since August 2025.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

  1. News
    Shooting threat at UO rec center deemed false after police clear building (Lookout Eugene-Springfield)
    lookouteugene-springfield.com
    archived copy
  2. Student Paper
    UOPD identifies no threat at Student Rec Center after reported swatting call (Daily Emerald)
    dailyemerald.com
    archived copy
  3. News
    Student Recreation Center returns to normal operations after brief lockdown; 'All Clear' (KVAL)
    kval.com
    archived copy
  4. News
    University of Oregon issues Alert after reported swatting incident at Student Rec Center (NBC16)
    nbc16.com
    archived copy
  5. Official
    Latest Alerts | Division of Safety and Risk Services (University of Oregon)
    safety.uoregon.edu
    archived copy
  6. News
    School Shooting 'Swatting' Calls Are Traumatizing Young People (The Trace)
    thetrace.org
    archived copy
  7. Official
    UO Division of Safety and Risk Services official alert archive (BE AWARE Student Rec Center)
    safety.uoregon.edu
    archived copy
  8. Student Paper
    University of Oregon Division of Safety and Risk Services official alert archive, 'UO Alert Eugene ALL CLEAR: Student Rec Center Swatting Incident' page, published 1:54 p.m. PDT May 6, 2026
    safety.uoregon.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Oregon: Phoned shooting threat clears the recreation center; assessed as a swatting hoax." Incident of May 6, 2026. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/university-of-oregon-rec-center-swatting-2026-05-06/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
swattingrec-centerathletic-venuepurgatoryconfirmed-hoaxphone-threatblocked-numberlack-of-specificityoregonpublic-r1spring-termemergency-notificationHoax
Added May 2026Updated July 2026Via ingestion