Campus Alert Archive
SVC

Canvas outage after third-party learning-platform security incident

AI-generated · every claim is source-linked
WAcybersecurityemergency notificationhigh confidence
Compare →

On May 7, 2026, Skagit Valley College notified the community that Instructure reported a security incident affecting portions of Canvas, temporarily making Canvas unavailable. Follow-up notices on May 8 reported service restoration and later full restoration with vendor findings about Free-For-Teacher account vulnerabilities.

Alerts
3
Response
—
Killed
0
Injured
0
Institution
Skagit Valley College
Community College · WA
All SVC cases →
~8,000 studentsSVC Alert / Emergency Communications
Documented Timeline

Alert Sequence

3 messages in sequence · 3 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 ALERTEmail
Verified verbatim3291 chars
Skagit Valley College has been notified by Instructure, the vendor that operates the Canvas learning management system, of a recent security incident affecting portions of its platform. Based on information currently available, certain SVC user information may have been involved in the incident. At this time, there is no indication that Skagit Valley College systems, networks, or infrastructure were compromised. The incident occurred within the third-party vendor environment used to provide Canvas services to colleges and universities across the country. Canvas is currently unavailable as Instructure continues responding to the incident. We will continue to monitor and provide updates regarding platform availability and related information as additional details become available. According to information provided by Instructure, there is currently no evidence that passwords, Social Security numbers, dates of birth, financial information, or other sensitive government-issued identifiers were involved in this incident. The vendor's investigation remains ongoing, and additional information may become available as their review continues. Although the current risk appears limited, incidents of this nature may increase the likelihood of phishing attempts, ransomware-related messages, fraudulent emails, text messages, phone calls, or other scams that attempt to appear legitimate. Members of the college community may receive communications that reference Canvas, coursework, institutional business, or account activity in an attempt to create urgency or solicit personal information. We encourage all students, faculty, and staff to remain especially vigilant in the coming weeks. Please use caution when: Opening unexpected emails or attachments Clicking links requesting login credentials or personal information Responding to messages that create urgency or request sensitive information Receiving communications that appear to reference Canvas conversations, coursework, or institutional business unexpectedly Receiving suspicious messages related to ransomware, payment demands, account verification, or technology support requests Skagit Valley College will never request passwords, Social Security numbers, banking information, or multifactor authentication codes through unsolicited email, phone calls, or text messages. As a precaution, members of the college community are encouraged to: Monitor their accounts for unusual activity Use strong and unique passwords Report suspicious emails or messages to the SVC Information Technology department Avoid clicking on unfamiliar links, even if the message appears to come from a known source If you receive suspicious communications, believe you may have interacted with a fraudulent message, or have concerns related to this incident, please contact the SVC Information Technology support team at mv.help@skagit.edu for assistance. The college is actively reviewing the information provided regarding this incident and will continue coordinating with appropriate parties as necessary to better understand the scope of the event and determine whether any additional actions are warranted. We appreciate your patience and partnership as we continue to monitor this situation and provide updates as appropriate.
Verify this quote
SVC Emergency Communications — May 7, 2026 Canvas security incidentskagit.edufind archived copies
Verbatim text transcribed from the official SVC or university page cited in sourceUrl.
UPDATEEmail
Verified verbatim645 chars
Canvas is currently accessible once again. Service was restored last evening around approximately 7:30 p.m., with confirmation from Canvas around 9:15 p.m. However, some users reported Canvas difficulties after this time. We are not currently seeing continued issues in Canvas. Please see yesterday's message below from campus leadership regarding the overall security breach related to the outage. We encourage continued caution with any suspicious links, images, or attachments claiming to be related to Canvas. If you encounter ongoing difficulties within Canvas, such as tools not functioning properly, please contact eLearning@skagit.edu.
Verify this quote
SVC Emergency Communications — May 8, 2026 8:30 a.m. service restoredskagit.edufind archived copies
Verbatim text transcribed from the official SVC or university page cited in sourceUrl.
UPDATEEmail+2h 35m
Verified verbatim2749 chars
Skagit Valley College would like to provide an update regarding the recent security incident involving Canvas, the learning management system operated by Instructure. Canvas services have now been restored and are fully available for use. According to information provided by Instructure, the vendor identified and contained the unauthorized activity and temporarily placed portions of the platform into maintenance mode as a precautionary measure while the issue was investigated. What Happened Instructure has informed the Washington State Board for Community and Technical Colleges (SBCTC) that the unauthorized activity involved changes made to pages viewed by some students and instructors while logged into Canvas. The vendor reports that it worked with an independent forensic partner and, at this time, has found no evidence that the unauthorized actor: Obtained institutional account credentials Established persistent access within the environment Exfiltrated additional data related to SVC users According to Instructure, the incident originated through vulnerabilities associated with Canvas Free-For-Teacher accounts, which have since been temporarily disabled while additional security measures are implemented. Impact to Skagit Valley College At this time, there continues to be no indication that SVC systems, networks, or infrastructure were compromised. Instructure has also stated there is currently no evidence that passwords, Social Security numbers, dates of birth, banking information, or other sensitive government-issued identifiers were involved in the incident. Reminder to Remain Vigilant Although Canvas services have been restored, members of the college community are encouraged to remain vigilant regarding potential phishing attempts, fraudulent emails, or suspicious messages that may attempt to leverage awareness of this incident. Please continue to use caution when: Opening unexpected communications Clicking unfamiliar links Responding to requests for personal or institutional information Important Reminders SVC will never request passwords, multifactor authentication codes, Social Security numbers, or banking information through unsolicited email, phone calls, or text messages. Suspicious messages or cybersecurity concerns should be reported to the Information Technology department at mv.help@skagit.edu. Users are encouraged to continue monitoring accounts for unusual activity and maintain strong, unique passwords. The college will continue coordinating with Instructure and monitoring any additional information related to this incident. We appreciate your patience, understanding, and partnership as we worked through this disruption and restored services to the campus community.
Verify this quote
SVC Emergency Communications — May 8, 2026 11:05 a.m. fully restoredskagit.edufind archived copies
Verbatim text transcribed from the official SVC or university page cited in sourceUrl.
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.

