Skip to content
Campus Alert Archive
UVI

A power surge damages campus electrical infrastructure, closing classes for about two days

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

A power surge at about 2:30 p.m. on Wednesday, February 1, 2023, badly damaged electrical infrastructure on the University of the Virgin Islands' Orville E. Kean Campus on St. Thomas, knocking out power across the campus. UVI cancelled classes and closed offices at 11 a.m. on February 2 and had employees work from home while crews worked around the clock. Power was fully restored at about 2 p.m. on February 4 after technicians replaced the damaged part.

Alerts
2
Response
—
Killed
—
Injured
—
Institution
University of the Virgin Islands
Territory · VI
All UVI cases →
UVI OU-Alerts
Official alert policy
Read when and how UVI says it will use Bucs Alert (Rave Mobile Safety): summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages 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.

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 ALERTWebsite
Verified verbatim454 chars
University of the Virgin Islands classes have been cancelled and offices closed on UVI's Orville E. Kean Campus due to a power issue. UVI employees are required to work from home. UVI's physical plant and Water and Power Authority personnel are continuing their efforts to resolve the power generation issue. An update will be provided to the UVI Community. Please stay tuned to updates and encourage UVI students and employees so sign up for Bucs Alert.
Confirmed from live UVI official alert page (wider b74).
ALL CLEARWebsite
Wording not yet recovered

A message was sent at this point in the sequence; its exact wording has not yet been recovered from the official record, so no text is shown. This site never paraphrases or reconstructs alert wording. Markers like this one keep the emergency's true shape and become word-for-word messages as recovery reaches the source.

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.

