UCSB incident

Network Service Disruption

Minor Resolved View vendor source →

UCSB experienced a minor incident on September 28, 2025 affecting Campus Network, lasting 14d 22h. The incident has been resolved; the full update timeline is below.

Started
Sep 28, 2025, 09:42 PM UTC
Resolved
Oct 13, 2025, 07:50 PM UTC
Duration
14d 22h
Detected by Pingoru
Sep 28, 2025, 09:42 PM UTC

Affected components

Campus Network

Update timeline

  1. investigating Sep 28, 2025, 09:42 PM UTC

    The NOC is reporting intermittent network loss on the campus network. There may be additional disruptions during troubleshooting. Further updates will be provided as information becomes available. Thank you for your patience and support.

  2. identified Sep 29, 2025, 01:02 AM UTC

    The network problems were isolated to a set of wireless controllers which were taken off line at 4:13pm. Service has been stable since that time. Additional troubleshooting will take place over the next several hours.

  3. investigating Sep 29, 2025, 06:42 PM UTC

    Wireless network instability has returned. The network team is investigating

  4. investigating Oct 01, 2025, 04:27 PM UTC

    Network stability was substantially improved late Monday evening. Work is continuing with vendor technical support teams

  5. investigating Oct 01, 2025, 05:10 PM UTC

    A network disruption occurred approximately 9:50-10:05am today. This is part of the ongoing investigation

  6. investigating Oct 03, 2025, 04:22 PM UTC

    We are investigating reports of network disruptions from various locations on campus

  7. investigating Oct 07, 2025, 10:04 PM UTC

    The probable cause of network disruptions was isolated at 5:58 pm on Saturday and network service has remained stable. There is a slight risk of disruption as remaining tests are conducted, however these activities take place outside of classroom instruction hours to minimize any potential impact.

  8. monitoring Oct 10, 2025, 05:18 PM UTC

    Network service has remained stable 5:58pm on Saturday, Oct. 4th following isolation of misbehaving equipment. The network team continues to closely monitor the situation.

  9. monitoring Oct 13, 2025, 07:49 PM UTC

    The monitoring period ended with no further incidences. This issue is considered resolved

  10. resolved Oct 13, 2025, 07:50 PM UTC

    This incident has been resolved.