Skip to content
Campus Alert Archive
UW

T-Mobile regional outage

AI-generated · every claim is source-linked
WAhazmatemergency notificationhigh confidence

University of Washington published an official alert update on or about 2022-06-09. Full text is preserved from the official archive.

Alerts
1
Response
—
Killed
0
Injured
0
Institution
University of Washington
Public R1 · WA
All UW cases →
~50,000 studentsUW Alert
Official alert policy
Read when and how UW says it will use UW Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 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 ALERTMulti-channel
Verified verbatim646 chars
UPDATE at 7:20 p.m.: T-Mobile is reporting the outage issue is fully resolved. UPDATE at 5:40 p.m.: T-Mobile indicated it has implemented a workaround and callers in the Puget Sound region, including in King and Pierce counties, should be able call and text 9-1-1 for emergencies. ORIGINAL POST at 1:56 p.m.: T-Mobile is reportedly experiencing a regional outage that is affecting some customers in King and Pierce counties, as well as other parts of western Washington. Some users may not be able to call or text 9-1-1. See the T-Mobile outage map: https://downdetector.com/status/t-mobile/map/ There is no known timeline for resolution yet.
Transcribed from official institutional alert archive page.
Confirmed-verbatim recovery from live institutional source.
Message elements

How the first alert is built

To check this alert, Claude Opus 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.