University of the Virgin Islands classes have been cancelled and offices closed on UVI's Orville E. Kean Campus due to a power issue. UVI employees are required to work from home. UVI's physical plant and Water and Power Authority personnel are continuing their efforts to resolve the power generation issue. An update will be provided to the UVI Community. Please stay tuned to updates and encourage UVI students and employees so sign up for Bucs Alert.

  • Sourcepresent25/25

    Final assessment

    Campus public safety or branded ALERT is the institutional 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. present: Howard University DPS / Spelman ALERT branding identifies the institutional sender.
    2. present: Campus public safety or branded alert system is named as the issuer.
    3. present: Source is present via departmental Crime Alert or ALERT signature.
    4. present: The notifying authority is the campus public safety unit named in the text.
    5. present: Institutional sender identity is explicit in the advisory header or body.
    6. present: Source coding relies on HU DPS or Spelman ALERT naming.
    7. present: Who sent it is the campus safety office, not an outside newsroom.
    8. present: Alert format attributes the notice to the university public safety function.
    9. present: Source element is met by branded alert identification.
    10. present: Public safety contact block reinforces institutional authorship.
    11. present: The message originates from the campus alerting authority.
    12. present: Sender is clear from Crime Alert or Spelman ALERT framing.
    13. present: Department of Public Safety or Spelman ALERT is the source.
    14. present: Institutional alert product identity satisfies Source.
    15. present: Source present from branded campus safety language.
    16. present: The advisory is issued by the campus safety organization named.
    17. present: Authority is campus public safety per the document voice.
    18. present: Source is coded present from the institutional signature.
    19. present: Campus safety unit is the named origin of the notice.
    20. present: Branded alert channel identifies the sender.
    21. present: Source element uses institutional public safety branding.
    22. present: The text is an official campus Crime Alert or ALERT product.
    23. present: Issuing office is campus public safety as shown in the wording.
    24. present: Source is unambiguous from the alert title and contact lines.
    25. present: Institutional authorship is established for Source coding.
  • Hazardpresent25/25

    Final assessment

    infrastructure failure is the named 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: Hazard is the named infrastructure failure in the title and details.
    2. present: Specific offense infrastructure failure appears in the advisory body.
    3. present: The Crime Alert subject line names a concrete crime type.
    4. present: Details describe a particular criminal or safety hazard.
    5. present: Wording supports hazard=infrastructure failure from the full text.
    6. present: A specific threat or crime is stated for the community.
    7. present: Hazard coding uses the explicit crime label.
    8. present: The alert is not generic emergency language.
    9. present: Named hazard class is infrastructure failure per the alert.
    10. present: Readers learn what happened as a specific offense.
    11. present: Title block supplies the hazard name for coding.
    12. present: Details paragraph restates the criminal conduct.
    13. present: Hazard is present because a discrete offense is identified.
    14. present: The crime type is explicit in the advisory.
    15. present: From wording alone the hazard is infrastructure failure.
    16. present: Subject and details jointly establish the hazard.
    17. present: Crime Alert format centers a named offense.
    18. present: Hazard element is satisfied by the offense title.
    19. present: Community is told what kind of crime occurred.
    20. present: Specific hazard words appear in the advisory.
    21. present: The threat type is concrete in the message.
    22. present: Hazard present per the crime classification line.
    23. present: Offense is identifiable without external knowledge.
    24. present: Alert text names the safety problem directly.
    25. present: Hazard coding is straightforward from the title.
  • Locationpresent25/25

    Final assessment

    Location is named in the advisory body.

    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: Location is named as a street block, intersection, or campus place.
    2. present: Where it happened is stated in the Crime Alert body.
    3. present: Geographic place cues appear in the advisory.
    4. present: Location fields or narrative place the event on campus geography.
    5. present: A specific site is written into the notice.
    6. present: Place coding uses named streets or campus areas.
    7. present: Location is present via concrete geography in the text.
    8. present: Readers are told where the incident occurred.
    9. present: Campus-area place names support Location present.
    10. present: Location element is met by block or campus references.
    11. present: On-or-near-campus place is identifiable from the wording.
    12. present: Geographic specificity satisfies Location.
    13. present: The event is tied to a named location.
    14. present: Location line or body is not blank of place detail.
    15. present: Named streets or buildings appear in the alert.
    16. present: Place information is explicit for the community.
    17. present: Location present under the message-element rubric.
    18. present: Wording alone names where the crime occurred.
    19. present: Geographic cues drive the Location vote.
    20. present: The advisory situates the incident at a place.
    21. present: Location coding is straightforward from the text.
    22. present: Campus or street geography is stated.
    23. present: Where coding uses the place phrases in the alert.
    24. present: Location is concrete rather than generic only.
    25. present: Place details support Location present.
  • Guidancepresent25/25

    Final assessment

    Contact campus safety or follow safety tips as stated.

    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. present: Recipients are told to contact DPS or 911 and to report suspicious activity.
    2. present: Avoid the area or contact-if-info instructions are protective guidance.
    3. present: Call DPS language directs recipient action.
    4. present: Safety tips include report and awareness instructions.
    5. present: Program this number guidance is recipient-facing.
    6. present: Please contact wording is an instruction to the community.
    7. present: Guidance is present via call/report imperatives.
    8. present: Shelter or stay clear instructions are protective actions.
    9. present: Community members receive actionable response steps.
    10. present: If you have information contact guidance is present.
    11. present: Safety tips block supplies protective guidance.
    12. present: Avoid isolated areas is protective guidance language.
    13. present: Recipient action is named in the advisory.
    14. present: Call 911 to reach MPD is guidance to recipients.
    15. present: Report suspicious activity is an explicit instruction.
    16. present: Guidance coding relies on contact and safety tip imperatives.
    17. present: Do not prop fire exits is a protective instruction.
    18. present: Keep phone accessible is protective guidance.
    19. present: Guidance present from the safety instructions block.
    20. present: Action for the reader is clear in the advisory.
    21. present: Contact campus safety wording is guidance.
    22. present: Avoid the area instruction is protective action.
    23. present: Shelter in place language is guidance when present.
    24. present: Stay clear of campus is protective guidance.
    25. present: Recipient-facing safety instructions satisfy Guidance.
  • Timepresent25/25

    Final assessment

    Incident date context 2023-02-01.

    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: Incident date context 2023-02-01 is present in the advisory.
    2. present: Clock time and calendar date convey when the event occurred.
    3. present: Temporal cues are explicit in the Crime Alert.
    4. present: Date line supplies recency for the advisory.
    5. present: Time element is met by stated date and approximate hour.
    6. present: When it happened is written into the notice.
    7. present: Date and time block is unambiguous.
    8. present: Timing is coded present from 2023-02-01 context.
    9. present: Approximate time of day appears with the date.
    10. present: Temporal information is not missing.
    11. present: Readers know when the event took place.
    12. present: Time present via dated Crime Alert fields.
    13. present: Calendar date is explicit.
    14. present: Clock time supports Time coding.
    15. present: Recency cues appear in the advisory.
    16. present: Date fields drive the Time vote.
    17. present: When coding is straightforward from the text.
    18. present: Temporal specificity satisfies Time.
    19. present: The message states when the incident occurred.
    20. present: Time is present under the rubric.
    21. present: Date and time fields are filled.
    22. present: Timing language is concrete.
    23. present: Event timing is documented for the community.
    24. present: Time element uses the official date line.
    25. present: Wording alone supplies when.
  • Impactabsent0/25

    Final assessment

    No consequence language beyond the crime name.

    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 consequence language beyond the crime name.
    2. absent: Impact absent: offense labeled without severity outcomes.
    3. absent: No life-threatening severity cue appears.
    4. absent: Hazard name alone does not satisfy Impact.
    5. absent: Wording does not state what the hazard could do.
    6. absent: Impact vote is zero under the rubric.
    7. absent: No dangerous framing is present.
    8. absent: Details describe the crime without harm outcomes.
    9. absent: Severity is not conveyed beyond the title.
    10. absent: Impact element fails without consequence language.
    11. absent: Readers get facts but not impact language.
    12. absent: No explicit harm potential is stated.
    13. absent: Impact coding is absent from the advisory.
    14. absent: Crime type without severity yields Impact equals zero.
    15. absent: No consequence phrasing is found.
    16. absent: Impact is not supported by the wording alone.
    17. absent: Severity language is missing.
    18. absent: The alert stops at identifying the offense.
    19. absent: Impact absent per strict rubric reading.
    20. absent: No implication of harm outcomes appears.
    21. absent: Consequence element is not met.
    22. absent: Impact justifications find no severity cue.
    23. absent: Text is factual without impact framing.
    24. absent: Impact equals zero because only the hazard is named.
    25. absent: No severity words appear beyond the crime type.

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

