Civitas Learning incident

Impact to Civitas applications due to AWS outage

Minor Resolved View vendor source →

Civitas Learning experienced a minor incident on October 20, 2025 affecting Degree Map and Data Warehouse (Explore) and 1 more component, lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 04:35 PM UTC
Resolved
Oct 23, 2025, 01:13 PM UTC
Duration
2d 20h
Detected by Pingoru
Oct 20, 2025, 04:35 PM UTC

Affected components

Degree MapData Warehouse (Explore)Advising Analytics (Inspire)Inspire for AdvisorsCourse Success Coaching (Inspire for Faculty)Course InsightsInitiative Analysis (Impact)Administrative Analytics (Illume)College SchedulerAcademic Planning

Update timeline

  1. investigating Oct 20, 2025, 04:35 PM UTC

    AWS is experiencing some widespread issues due to some internal issue with Amazon's own network. Specifically they have identified the root cause as an underlying internal subsystem responsible for monitoring the health of Amazon's network load balancers. This is potentially affecting data freshness and connectivity to our application(s).

  2. investigating Oct 20, 2025, 04:39 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 20, 2025, 05:56 PM UTC

    AWS has reportedly identified the issue and some systems are showing signs of recovery. Civitas is continuing to closely monitor any updates from AWS and will continue to update here until status is back to completely operational.

  4. identified Oct 21, 2025, 02:00 PM UTC

    Civitas has been able to recover site access to our tools, but the AWS outage is still impacting data freshness. Civitas is continuing to closely monitor all updates from AWS and will continue to update here until the status is back to completely operational.

  5. monitoring Oct 21, 2025, 08:42 PM UTC

    AWS services have recovered and we are starting to see recovery within Civitas tools as a result. We are closely monitoring this recovery and expecting data freshness to be within the threshold starting tomorrow. We will have an update regarding this outage again tomorrow with results.

  6. identified Oct 22, 2025, 12:18 PM UTC

    We've identified an additional error causing data freshness delays and we are investigating it as a top priority.

  7. identified Oct 22, 2025, 04:21 PM UTC

    We are continuing to work on a fix for this data freshness issue.

  8. monitoring Oct 22, 2025, 09:31 PM UTC

    A fix has been implemented and we are starting to see successful data updates. We are continuing to monitor the issue.

  9. resolved Oct 23, 2025, 01:13 PM UTC

    This incident has been fully resolved.