UPDATE at 7:20 p.m.: T-Mobile is reporting the outage issue is fully resolved. UPDATE at 5:40 p.m.: T-Mobile indicated it has implemented a workaround and callers in the Puget Sound region, including in King and Pierce counties, should be able call and text 9-1-1 for emergencies. ORIGINAL POST at 1:56 p.m.: T-Mobile is reportedly experiencing a regional outage that is affecting some customers in King and Pierce counties, as well as other parts of western Washington. Some users may not be able to call or text 9-1-1. See the T-Mobile outage map: https://downdetector.com/status/t-mobile/map/ There is no known timeline for resolution yet.

  • Sourceabsent4/25

    Final assessment

    Absent on a 4 of 25 vote. The text relays that "T-Mobile is reporting" its own fault and carries no campus office, agency or branded alert signature; the four dissenters treated the carrier itself as the source.

    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. absent: No issuing authority or branded tag appears: T-Mobile is the subject of the report, not the sender.
    2. absent: No university, agency or branded alert tag signs this; only T Mobile, the carrier reporting its own fault, is cited.
    3. absent: No university, alert brand or responding agency signs the message; only the carrier is discussed.
    4. present: "T-Mobile" is named as the carrier reporting and resolving the outage.
    5. absent: Only T-Mobile, the affected carrier, is named as reporting; no issuing agency or alert brand signs the message.
    6. absent: Only T-Mobile, the carrier at fault, is referenced; no issuing agency or alert signature appears.
    7. absent: Only T-Mobile, the carrier at fault, is named; no university, alert brand or public agency signs it.
    8. absent: Only T-Mobile is named as the carrier reporting the fault; no university, agency or alert tag identifies the sender.
    9. absent: Only T-Mobile and a downdetector link appear; no university tag or issuing agency identifies the sender.
    10. present: "T-Mobile" is named as reporting and resolving the outage.
    11. absent: No issuing authority or branded tag appears; the text only relays what T-Mobile itself reports.
    12. absent: Only T-Mobile, a carrier being reported on, appears; no issuing authority or alert branding identifies the sender.
    13. absent: No sender or branded tag identifies who is issuing this; T-Mobile is the subject, not the notifier.
    14. absent: Only the carrier T-Mobile and a Downdetector link appear: no campus office, agency or alert brand signs the message.
    15. present: "T-Mobile" is named as the entity reporting the outage and its resolution, identifying the information source.
    16. absent: No issuing authority or branded sender appears: T-Mobile is the subject, not the notifying body.
    17. absent: Only the carrier T-Mobile is named; no university, agency or alert brand issues the message.
    18. present: T-Mobile is named as the carrier reporting and resolving the outage.
    19. absent: No sender identifies itself: the text relays what "T-Mobile is reporting" without any university tag or issuing agency.
    20. absent: No issuing authority or alert brand signs the message; T-Mobile appears only as the subject reporting its own outage.
    21. absent: Only the carrier T-Mobile and a downdetector link appear; no campus, agency, or branded alert signature identifies the sender.
    22. absent: No issuing authority or alert brand signs the message; T-Mobile is the subject reported on, not the sender.
    23. absent: No university signature or agency sender appears; the text only relays what T-Mobile itself reports.
    24. absent: Only T-Mobile, the carrier at fault, is named; no university, agency or alert signature issues this.
    25. absent: Only T-Mobile, the carrier at fault, is named; no issuing agency or branded alert signature appears.
  • Hazardpresent25/25

    Final assessment

    Present, unanimous at 25 of 25. The named problem is "a regional outage" of T-Mobile service in which "Some users may not be able to call or text 9-1-1".

    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: The hazard is "a regional outage" that may block calls and texts to 9-1-1.
    2. present: The hazard is named as "a regional outage" that blocks some calls and texts to 9-1-1.
    3. present: The hazard is a "regional outage" of T-Mobile service affecting emergency calling.
    4. present: The hazard named is "a regional outage" of mobile service affecting customers.
    5. present: The hazard is a regional carrier outage in which "Some users may not be able to call or text 9-1-1".
    6. present: It names "a regional outage" of the T-Mobile network affecting calls and texts.
    7. present: The hazard is "a regional outage" affecting calls and texts including to 9-1-1.
    8. present: The hazard is specified as "a regional outage" affecting phone and 9-1-1 service.
    9. present: It names "a regional outage" affecting the ability to call or text 9-1-1.
    10. present: The hazard is "a regional outage" disrupting phone and 911 service.
    11. present: The specific problem is a regional T-Mobile outage affecting voice and text service.
    12. present: It names a regional network outage in which some users cannot call or text 9-1-1.
    13. present: It names a specific problem, "a regional outage" of T-Mobile service.
    14. present: It names "a regional outage" in which "Some users may not be able to call or text 9-1-1".
    15. present: It specifies "a regional outage" leaving users unable "to call or text 9-1-1."
    16. present: It names a regional carrier outage that may block calls and texts to 9-1-1.
    17. present: It names "a regional outage" affecting phone service including 9-1-1 calling.
    18. present: The hazard is "a regional outage" of T-Mobile service.
    19. present: It names "a regional outage" affecting phone service, including calls and texts to 9-1-1.
    20. present: The hazard is specific, a regional T-Mobile outage affecting calls and texts to 9-1-1.
    21. present: The hazard is specified as a "regional outage" leaving some users unable to call or text 9-1-1.
    22. present: The specific problem is "a regional outage" leaving some users unable "to call or text 9-1-1."
    23. present: The named hazard is "a regional outage" of T-Mobile service affecting emergency calling.
    24. present: It names "a regional outage" of T-Mobile service affecting customers.
    25. present: It names "a regional outage" leaving some users unable to call or text 9-1-1.
  • Locationpresent25/25

    Final assessment

    Present, unanimous at 25 of 25. The affected area is spelled out as "King and Pierce counties, as well as other parts of western Washington", plus the Puget Sound region.

    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: It names "King and Pierce counties" and "other parts of western Washington".
    2. present: It covers "King and Pierce counties, as well as other parts of western Washington".
    3. present: It names King and Pierce counties and other parts of western Washington.
    4. present: It covers "King and Pierce counties, as well as other parts of western Washington."
    5. present: It names King and Pierce counties and other parts of western Washington.
    6. present: The area is "King and Pierce counties, as well as other parts of western Washington".
    7. present: It affects King and Pierce counties "as well as other parts of western Washington".
    8. present: It names "King and Pierce counties, as well as other parts of western Washington".
    9. present: It specifies "King and Pierce counties, as well as other parts of western Washington".
    10. present: It affects "King and Pierce counties, as well as other parts of western Washington".
    11. present: It names King and Pierce counties, the Puget Sound region and western Washington.
    12. present: It specifies King and Pierce counties and other parts of western Washington.
    13. present: The area is given, "King and Pierce counties, as well as other parts of western Washington".
    14. present: It scopes the outage to "King and Pierce counties, as well as other parts of western Washington".
    15. present: It names "King and Pierce counties, as well as other parts of western Washington."
    16. present: It affects King and Pierce counties and other parts of western Washington.
    17. present: It covers "King and Pierce counties, as well as other parts of western Washington".
    18. present: It affects "King and Pierce counties, as well as other parts of western Washington".
    19. present: It covers "King and Pierce counties, as well as other parts of western Washington" and the Puget Sound region.
    20. present: It names King and Pierce counties and "other parts of western Washington".
    21. present: It names "King and Pierce counties, as well as other parts of western Washington".
    22. present: It names "King and Pierce counties, as well as other parts of western Washington."
    23. present: It covers "King and Pierce counties, as well as other parts of western Washington".
    24. present: It names King and Pierce counties and other parts of western Washington.
    25. present: It names "King and Pierce counties, as well as other parts of western Washington".
  • Guidanceabsent0/25

    Final assessment

    Absent, with 0 of 25 finding guidance. Readers get "See the T-Mobile outage map" and status notes, but no instruction and no alternative route to emergency help.

    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: It links an outage map but tells recipients no protective action to take.
    2. absent: Readers get an outage map link but no instruction on what to do if they need emergency help.
    3. absent: It offers a link to an outage map but no protective action for recipients.
    4. absent: No action is asked of readers apart from viewing an outage map, which is not protective guidance.
    5. absent: No action is given to recipients beyond an outage map link; no alternative to reach help is instructed.
    6. absent: It offers a status map but instructs recipients to take no action of their own.
    7. absent: Readers get an outage map link but no instruction on what to do.
    8. absent: No protective action is given to readers, only an outage map link and status notes.
    9. absent: It reports the outage and a workaround by the carrier but instructs recipients to do nothing.
    10. absent: No action is prescribed to readers beyond an outage map link; no workaround is instructed.
    11. absent: No action is asked of readers, only a link to an outage map and status updates.
    12. absent: No action is suggested to readers beyond a link to an outage map.
    13. absent: It links an outage map but asks recipients to take no protective action.
    14. absent: It offers an outage map but tells recipients nothing to do about reaching help.
    15. absent: No action is asked of recipients; the text only reports status and links to an outage map.
    16. absent: It links an outage map but asks recipients to take no protective step.
    17. absent: Recipients get an outage map link but no protective instruction or workaround to follow.
    18. absent: It links an outage map but never tells recipients what protective step to take.
    19. absent: No action is asked of recipients; the text only offers an outage map and status updates.
    20. absent: It supplies an outage map link but gives readers no protective action or alternative to take.
    21. absent: Recipients are given no action to take, only status reports and a link to an outage map.
    22. absent: Readers are offered a status map but given no action or alternative to take.
    23. absent: It offers an outage map and status but never tells recipients what to do about it.
    24. absent: It offers a downdetector map but asks no action of the reader.
    25. absent: Readers are pointed to an outage map but are never told to take any protective step.
  • Timepresent25/25

    Final assessment

    Present, unanimous at 25 of 25. The thread is stamped "ORIGINAL POST at 1:56 p.m." with updates "at 5:40 p.m." and "at 7:20 p.m.", and it concedes no resolution timeline.

    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: Stamps at "7:20 p.m.", "5:40 p.m." and "1:56 p.m." convey the timeline.
    2. present: Times are stamped at "1:56 p.m.", "5:40 p.m." and "7:20 p.m.".
    3. present: Entries are stamped "1:56 p.m.," "5:40 p.m." and "7:20 p.m."
    4. present: Entries are timed "UPDATE at 7:20 p.m." and "ORIGINAL POST at 1:56 p.m."
    5. present: Entries are timed "1:56 p.m.", "5:40 p.m." and "7:20 p.m.".
    6. present: Stamps at "1:56 p.m.", "5:40 p.m." and "7:20 p.m." establish timing.
    7. present: Entries are stamped 1:56 p.m., 5:40 p.m. and 7:20 p.m.
    8. present: Times appear, "ORIGINAL POST at 1:56 p.m.", with "no known timeline for resolution yet".
    9. present: Times "7:20 p.m.", "5:40 p.m." and "1:56 p.m." are stated.
    10. present: Stamps "1:56 p.m.", "5:40 p.m." and "7:20 p.m." are given.
    11. present: It is stamped "1:56 p.m.", "5:40 p.m." and "7:20 p.m.".
    12. present: Stamps of 1:56 p.m., 5:40 p.m. and 7:20 p.m. establish timing.
    13. present: Entries are timed, "ORIGINAL POST at 1:56 p.m." and updates at 5:40 and 7:20 p.m.
    14. present: The original is timed "1:56 p.m." with updates at "5:40 p.m." and "7:20 p.m.".
    15. present: Entries are stamped "1:56 p.m.," "5:40 p.m.," and "7:20 p.m."
    16. present: Entries are timed "ORIGINAL POST at 1:56 p.m." through 7:20 p.m.
    17. present: It carries the times "7:20 p.m.", "5:40 p.m." and "1:56 p.m."
    18. present: Stamps of 1:56 p.m., 5:40 p.m. and 7:20 p.m. establish the timeline.
    19. present: Stamps read "1:56 p.m.", "5:40 p.m." and "7:20 p.m.", with no known resolution timeline.
    20. present: Entries are timestamped "1:56 p.m.", "5:40 p.m." and "7:20 p.m." with no known resolution timeline.
    21. present: Stamps run "UPDATE at 7:20 p.m.", "5:40 p.m." and "ORIGINAL POST at 1:56 p.m.".
    22. present: Entries are timed, "UPDATE at 7:20 p.m." and "ORIGINAL POST at 1:56 p.m."
    23. present: Posts are stamped "1:56 p.m.", "5:40 p.m." and "7:20 p.m.".
    24. present: Entries are timed "7:20 p.m.", "5:40 p.m." and "1:56 p.m."
    25. present: It is stamped "1:56 p.m.", "5:40 p.m." and "7:20 p.m." with no timeline for resolution.
  • Impactpresent21/25

    Final assessment

    Present on a strong 21 of 25. The stated consequence is that "Some users may not be able to call or text 9-1-1"; four dissenters read that as the outage itself rather than a severity statement.

    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: It notes calls may not go through but does not state what that could cost anyone.
    2. absent: It notes some users may not reach 9-1-1 but never states the seriousness or danger of that gap.
    3. present: It states "Some users may not be able to call or text 9-1-1," a serious consequence.
    4. present: It states the risk that "Some users may not be able to call or text 9-1-1."
    5. present: Being unable to call or text 9-1-1 in an emergency is the stated consequence.
    6. present: It states "Some users may not be able to call or text 9-1-1", a serious consequence.
    7. absent: It stops at describing the outage without saying what a failed emergency call could cause.
    8. present: The consequence is stated: "Some users may not be able to call or text 9-1-1".
    9. present: It warns "Some users may not be able to call or text 9-1-1", a safety consequence.
    10. present: It states "Some users may not be able to call or text 9-1-1", an emergency-access consequence.
    11. present: It warns that "Some users may not be able to call or text 9-1-1" during an emergency.
    12. present: It states "Some users may not be able to call or text 9-1-1", a serious emergency consequence.
    13. present: It warns of the consequence, "Some users may not be able to call or text 9-1-1".
    14. present: Loss of the ability to call or text 9-1-1 "for emergencies" is an explicit dangerous consequence.
    15. present: Being unable to reach 9-1-1 for emergencies is the stated consequence of the outage.
    16. present: It states "Some users may not be able to call or text 9-1-1", a direct safety consequence.
    17. present: It warns "Some users may not be able to call or text 9-1-1", a safety consequence.
    18. present: It warns "Some users may not be able to call or text 9-1-1", a serious consequence.
    19. present: It states "Some users may not be able to call or text 9-1-1", a clear emergency access consequence.
    20. present: It warns of a real consequence, "Some users may not be able to call or text 9-1-1".
    21. present: Losing the ability to "call or text 9-1-1 for emergencies" is an explicitly stated serious consequence.
    22. present: The consequence is stated, "Some users may not be able to call or text 9-1-1."
    23. present: It warns that "Some users may not be able to call or text 9-1-1", a stated safety consequence.
    24. present: It warns "Some users may not be able to call or text 9-1-1", a grave consequence of the outage.
    25. absent: The lost 9-1-1 access is the outage itself, with no stated consequence or severity beyond it.

Coded by Claude Opus 5

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

About this analysis
Context

Background

Official UW Alert archive entry.
Analysis

Key Findings

Official archive page preserves complete alert text.
Outcome
See official notice for status.
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
Cite this case

Campus Alert Archive. "University of Washington: T-Mobile regional outage." Incident of June 9, 2022. Added July 2026; last updated August 2026. https://campusalertarchive.com/case/university-of-washington-uw-advisory-t-mobile-regional-outage-2022-06-09/

Download case JSON

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

Tags
washingtonuwuw-alerthazmat
Added July 2026Updated August 2026Via ingestion