Saint Joseph's University IT Status - Network Outage - Hawk Hill – Incident details

All systems operational

IT Scheduled Maintenance Calendar

Network Outage - Hawk Hill

Resolved
Operational
Started over 2 years agoLasted 6 hours 18 minutes

Affected

Collaboration and Enterprise Services

Operational from 2:23 PM to 8:42 PM

CAS

Operational from 2:23 PM to 8:42 PM

Websites

Operational from 2:23 PM to 8:42 PM

SJU Sites

Operational from 2:23 PM to 8:42 PM

MachForms

Operational from 2:23 PM to 8:42 PM

Academic Tools

Operational from 2:23 PM to 8:42 PM

Updates
  • Resolved
    UTC
    Resolved

    The issue is now resolved. All services have returned to normal. A full postmortem report will be produced detailing the cause of this disruption and the permanent fix that was implemented.

  • Update
    UTC
    Update

    We believe we have identified the source of the traffic that was fully congesting our internal firewall, and are working on a fix.

    No immediate ETA on resolution.

  • Update
    UTC
    Update

    We are continuing to work on a fix for this outage. All noted systems should be considered unavailable until a resolution is implemented:

    • Degree Works
    • Banner (Self-Service, Registration, and Administrative Pages)
    • BDMS
    • Cognos
    • University WordPress Websites (Sites and Clubs)
    • MachForms
    • VPN/Webvpn
    • EZProxy
    • HawkPrint
  • Update
    UTC
    Update

    The issue has become more severe, and major systems are now offline. We are continuing to engage and escalate with the vendor.

  • Update
    UTC
    Update

    The issue affecting the performance of certain on-campus services is still ongoing. The vendor is engaged, and we are continuing to actively troubleshoot.

    The slowed performance is intermittent, and only affects the Hawk Hill location.

  • Identified
    UTC
    Identified

    There is currently an issue affecting the Hawk Hill internal network. Certain applications, network connectivity, and VPN may be sluggish or sporadically unavailable.

    We are continuing to troubleshoot this issue.