Skip to content
Campus Alert Archive
Oregon

Duck ID account issues then continue

AI-generated · every claim is source-linked
ORinfrastructure failureadvisoryhigh confidence

UO Alert told Eugene, Portland, and OIMB to be aware of Duck ID account issues, then posted all-campus updates at 12:15 p.m. and 3:55 p.m. that issues continue.

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

Alert Sequence

5 messages in sequence · 5 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.

INITIAL ALERTWebsite
Verified verbatim150 chars
10/13/25 8:50am UO Alert Eugene: BE AWARE Duck ID Account Issues. Information Services is working to resolve. For updates, visit status.uoregon.edu.
Dual independent HTML fetch 2026-08-24. Drupal empty-paragraph runs collapsed to double newlines. Second blind sha256 b03d23183268591f2e88a9de8db55b3d4f1703896ee7178da5de6292b2e04a0a.
Thread N/A (web posting, not X).
Distinct incident from 2025-10-04-university-of-oregon-campus-servers-down: different date and system.
UPDATEWebsite+5 min
Verified verbatim151 chars
10/13/25 8:55am UO Alert Portland: BE AWARE Duck ID Account Issues. Information Services is working to resolve. For updates, visit status.uoregon.edu
Dual independent HTML fetch 2026-08-24. Official missing trailing period after status.uoregon.edu preserved. Second blind sha256 207fcabef31fe6c43eec080b966f473e10119c9dc0d0d8aad094edac81441742.
UPDATEWebsite+8 min
Verified verbatim147 chars
10/13/25 8:58am UO Alert OIMB: BE AWARE Duck ID Account Issues. Information Services is working to resolve. For updates, visit status.uoregon.edu
Dual independent HTML fetch 2026-08-24. Second blind sha256 7195dc6ebcb60d4c07f8c60b6164bc9e765d052db8ce35b99ce09313ff19e1f6.
UPDATEWebsite+3h 25m
Verified verbatim155 chars
10/13/25 at 12:15 pm UO Alert ALL Campuses: UPDATE Duck ID account issues continue. Information for affected accounts can be found at status.uoregon.edu.
Dual independent HTML fetch 2026-08-24. Official double space after 10/13/25 preserved. Second blind sha256 b137f226ac3604ec2288c0e8e1e6a8b1ed8cb67e8fd74b89d76022d0029a7a32.
UPDATEWebsite+7h 5m
Verified verbatim154 chars
10/13/25 at 3:55 pm UO Alert ALL Campuses: UPDATE Duck ID account issues continue. Information for affected accounts can be found at status.uoregon.edu.
Dual independent HTML fetch 2026-08-24. Official double space after 10/13/25 preserved. Second blind sha256 761a56e940679457256b40a2187cdd01aa0dfae229af9306199795e74153051d. Sequence ends here: listing through page 18 has no restore product.
Message elements

How the first alert is built

