Kuali incident

Build/Platform not loading in US

Critical Resolved View vendor source →

Kuali experienced a critical incident on August 19, 2025 affecting United States (Oregon), lasting 48m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2025, 12:51 AM UTC
Resolved
Aug 19, 2025, 01:39 AM UTC
Duration
48m
Detected by Pingoru
Aug 19, 2025, 12:51 AM UTC

Affected components

United States (Oregon)

Update timeline

  1. investigating Aug 19, 2025, 12:51 AM UTC

    We are seeing issues loading Kuali Build and Kuali Next-Gen products in the US region. Our engineers are currently investigating and we will keep you posted on our progress. We apologize for the inconvenience this may be causing.

  2. monitoring Aug 19, 2025, 12:57 AM UTC

    Build and next generation products should be back up again in US regions. We're continuing to monitor and investigate the root cause.

  3. resolved Aug 19, 2025, 01:39 AM UTC

    Environments have been stable and should be fully operational. We had an issue with our database instances getting into a bad state and we're following up with our database service provider (Mongo) to find out what caused. We'll be doing a full retro and provide the post mortem as soon as our investigation is complete. We apologize for any disruption this may have caused.

  4. postmortem Aug 28, 2025, 10:18 PM UTC

    We discovered long running queries in our codebase that was causing our database to get into a bad state. We’ve improved the query performance by adding additional indexes so results are returned much more efficiently. We’ve also streamlined our process when adding new queries to maintain performance in the future. Lastly, we’re also looking into long term infrastructure improvements that can better distribute performance spikes. We apologize for the inconvenience and we appreciate your patience while we resolved these issues.