weather campus emergency notice — network outage
AI-generated · every claim is source-linkedUniversity of Missouri published an official alert on or about 2020-10-22. Full text is preserved from the official archive.
- Alerts
- 1
- Response
- —
- Killed
- 0
- Injured
- 0
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.
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.
Oct. 22, 2020 11:29 a.m. Due to the networking outage this morning, email delivery will be delayed for some messages that were sent or received between 6-10 a.m. this morning. Those messages are currently queued, but are being processed and should be delivered in the next few hours. 10:19 a.m. Services are coming back up now and should begin to be accessible. Check your internet connections, email, VPN, and report any problems to 573-882-5000. We'll provide updates about afternoon classes as soon as possible. 9:51 a.m. Due to continued technical issues, Mizzou is postponing all classes that start before noon. Find more information here: status.missouri.edu 8:54 a.m. Due to widespread technical issues, 9 a.m. classes at MU are postponed. Stay tuned for updates. Find more information here: status.missouri.edu 8:00 a.m. We are aware of a campuswide internet outage. The MU Division of IT is working to solve the issue.
Sourcepresent25/25
Final assessment
Present, 25 of 25. The updates name "The MU Division of IT" as working the problem and say "Mizzou is postponing all classes", identifying the university and unit behind the notice.
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
- present: It identifies "Mizzou" and "The MU Division of IT" as the responding and issuing parties.
- present: "The MU Division of IT" and "Mizzou" identify the university unit issuing the updates.
- present: "Mizzou" and "The MU Division of IT" identify the institution and the responsible unit.
- present: The MU Division of IT and Mizzou are named as the source of these updates.
- present: "Mizzou" and "The MU Division of IT" are named as the parties reporting and fixing the problem.
- present: "The MU Division of IT" and Mizzou are identified as the parties reporting and fixing the problem.
- present: "The MU Division of IT" and Mizzou are named as the ones handling and announcing the problem.
- present: "The MU Division of IT" and Mizzou are named as the responding and issuing parties.
- present: "The MU Division of IT" and Mizzou are named as the entities handling the outage.
- present: "The MU Division of IT" and "Mizzou" identify the sender of the outage updates.
- present: "The MU Division of IT" and Mizzou are identified as the responding and sending parties.
- present: "The MU Division of IT" and "Mizzou" identify the university unit sending the updates.
- present: "Mizzou" and "The MU Division of IT" identify who is reporting the outage.
- present: "Mizzou" and "The MU Division of IT" identify the sending organization.
- present: "The MU Division of IT" and Mizzou are identified as the responding and announcing bodies.
- present: "The MU Division of IT" and Mizzou are identified as the responding and announcing bodies.
- present: "Mizzou", "MU" and "The MU Division of IT" are identified as the source of the updates.
- present: "The MU Division of IT" and Mizzou are named as the responding and issuing parties.
- present: Updates come from Mizzou and "The MU Division of IT", identifying the responsible office.
- present: "The MU Division of IT" and Mizzou are identified as the source of the updates.
- present: "Mizzou" and "The MU Division of IT" are identified as the ones reporting and fixing the outage.
- present: "The MU Division of IT" and "Mizzou" identify the university unit issuing the updates.
- present: "The MU Division of IT" and Mizzou are named as the responding and issuing parties.
- present: It names "the MU Division of IT" and Mizzou as the responding and issuing authority.
- present: "Mizzou" and "The MU Division of IT" identify the university as the sender.
Hazardpresent25/25
Final assessment
Present, 25 of 25. The trouble is named specifically as "a campuswide internet outage" and, later, "the networking outage this morning", not a vague incident.
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
- present: The threat is named specifically as "a campuswide internet outage" and networking failure.
- present: The hazard is a specific "campuswide internet outage" and networking failure, not a vague incident.
- present: The problem is named specifically as a "campuswide internet outage" and networking failure.
- present: The hazard is specific: a "campuswide internet outage" and continued technical issues.
- present: It names a "campuswide internet outage" and "networking outage", a specific technological hazard.
- present: It names a concrete failure, a "campuswide internet outage" and "networking outage", not a vague incident.
- present: It names a "campuswide internet outage" and networking failure, a specific disruption.
- present: It names a "campuswide internet outage" and networking failure, a specific disruption.
- present: A "campuswide internet outage" and networking failure are the specific named problem.
- present: A "campuswide internet outage" and "networking outage" is a specific named disruption.
- present: It names a "campuswide internet outage" and "networking outage", a specific technical hazard.
- present: The hazard is specific: a "campuswide internet outage" and "networking outage".
- present: A "campuswide internet outage" and networking failure are named specifically.
- present: The hazard is a "campuswide internet outage" and "widespread technical issues", specifically named.
- present: The problem is specifically a "campuswide internet outage" and networking failure, not a vague incident.
- present: It names a "campuswide internet outage" and networking failure, a specific technological hazard.
- present: It names a "campuswide internet outage" and "networking outage", a specific service hazard.
- present: The hazard is a specific technical one: "a campuswide internet outage" and networking failure.
- present: The threat is named concretely as a "campuswide internet outage" and networking failure.
- present: The problem is named specifically as a "campuswide internet outage" and networking failure.
- present: The problem is named as a "campuswide internet outage" and networking failure, a specific disruption.
- present: It names a "campuswide internet outage" and "networking outage", a specific disruption.
- present: It names a "campuswide internet outage" and networking failure, a specific disruption.
- present: The problem is specific: a "campuswide internet outage" and networking failure, not a vague incident.
- present: It names a "campuswide internet outage" and networking failure, a specific disruption.
Locationpresent25/25
Final assessment
Present, 25 of 25. The outage is described as "campuswide" and the postponements apply to "9 a.m. classes at MU", locating the disruption on the university network.
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
- present: The outage is described as "campuswide" and affecting classes "at MU".
- present: "campuswide" and "at MU" locate the outage on the university network.
- present: It is described as campuswide and affecting classes "at MU", a located disruption.
- present: It describes the outage as campuswide and refers to classes at MU.
- present: The outage is described as campuswide at MU, locating it across the campus.
- present: The outage is described as "campuswide" and affecting classes "at MU".
- present: The outage is described as campuswide at MU, locating it.
- present: The outage is described as campuswide and affecting classes "at MU".
- present: The outage is described as campuswide at MU, locating it on campus.
- present: It is campuswide at MU, with services and classes on that campus affected.
- present: The outage is described as "campuswide" and affecting classes "at MU".
- present: It says the outage is "campuswide" and affects classes "at MU".
- present: The outage is described as campuswide at MU.
- present: It is described as campuswide, affecting MU classes and systems.
- present: It describes the outage as campuswide and affecting classes "at MU".
- present: The outage is described as campuswide, affecting MU.
- present: The outage is described as campuswide and affecting MU classes.
- present: It is described as "campuswide" and affecting classes "at MU".
- present: It is described as campuswide at MU, with a link to status.missouri.edu.
- present: "campuswide" and "classes at MU" locate the disruption on the MU campus.
- present: It is described as campuswide, affecting MU classes and university systems.
- present: The outage is described as campuswide and classes "at MU" are affected, giving place.
- present: The outage is described as campuswide at MU.
- present: It says the outage is campuswide and affects classes at MU.
- present: The outage is described as campuswide "at MU", locating it.
Guidancepresent25/25
Final assessment
Present, 25 of 25. Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000" and to watch status.missouri.edu.
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
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: It tells readers to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to check connections, report problems to 573-882-5000, and stay tuned.
- present: Recipients are told to check connections and VPN, report problems to 573-882-5000, and stay tuned.
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000" and stay tuned.
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000" and stay tuned.
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: It tells readers to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: It tells people to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: People are told to check connections, report problems to 573-882-5000, and stay tuned.
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: It tells readers to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Recipients are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: People are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
- present: Readers are told to check connections, report problems to 573-882-5000, and stay tuned for updates.
- present: Readers are told to "Check your internet connections, email, VPN, and report any problems to 573-882-5000".
Timepresent25/25
Final assessment
Present, 25 of 25. Every update carries a clock stamp, from "8:00 a.m." to "11:29 a.m." on "Oct. 22, 2020", plus the "between 6-10 a.m." mail delay window.
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
- present: Multiple timestamps appear, including "11:29 a.m." and delays "between 6-10 a.m. this morning".
- present: Several clock stamps appear, including "8:00 a.m." and "11:29 a.m." on Oct. 22.
- present: Each entry carries a clock time such as "11:29 a.m." and "8:00 a.m."
- present: Each entry carries a clock time such as "11:29 a.m." and "8:00 a.m.".
- present: Multiple clock times, "this morning", and "between 6-10 a.m." give the timeline precisely.
- present: Each update carries a clock time and references messages "sent or received between 6-10 a.m. this morning".
- present: Multiple clock stamps appear, including "11:29 a.m." and messages sent between 6 and 10 a.m.
- present: Each entry carries a clock time such as "9:51 a.m." and refers to "this morning".
- present: Multiple timestamps from 8:00 a.m. to 11:29 a.m. on Oct. 22 mark the sequence.
- present: Each entry carries a clock time such as "9:51 a.m." on Oct. 22, 2020.
- present: Multiple clock stamps from 8:00 a.m. to 11:29 a.m. anchor each update.
- present: Each update is timestamped, from "8:00 a.m." through "11:29 a.m." on Oct. 22, 2020.
- present: Sequential stamps like "11:29 a.m." and "8:00 a.m." pin the timeline.
- present: Each update carries a clock time such as "11:29 a.m." and "8:00 a.m." on Oct. 22.
- present: Multiple clock stamps appear, including "8:00 a.m." and "this morning" between 6 and 10 a.m.
- present: Each entry carries a clock time such as "9:51 a.m." and the date Oct. 22, 2020.
- present: Each update carries a clock time such as "11:29 a.m." and "8:00 a.m." on Oct. 22, 2020.
- present: Each update carries a clock time such as "9:51 a.m." and the date Oct. 22, 2020.
- present: Each update carries a clock time such as "9:51 a.m." and refers to messages sent "between 6-10 a.m.".
- present: Each update carries a clock time such as "11:29 a.m." and "8:00 a.m.".
- present: Successive entries are clock stamped from 8:00 a.m. to 11:29 a.m. on Oct. 22, 2020.
- present: Each update carries a clock time such as "11:29 a.m." and refers to "this morning".
- present: Each update carries a clock time such as "11:29 a.m." on Oct. 22, 2020.
- present: Each entry carries a clock time from 8:00 a.m. through 11:29 a.m.
- present: Each update carries a clock time such as "11:29 a.m." and "this morning".
Impactpresent24/25
Final assessment
Present, 24 of 25. Concrete effects are spelled out: "email delivery will be delayed", classes before noon "postponed", services inaccessible. One read dissented, wanting physical danger rather than disruption.
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
- present: Effects are spelled out: classes postponed, email delivery delayed, services inaccessible.
- present: It states consequences: classes "are postponed" and "email delivery will be delayed", concrete effects.
- present: Consequences are spelled out: delayed email delivery and postponement of all classes before noon.
- present: Consequences are spelled out: classes postponed and email delivery delayed for messages sent 6 to 10 a.m.
- present: It states the effects: classes before noon postponed and email delivery delayed, real consequences of the outage.
- present: It states the concrete effects: classes postponed and "email delivery will be delayed for some messages".
- present: It spells out consequences: delayed email delivery and postponement of all classes starting before noon.
- present: It spells out the consequences: postponed 9 a.m. and pre-noon classes and delayed email delivery.
- present: It spells out consequences: classes postponed and email delivery delayed for messages sent between 6 and 10 a.m.
- present: Consequences are spelled out: classes postponed and "email delivery will be delayed" for hours.
- present: It states real consequences: classes postponed before noon and email delivery delayed for hours.
- present: It spells out consequences: classes before noon postponed and email delivery delayed for hours.
- present: It states classes are postponed and email delivery delayed, the outage's concrete effects.
- present: It states the concrete consequences: delayed email delivery and postponement of all classes before noon.
- present: It spells out consequences: classes postponed and "email delivery will be delayed" for queued messages.
- present: It spells out consequences: classes before noon postponed and email delivery delayed for hours.
- present: It states concrete consequences: classes before noon postponed and email delivery delayed for hours.
- present: It spells out effects: classes postponed before noon and email delivery delayed for hours.
- present: It spells out consequences: classes before noon postponed and email delivery delayed for hours.
- absent: Class postponements are described, but no harm or danger from the outage is stated.
- present: It spells out consequences: classes postponed and "email delivery will be delayed" for messages sent between 6 and 10 a.m.
- present: It spells out consequences: classes before noon postponed and email delivery delayed for hours.
- present: It states consequences: classes postponed and "email delivery will be delayed" for hours.
- present: Consequences are spelled out: classes postponed and email delivery delayed for messages sent 6 to 10 a.m.
- present: It states real consequences: classes before noon postponed and email delivery delayed for hours.
Coded by Claude Opus 5
Systematic AI judgments with visible reasoning, not human-validated codings.
Background
Key Findings
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.
- Official
Campus Alert Archive. "University of Missouri: weather campus emergency notice — network outage." Incident of October 22, 2020. Added July 2026; last updated August 2026. https://campusalertarchive.com/case/university-of-missouri-network-outage-2020-10-22/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.