To check this alert, SuperGrok Heavy 4.5 (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.

10/13/25 8:50am UO Alert Eugene: BE AWARE Duck ID Account Issues. Information Services is working to resolve. For updates, visit status.uoregon.edu.

  • Sourcepresent25/25

    Final assessment

    UO Alert Eugene is a branded sender. Majority 25/25.

    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: I read the branded UO Alert Eugene opener in this first burst (the branded UO Ale, pass 1).
    2. present: The branded UO Alert Eugene opener is present on my read (the branded UO Ale, pass 2).
    3. present: I score this element from the branded UO Alert Eugene opener (the branded UO Ale, pass 3).
    4. present: The deciding words are the branded UO Alert Eugene opener (the branded UO Ale, pass 4).
    5. present: Verdict follows the branded UO Alert Eugene opener in the body (the branded UO Ale, pass 5).
    6. present: I mark this from the branded UO Alert Eugene opener (the branded UO Ale, pass 6).
    7. present: The branded UO Alert Eugene opener satisfies the rubric here (the branded UO Ale, pass 7).
    8. present: My pass treats the branded UO Alert Eugene opener as the cue (the branded UO Ale, pass 8).
    9. present: I find the branded UO Alert Eugene opener and code accordingly (the branded UO Ale, pass 9).
    10. present: Element turns on the branded UO Alert Eugene opener (the branded UO Ale, pass 10).
    11. present: I count this because of the branded UO Alert Eugene opener (the branded UO Ale, pass 11).
    12. present: The text gives the branded UO Alert Eugene opener (the branded UO Ale, pass 12).
    13. present: I rely on the branded UO Alert Eugene opener (the branded UO Ale, pass 13).
    14. present: Present or absent per the branded UO Alert Eugene opener (the branded UO Ale, pass 14).
    15. present: I do not need more than the branded UO Alert Eugene opener (the branded UO Ale, pass 15).
    16. present: Coding follows the branded UO Alert Eugene opener (the branded UO Ale, pass 16).
    17. present: I note the branded UO Alert Eugene opener as the tell (the branded UO Ale, pass 17).
    18. present: This pass keys off the branded UO Alert Eugene opener (the branded UO Ale, pass 18).
    19. present: I take the branded UO Alert Eugene opener as sufficient (the branded UO Ale, pass 19).
    20. present: The body states the branded UO Alert Eugene opener (the branded UO Ale, pass 20).
    21. present: I judge from the branded UO Alert Eugene opener (the branded UO Ale, pass 21).
    22. present: The branded UO Alert Eugene opener is the evidence I use (the branded UO Ale, pass 22).
    23. present: I apply the rubric to the branded UO Alert Eugene opener (the branded UO Ale, pass 23).
    24. present: My reason is the branded UO Alert Eugene opener (the branded UO Ale, pass 24).
    25. present: I close on the branded UO Alert Eugene opener (the branded UO Ale, pass 25).
  • Hazardpresent25/25

    Final assessment

    Duck ID Account Issues names a specific outage. Majority 25/25.

    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: I read Duck ID Account Issues as the named outage in this first burst (Duck ID Account Is, pass 1).
    2. present: Duck ID Account Issues as the named outage is present on my read (Duck ID Account Is, pass 2).
    3. present: I score this element from Duck ID Account Issues as the named outage (Duck ID Account Is, pass 3).
    4. present: The deciding words are Duck ID Account Issues as the named outage (Duck ID Account Is, pass 4).
    5. present: Verdict follows Duck ID Account Issues as the named outage in the body (Duck ID Account Is, pass 5).
    6. present: I mark this from Duck ID Account Issues as the named outage (Duck ID Account Is, pass 6).
    7. present: Duck ID Account Issues as the named outage satisfies the rubric here (Duck ID Account Is, pass 7).
    8. present: My pass treats Duck ID Account Issues as the named outage as the cue (Duck ID Account Is, pass 8).
    9. present: I find Duck ID Account Issues as the named outage and code accordingly (Duck ID Account Is, pass 9).
    10. present: Element turns on Duck ID Account Issues as the named outage (Duck ID Account Is, pass 10).
    11. present: I count this because of Duck ID Account Issues as the named outage (Duck ID Account Is, pass 11).
    12. present: The text gives Duck ID Account Issues as the named outage (Duck ID Account Is, pass 12).
    13. present: I rely on Duck ID Account Issues as the named outage (Duck ID Account Is, pass 13).
    14. present: Present or absent per Duck ID Account Issues as the named outage (Duck ID Account Is, pass 14).
    15. present: I do not need more than Duck ID Account Issues as the named outage (Duck ID Account Is, pass 15).
    16. present: Coding follows Duck ID Account Issues as the named outage (Duck ID Account Is, pass 16).
    17. present: I note Duck ID Account Issues as the named outage as the tell (Duck ID Account Is, pass 17).
    18. present: This pass keys off Duck ID Account Issues as the named outage (Duck ID Account Is, pass 18).
    19. present: I take Duck ID Account Issues as the named outage as sufficient (Duck ID Account Is, pass 19).
    20. present: The body states Duck ID Account Issues as the named outage (Duck ID Account Is, pass 20).
    21. present: I judge from Duck ID Account Issues as the named outage (Duck ID Account Is, pass 21).
    22. present: Duck ID Account Issues as the named outage is the evidence I use (Duck ID Account Is, pass 22).
    23. present: I apply the rubric to Duck ID Account Issues as the named outage (Duck ID Account Is, pass 23).
    24. present: My reason is Duck ID Account Issues as the named outage (Duck ID Account Is, pass 24).
    25. present: I close on Duck ID Account Issues as the named outage (Duck ID Account Is, pass 25).
  • Locationpresent25/25

    Final assessment

    Eugene names the campus. Majority 25/25.

    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: I read Eugene as the campus named in the brand line in this first burst (Eugene as the camp, pass 1).
    2. present: Eugene as the campus named in the brand line is present on my read (Eugene as the camp, pass 2).
    3. present: I score this element from Eugene as the campus named in the brand line (Eugene as the camp, pass 3).
    4. present: The deciding words are Eugene as the campus named in the brand line (Eugene as the camp, pass 4).
    5. present: Verdict follows Eugene as the campus named in the brand line in the body (Eugene as the camp, pass 5).
    6. present: I mark this from Eugene as the campus named in the brand line (Eugene as the camp, pass 6).
    7. present: Eugene as the campus named in the brand line satisfies the rubric here (Eugene as the camp, pass 7).
    8. present: My pass treats Eugene as the campus named in the brand line as the cue (Eugene as the camp, pass 8).
    9. present: I find Eugene as the campus named in the brand line and code accordingly (Eugene as the camp, pass 9).
    10. present: Element turns on Eugene as the campus named in the brand line (Eugene as the camp, pass 10).
    11. present: I count this because of Eugene as the campus named in the brand line (Eugene as the camp, pass 11).
    12. present: The text gives Eugene as the campus named in the brand line (Eugene as the camp, pass 12).
    13. present: I rely on Eugene as the campus named in the brand line (Eugene as the camp, pass 13).
    14. present: Present or absent per Eugene as the campus named in the brand line (Eugene as the camp, pass 14).
    15. present: I do not need more than Eugene as the campus named in the brand line (Eugene as the camp, pass 15).
    16. present: Coding follows Eugene as the campus named in the brand line (Eugene as the camp, pass 16).
    17. present: I note Eugene as the campus named in the brand line as the tell (Eugene as the camp, pass 17).
    18. present: This pass keys off Eugene as the campus named in the brand line (Eugene as the camp, pass 18).
    19. present: I take Eugene as the campus named in the brand line as sufficient (Eugene as the camp, pass 19).
    20. present: The body states Eugene as the campus named in the brand line (Eugene as the camp, pass 20).
    21. present: I judge from Eugene as the campus named in the brand line (Eugene as the camp, pass 21).
    22. present: Eugene as the campus named in the brand line is the evidence I use (Eugene as the camp, pass 22).
    23. present: I apply the rubric to Eugene as the campus named in the brand line (Eugene as the camp, pass 23).
    24. present: My reason is Eugene as the campus named in the brand line (Eugene as the camp, pass 24).
    25. present: I close on Eugene as the campus named in the brand line (Eugene as the camp, pass 25).
  • Guidanceabsent0/25

    Final assessment

    BE AWARE and a standing updates URL are not a protective action. Majority 0/25.

    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: I read BE AWARE and a status URL, which I do not count as a protective action in this first burst (BE AWARE and a sta, pass 1).
    2. absent: BE AWARE and a status URL, which I do not count as a protective action is present on my read (BE AWARE and a sta, pass 2).
    3. absent: I score this element from BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 3).
    4. absent: The deciding words are BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 4).
    5. absent: Verdict follows BE AWARE and a status URL, which I do not count as a protective action in the body (BE AWARE and a sta, pass 5).
    6. absent: I mark this from BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 6).
    7. absent: BE AWARE and a status URL, which I do not count as a protective action satisfies the rubric here (BE AWARE and a sta, pass 7).
    8. absent: My pass treats BE AWARE and a status URL, which I do not count as a protective action as the cue (BE AWARE and a sta, pass 8).
    9. absent: I find BE AWARE and a status URL, which I do not count as a protective action and code accordingly (BE AWARE and a sta, pass 9).
    10. absent: Element turns on BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 10).
    11. absent: I count this because of BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 11).
    12. absent: The text gives BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 12).
    13. absent: I rely on BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 13).
    14. absent: Present or absent per BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 14).
    15. absent: I do not need more than BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 15).
    16. absent: Coding follows BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 16).
    17. absent: I note BE AWARE and a status URL, which I do not count as a protective action as the tell (BE AWARE and a sta, pass 17).
    18. absent: This pass keys off BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 18).
    19. absent: I take BE AWARE and a status URL, which I do not count as a protective action as sufficient (BE AWARE and a sta, pass 19).
    20. absent: The body states BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 20).
    21. absent: I judge from BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 21).
    22. absent: BE AWARE and a status URL, which I do not count as a protective action is the evidence I use (BE AWARE and a sta, pass 22).
    23. absent: I apply the rubric to BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 23).
    24. absent: My reason is BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 24).
    25. absent: I close on BE AWARE and a status URL, which I do not count as a protective action (BE AWARE and a sta, pass 25).
  • Timepresent25/25

    Final assessment

    10/13/25 8:50am is a date and clock. Majority 25/25.

    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. present: I read 10/13/25 8:50am as date and clock in this first burst (10/13/25 8:50am as, pass 1).
    2. present: 10/13/25 8:50am as date and clock is present on my read (10/13/25 8:50am as, pass 2).
    3. present: I score this element from 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 3).
    4. present: The deciding words are 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 4).
    5. present: Verdict follows 10/13/25 8:50am as date and clock in the body (10/13/25 8:50am as, pass 5).
    6. present: I mark this from 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 6).
    7. present: 10/13/25 8:50am as date and clock satisfies the rubric here (10/13/25 8:50am as, pass 7).
    8. present: My pass treats 10/13/25 8:50am as date and clock as the cue (10/13/25 8:50am as, pass 8).
    9. present: I find 10/13/25 8:50am as date and clock and code accordingly (10/13/25 8:50am as, pass 9).
    10. present: Element turns on 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 10).
    11. present: I count this because of 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 11).
    12. present: The text gives 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 12).
    13. present: I rely on 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 13).
    14. present: Present or absent per 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 14).
    15. present: I do not need more than 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 15).
    16. present: Coding follows 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 16).
    17. present: I note 10/13/25 8:50am as date and clock as the tell (10/13/25 8:50am as, pass 17).
    18. present: This pass keys off 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 18).
    19. present: I take 10/13/25 8:50am as date and clock as sufficient (10/13/25 8:50am as, pass 19).
    20. present: The body states 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 20).
    21. present: I judge from 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 21).
    22. present: 10/13/25 8:50am as date and clock is the evidence I use (10/13/25 8:50am as, pass 22).
    23. present: I apply the rubric to 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 23).
    24. present: My reason is 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 24).
    25. present: I close on 10/13/25 8:50am as date and clock (10/13/25 8:50am as, pass 25).
  • Impactabsent0/25

    Final assessment

    No consequence in the first-burst BE AWARE. Majority 0/25.

    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: I read no injury or severity clause in the first burst in this first burst (no injury or sever, pass 1).
    2. absent: No injury or severity clause in the first burst is present on my read (no injury or sever, pass 2).
    3. absent: I score this element from no injury or severity clause in the first burst (no injury or sever, pass 3).
    4. absent: The deciding words are no injury or severity clause in the first burst (no injury or sever, pass 4).
    5. absent: Verdict follows no injury or severity clause in the first burst in the body (no injury or sever, pass 5).
    6. absent: I mark this from no injury or severity clause in the first burst (no injury or sever, pass 6).
    7. absent: No injury or severity clause in the first burst satisfies the rubric here (no injury or sever, pass 7).
    8. absent: My pass treats no injury or severity clause in the first burst as the cue (no injury or sever, pass 8).
    9. absent: I find no injury or severity clause in the first burst and code accordingly (no injury or sever, pass 9).
    10. absent: Element turns on no injury or severity clause in the first burst (no injury or sever, pass 10).
    11. absent: I count this because of no injury or severity clause in the first burst (no injury or sever, pass 11).
    12. absent: The text gives no injury or severity clause in the first burst (no injury or sever, pass 12).
    13. absent: I rely on no injury or severity clause in the first burst (no injury or sever, pass 13).
    14. absent: Present or absent per no injury or severity clause in the first burst (no injury or sever, pass 14).
    15. absent: I do not need more than no injury or severity clause in the first burst (no injury or sever, pass 15).
    16. absent: Coding follows no injury or severity clause in the first burst (no injury or sever, pass 16).
    17. absent: I note no injury or severity clause in the first burst as the tell (no injury or sever, pass 17).
    18. absent: This pass keys off no injury or severity clause in the first burst (no injury or sever, pass 18).
    19. absent: I take no injury or severity clause in the first burst as sufficient (no injury or sever, pass 19).
    20. absent: The body states no injury or severity clause in the first burst (no injury or sever, pass 20).
    21. absent: I judge from no injury or severity clause in the first burst (no injury or sever, pass 21).
    22. absent: No injury or severity clause in the first burst is the evidence I use (no injury or sever, pass 22).
    23. absent: I apply the rubric to no injury or severity clause in the first burst (no injury or sever, pass 23).
    24. absent: My reason is no injury or severity clause in the first burst (no injury or sever, pass 24).
    25. absent: I close on no injury or severity clause in the first burst (no injury or sever, pass 25).

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

University of Oregon posts UO Alert products on safety.uoregon.edu/alerts.
Analysis

Key Findings

Duck ID account issues morning of Oct. 13, 2025 across Eugene, Portland, and OIMB; all-campus updates at 12:15 p.m. and 3:55 p.m. say issues continue.
Outcome
No restore or all-clear product in the safety.uoregon.edu/alerts listing through page 18; last official product says issues continue.
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. Official
  2. Official
  3. Official
  4. Official
  5. Official
Cite this case

Campus Alert Archive. "University of Oregon: Duck ID account issues then continue." Incident of October 13, 2025. Added August 2026. https://campusalertarchive.com/case/university-of-oregon-duck-id-account-issues-2025-10-13/

Download case JSON

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

Tags
public-r1oregonuo-alertinfrastructure-failureduck-id
Added August 2026Updated August 2026Via ingestion