Skagit Valley College has been notified by Instructure, the vendor that operates the Canvas learning management system, of a recent security incident affecting portions of its platform. Based on information currently available, certain SVC user information may have been involved in the incident. At this time, there is no indication that Skagit Valley College systems, networks, or infrastructure were compromised. The incident occurred within the third-party vendor environment used to provide Canvas services to colleges and universities across the country. Canvas is currently unavailable as Instructure continues responding to the incident. We will continue to monitor and provide updates regarding platform availability and related information as additional details become available. According to information provided by Instructure, there is currently no evidence that passwords, Social Security numbers, dates of birth, financial information, or other sensitive government-issued identifiers were involved in this incident. The vendor's investigation remains ongoing, and additional information may become available as their review continues. Although the current risk appears limited, incidents of this nature may increase the likelihood of phishing attempts, ransomware-related messages, fraudulent emails, text messages, phone calls, or other scams that attempt to appear legitimate. Members of the college community may receive communications that reference Canvas, coursework, institutional business, or account activity in an attempt to create urgency or solicit personal information. We encourage all students, faculty, and staff to remain especially vigilant in the coming weeks. Please use caution when: Opening unexpected emails or attachments Clicking links requesting login credentials or personal information Responding to messages that create urgency or request sensitive information Receiving communications that appear to reference Canvas conversations, coursework, or institutional business unexpectedly Receiving suspicious messages related to ransomware, payment demands, account verification, or technology support requests Skagit Valley College will never request passwords, Social Security numbers, banking information, or multifactor authentication codes through unsolicited email, phone calls, or text messages. As a precaution, members of the college community are encouraged to: Monitor their accounts for unusual activity Use strong and unique passwords Report suspicious emails or messages to the SVC Information Technology department Avoid clicking on unfamiliar links, even if the message appears to come from a known source If you receive suspicious communications, believe you may have interacted with a fraudulent message, or have concerns related to this incident, please contact the SVC Information Technology support team at mv.help@skagit.edu for assistance. The college is actively reviewing the information provided regarding this incident and will continue coordinating with appropriate parties as necessary to better understand the scope of the event and determine whether any additional actions are warranted. We appreciate your patience and partnership as we continue to monitor this situation and provide updates as appropriate.

  • Sourcepresent25/25

    Final assessment

    Majority finds S present based on Skagit Valley College.

    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: Source present: Skagit Valley College appears as the issuing institution. Independent read 1.
    2. present: The message identifies the sender through Skagit Valley College. Independent read 2.
    3. present: Institutional source is clear via Skagit Valley College. Independent read 3.
    4. present: Sender authority is Skagit Valley College, meeting the source criterion. Independent read 4.
    5. present: Named organization Skagit Valley College functions as the source tag. Independent read 5.
    6. present: Source element satisfied by Skagit Valley College self-identification. Independent read 6.
    7. present: The alert is framed as an official Skagit Valley College notice. Independent read 7.
    8. present: Present source because Skagit Valley College is named in the body. Independent read 8.
    9. present: Authority wording points to Skagit Valley College as the issuer. Independent read 9.
    10. present: Source=1 from the Skagit Valley College naming. Independent read 10.
    11. present: Clear institutional authorship: Skagit Valley College. Independent read 11.
    12. present: The university or college name Skagit Valley College counts as source. Independent read 12.
    13. present: Source present through explicit Skagit Valley College language. Independent read 13.
    14. present: Issuing body is identifiable as Skagit Valley College. Independent read 14.
    15. present: Rubric source met by Skagit Valley College. Independent read 15.
    16. present: Self-named institution Skagit Valley College is enough for source. Independent read 16.
    17. present: Source coded present due to Skagit Valley College. Independent read 17.
    18. present: The text attributes the notice to Skagit Valley College. Independent read 18.
    19. present: Branded or named sender Skagit Valley College is present. Independent read 19.
    20. present: Source element is present via Skagit Valley College. Independent read 20.
    21. present: Institutional identity Skagit Valley College anchors the source. Independent read 21.
    22. present: Sender is established by Skagit Valley College wording. Independent read 22.
    23. present: Source verdict 1 based on Skagit Valley College. Independent read 23.
    24. present: Named campus authority Skagit Valley College satisfies source. Independent read 24.
    25. present: Present: Skagit Valley College identifies who is communicating. Independent read 25.
  • Hazardpresent25/25

    Final assessment

    Majority finds H present based on security incident / Canvas unavailable.

    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 present: security incident / Canvas unavailable is a specific threat type. Independent read 1.
    2. present: The text names security incident / Canvas unavailable rather than a generic emergency. Independent read 2.
    3. present: Specific hazard language appears as security incident / Canvas unavailable. Independent read 3.
    4. present: Hazard element met by security incident / Canvas unavailable. Independent read 4.
    5. present: Concrete threat: security incident / Canvas unavailable. Independent read 5.
    6. present: Hazard=1 because security incident / Canvas unavailable is specified. Independent read 6.
    7. present: Named hazard security incident / Canvas unavailable satisfies the rubric. Independent read 7.
    8. present: The causal threat is security incident / Canvas unavailable. Independent read 8.
    9. present: Hazard coded present from security incident / Canvas unavailable wording. Independent read 9.
    10. present: Present hazard via security incident / Canvas unavailable. Independent read 10.
    11. present: Threat type is explicit: security incident / Canvas unavailable. Independent read 11.
    12. present: Rubric hazard satisfied by security incident / Canvas unavailable. Independent read 12.
    13. present: Hazard is not vague; it is security incident / Canvas unavailable. Independent read 13.
    14. present: The message identifies security incident / Canvas unavailable as the hazard. Independent read 14.
    15. present: Specific threat security incident / Canvas unavailable is stated. Independent read 15.
    16. present: Hazard present through security incident / Canvas unavailable. Independent read 16.
    17. present: Named danger security incident / Canvas unavailable counts for hazard. Independent read 17.
    18. present: Hazard element is present: security incident / Canvas unavailable. Independent read 18.
    19. present: Clear hazard reference to security incident / Canvas unavailable. Independent read 19.
    20. present: The alert opens or centers on security incident / Canvas unavailable. Independent read 20.
    21. present: Hazard verdict 1 for security incident / Canvas unavailable. Independent read 21.
    22. present: Specificity of security incident / Canvas unavailable meets hazard. Independent read 22.
    23. present: Threat named as security incident / Canvas unavailable. Independent read 23.
    24. present: Hazard is security incident / Canvas unavailable, clearly stated. Independent read 24.
    25. present: Present: security incident / Canvas unavailable is a concrete hazard. Independent read 25.
  • Locationabsent0/25

    Final assessment

    Majority finds L absent: no physical place; Canvas platform only.

    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. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 1.
    2. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 2.
    3. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 3.
    4. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 4.
    5. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 5.
    6. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 6.
    7. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 7.
    8. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 8.
    9. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 9.
    10. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 10.
    11. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 11.
    12. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 12.
    13. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 13.
    14. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 14.
    15. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 15.
    16. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 16.
    17. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 17.
    18. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 18.
    19. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 19.
    20. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 20.
    21. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 21.
    22. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 22.
    23. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 23.
    24. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 24.
    25. absent: Location absent: no building, campus, or place is named (no physical place; Canvas platform only). pass 25.
  • Guidancepresent25/25

    Final assessment

    Majority finds G present based on use caution, monitor accounts, report suspicious messages.

    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: Guidance present: use caution, monitor accounts, report suspicious messages instructs recipients. Independent read 1.
    2. present: Protective or operational direction: use caution, monitor accounts, report suspicious messages. Independent read 2.
    3. present: Action language includes use caution, monitor accounts, report suspicious messages. Independent read 3.
    4. present: Guidance element met by use caution, monitor accounts, report suspicious messages. Independent read 4.
    5. present: Recipients are told to use caution, monitor accounts, report suspicious messages. Independent read 5.
    6. present: Guidance=1 from use caution, monitor accounts, report suspicious messages. Independent read 6.
    7. present: Instructional content: use caution, monitor accounts, report suspicious messages. Independent read 7.
    8. present: The message directs people to use caution, monitor accounts, report suspicious messages. Independent read 8.
    9. present: Guidance coded present via use caution, monitor accounts, report suspicious messages. Independent read 9.
    10. present: Present guidance through use caution, monitor accounts, report suspicious messages. Independent read 10.
    11. present: Do-this language appears as use caution, monitor accounts, report suspicious messages. Independent read 11.
    12. present: Guidance satisfied by use caution, monitor accounts, report suspicious messages. Independent read 12.
    13. present: Actionable instruction: use caution, monitor accounts, report suspicious messages. Independent read 13.
    14. present: Guidance element is present: use caution, monitor accounts, report suspicious messages. Independent read 14.
    15. present: Clear instruction: use caution, monitor accounts, report suspicious messages. Independent read 15.
    16. present: Community told to use caution, monitor accounts, report suspicious messages. Independent read 16.
    17. present: Guidance present in use caution, monitor accounts, report suspicious messages. Independent read 17.
    18. present: Protective action use caution, monitor accounts, report suspicious messages counts. Independent read 18.
    19. present: The alert instructs use caution, monitor accounts, report suspicious messages. Independent read 19.
    20. present: Guidance verdict 1 for use caution, monitor accounts, report suspicious messages. Independent read 20.
    21. present: Operational order: use caution, monitor accounts, report suspicious messages. Independent read 21.
    22. present: Guidance is explicit via use caution, monitor accounts, report suspicious messages. Independent read 22.
    23. present: Instruction named: use caution, monitor accounts, report suspicious messages. Independent read 23.
    24. present: Guidance from use caution, monitor accounts, report suspicious messages is sufficient. Independent read 24.
    25. present: Present: use caution, monitor accounts, report suspicious messages is guidance to recipients. Independent read 25.
  • Timepresent25/25

    Final assessment

    Majority finds T present based on recent / currently unavailable / coming weeks.

    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: Time present: recent / currently unavailable / coming weeks is a temporal cue. Independent read 1.
    2. present: When is stated via recent / currently unavailable / coming weeks. Independent read 2.
    3. present: Time language includes recent / currently unavailable / coming weeks. Independent read 3.
    4. present: Time element met by recent / currently unavailable / coming weeks. Independent read 4.
    5. present: Clock or calendar cue recent / currently unavailable / coming weeks appears. Independent read 5.
    6. present: Time=1 from recent / currently unavailable / coming weeks. Independent read 6.
    7. present: Named time recent / currently unavailable / coming weeks satisfies the rubric. Independent read 7.
    8. present: The message times the event with recent / currently unavailable / coming weeks. Independent read 8.
    9. present: Time coded present using recent / currently unavailable / coming weeks. Independent read 9.
    10. present: Present time via recent / currently unavailable / coming weeks. Independent read 10.
    11. present: Temporal reference recent / currently unavailable / coming weeks is enough. Independent read 11.
    12. present: Time satisfied by recent / currently unavailable / coming weeks wording. Independent read 12.
    13. present: Schedule language: recent / currently unavailable / coming weeks. Independent read 13.
    14. present: Time element is present: recent / currently unavailable / coming weeks. Independent read 14.
    15. present: Clear when: recent / currently unavailable / coming weeks. Independent read 15.
    16. present: Date or hour cue recent / currently unavailable / coming weeks appears. Independent read 16.
    17. present: Time present through recent / currently unavailable / coming weeks. Independent read 17.
    18. present: Timing recent / currently unavailable / coming weeks counts for time. Independent read 18.
    19. present: The alert specifies recent / currently unavailable / coming weeks as when. Independent read 19.
    20. present: Time verdict 1 for recent / currently unavailable / coming weeks. Independent read 20.
    21. present: Temporal scope: recent / currently unavailable / coming weeks. Independent read 21.
    22. present: Time is explicit via recent / currently unavailable / coming weeks. Independent read 22.
    23. present: Time marker: recent / currently unavailable / coming weeks. Independent read 23.
    24. present: Time from recent / currently unavailable / coming weeks is sufficient. Independent read 24.
    25. present: Present: recent / currently unavailable / coming weeks identifies timing. Independent read 25.
  • Impactabsent0/25

    Final assessment

    Majority finds I absent: risk appears limited; no clear harm severity.

    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: Impact absent: hazard is named without consequence language (risk appears limited; no clear harm severity). Independent read 1.
    2. absent: No severity or harm statement appears (risk appears limited; no clear harm severity). Independent read 2.
    3. absent: Impact=0; nothing about injury, death, or damage risk (risk appears limited; no clear harm severity). Independent read 3.
    4. absent: Consequence wording is missing (risk appears limited; no clear harm severity). Independent read 4.
    5. absent: Does not state what the hazard could do (risk appears limited; no clear harm severity). Independent read 5.
    6. absent: Impact not established beyond the hazard name (risk appears limited; no clear harm severity). Independent read 6.
    7. absent: No life-threatening or dangerous severity clause (risk appears limited; no clear harm severity). Independent read 7.
    8. absent: Impact coded absent: risk appears limited; no clear harm severity. Independent read 8.
    9. absent: Severity is not articulated (risk appears limited; no clear harm severity). Independent read 9.
    10. absent: People harm is not described (risk appears limited; no clear harm severity). Independent read 10.
    11. absent: Impact element fails: risk appears limited; no clear harm severity. Independent read 11.
    12. absent: No Sutton-style consequence language (risk appears limited; no clear harm severity). Independent read 12.
    13. absent: Impact missing in this text (risk appears limited; no clear harm severity). Independent read 13.
    14. absent: Without consequence phrasing, impact is 0 (risk appears limited; no clear harm severity). Independent read 14.
    15. absent: Impact verdict 0: risk appears limited; no clear harm severity. Independent read 15.
    16. absent: Hazard alone does not satisfy impact (risk appears limited; no clear harm severity). Independent read 16.
    17. absent: No explicit harm to people or property (risk appears limited; no clear harm severity). Independent read 17.
    18. absent: Impact not present (risk appears limited; no clear harm severity). Independent read 18.
    19. absent: Severity cue absent (risk appears limited; no clear harm severity). Independent read 19.
    20. absent: Consequence language not found (risk appears limited; no clear harm severity). Independent read 20.
    21. absent: Impact fails the rubric (risk appears limited; no clear harm severity). Independent read 21.
    22. absent: Does not convey potential harm (risk appears limited; no clear harm severity). Independent read 22.
    23. absent: Impact unsupported: risk appears limited; no clear harm severity. Independent read 23.
    24. absent: No impact statement (risk appears limited; no clear harm severity). Independent read 24.
    25. absent: Absent impact: risk appears limited; no clear harm severity. Independent read 25.

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

About this analysis
Context

Background

On May 7, 2026, Skagit Valley College notified the community that Instructure reported a security incident affecting portions of Canvas, temporarily making Canvas unavailable. Follow-up notices on May 8 reported service restoration and later full restoration with vendor findings about Free-For-Teacher account vulnerabilities.
Analysis

Key Findings

Full English text recovered from the official SVC Emergency Communications page.
Spanish parallel versions exist on the same page and were not transcribed as separate alerts.
Outcome
Canvas was restored the evening of May 7 (confirmed ~9:15 p.m.) with some residual user reports overnight; by May 8 11:05 a.m. SVC reported full restoration. No indication SVC systems were compromised.
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
    Emergency Communications (Skagit Valley College Security Services)
    skagit.edu
    archived copy
Cite this case

Campus Alert Archive. "Skagit Valley College: Canvas outage after third-party learning-platform security incident." Incident of May 7, 2026. Added July 2026. https://campusalertarchive.com/case/skagit-valley-college-canvas-security-incident-outage-2026-05-07/

Download case JSON

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

Tags
skagit-valley-collegecybersecuritycanvascommunity-college
Added July 2026Updated July 2026Via ingestion