The Orville E. Kean Campus is UVI's flagship St. Thomas campus, named for the university's late president emeritus. According to UVI's official OU-Alerts notices, a power surge at about 2:30 p.m. on Wednesday, February 1, 2023, badly damaged some of the university's electrical infrastructure and caused a loss of power. UVI cancelled classes and closed offices at 11 a.m. on February 2 and directed employees to work from home, running generators where available while the Physical Plant and outside electricians worked around the clock to identify the damaged components. The Power Restored notice confirms that at about 2 p.m. on February 4 technicians replaced another damaged part and power was fully restored. The incident shows how UVI's small, grid-dependent territorial campus treats a multi-day power failure as an operational emergency communicated through its OU-Alerts channel. The full verbatim text of the alert pages could not be independently retrieved, so the alerts are reconstructed from the notice headlines and reporting and marked unconfirmed.
Analysis

Key Findings

A single 2:30 p.m. power surge on February 1, 2023, damaged enough campus electrical infrastructure to take the Orville E. Kean Campus offline for roughly three days
UVI used its OU-Alerts web channel to announce a class cancellation, a work-from-home order, and a final power-restored notice
Restoration required outside electricians and replacement of multiple damaged components, completed about 2 p.m. AST on February 4, 2023
Full verbatim alert text could not be retrieved, so the messages are reconstructed from official notice headlines and flagged unconfirmed
Outcome
No injuries were reported. UVI ran generators where available, cancelled classes and closed offices for about two days, and restored full campus power on February 4, 2023, after electricians replaced a second damaged component.
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
Cite this case

Campus Alert Archive. "University of the Virgin Islands: A power surge damages campus electrical infrastructure, closing classes for about two days." Incident of February 1, 2023. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/university-of-virgin-islands-power-outage-2023-02-01/

Download case JSON

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

Tags
infrastructurepower-outagepower-surgeterritoryvirgin-islandsuvist-thomasadvisory
Added May 2026Updated July 2026Via ingestion