Kuali Outage History

From approximately 9:52 a.m. to 10:03 a.m. CT, some users were unable to access Platform and Build. The interruption was caused by a networking incident affecting Fly.io, a third-party infrastructure service provider used by Kuali. Fly.io resolved the issue, and access to the affected applications was restored. We apologize for the disruption.

Our engineers have deployed a fix, and the PDF generation issue should now be resolved. We will also retry affected workflow jobs to ensure previously failed notifications are processed.

Our engineers have deployed a fix, and PDF exports now appear to be working as expected. They are also developing a script to address documents that entered an Error status because of the PDF generation issue. We will provide another update once that work is complete.

Our engineers identified a configuration issue that was limiting system capacity below the expected level. The configuration has been corrected, and system performance has improved. We will continue to monitor the environment and are taking additional steps to help prevent this issue from recurring.

Our environments experienced intermittent performance degradation from approximately 10:00–10:27 AM MT due to an incident with our hosting provider that delayed replacement servers from coming online as expected. This temporarily reduced system capacity and resulted in slower performance. Once the replacement servers were available, performance returned to normal.

Our US environments were briefly unable to load from ~12:54-12:56pm MT due to a temporary issue with our database provider and our monitoring shows that performance has stabilized.

A deployment-related infrastructure issue caused some application servers to become unhealthy, resulting resulting in intermittent access errors for some users in Kuali Platform products. The affected servers have been removed and service has been restored.

We've resolved the issue affecting all environments. The issue was caused by a database migration associated with a recent code deploy that encountered an unexpected error in our US environments. The migration has been corrected, and all services are now operating normally. As a follow-up, we are reviewing the migration process to identify what led to the error and implement additional safeguards to help prevent similar issues in the future. Our apologies for the disruption this caused.

This issue is now resolved and environments in the US region should be back up again. The incident was caused by an unexpected database coordination issue that prevented the database cluster from operating normally, resulting in a temporary service disruption. The issue was identified and the cluster was restored to its expected operating state. We'll be doing a full retro and take the necessary steps to avoid this type of disruption in the future. Our apologies for the disruption this caused your users.

This incident has been resolved. We identified the issue as a database connectivity problem related to a MongoDB security certificate. The necessary updates have been completed, service has been fully restored, and we are enhancing our monitoring and certificate management processes to reduce the risk of similar issues in the future.

Platform/Build customers using the Canada environment may have experienced issues accessing Catalog, API, and Identity services. Our monitoring alerted us to the issue at 7:32 AM, and services were confirmed recovered by 11:27 AM.

From ~3:15-3:40pm (MDT) users may have seen "The server responded with an error. Please try again" when working within apps or documents in the Kuali platform (US region only). This was due to our deployment that included an upgrade and migration that took longer than expected and caused the errors until it finished.

On June 3, 2026, the Kuali Platform service for US customers experienced an issue that affected application and document loading between approximately 6:32 PM and 7:24 PM PT. During this time, some users may have encountered forms that failed to load and remained in a loading state. This was due to a deployment configuration issue that didn't load the necessary resources properly.

The Academic Ops Catalog service for US customers experienced intermittent errors between approximately 3:24 AM and 5:54 AM ET due to a temporary infrastructure issue affecting the catalog database. During this time, some users may have encountered errors when accessing catalog content. No catalog data was lost or corrupted, and the catalogs are available at this time. After investigating, we have confirmed that the system was able to recover on its own, and the catalog service is fully operational again, and scheduled catalog reindex jobs have completed.

We have received reports of documents that were unable to save due to an error with the user gadget on the form. Our team has resolved the issues, and we identified an error within a recent deploy that has been corrected. We’ll be looking into ways to avoid this type of issue in the future and we apologize for the inconvenience this caused. If you have any further questions please feel free to reach out to our support team.

We will be undergoing database maintenance during our maintenance window Sunday 4/5/26 from 6-10am MDT. Please be aware that Kuali Platform products and APIs will be unavailable for use during this time.

Users experienced a brief period where the Platform/Build was not loading due to a temporary disruption in service connectivity.

Our Canada environments briefly went down due to a temporary issue with our identity service.

We've resolved the issue and apps are loading as expected. We apologize for the inconvenience and are taking steps to prevent similar issues in the future.

The service disruption that occurred today was due to an outage with one of our infrastructure providers, Fly.io. This impacted our ability to deploy services and resulted in temporary unavailability of our environments. The issue has been resolved, and all services are now operational and performing as expected. We are reviewing our deployment processes to further reduce the risk and impact of similar provider-related incidents in the future. Additional details are available on the Fly.io status page at https://status.flyio.net/

Our team has resolved the issues causing the missing variables within workflows and errors with integrations on forms. We identified an error within a recent deploy that has been corrected. We’ll be looking into ways to avoid this type of issue in the future and we apologize for the inconvenience this caused. If you have any further questions please feel free to reach out to our support team.

Some users may have experienced intermittent errors when accessing pages due to a server entering an unhealthy state. Once identified, our engineers eliminated the unhealthy node and brought a healthy server online to stabilize the environment. During the transition, some customers may have noticed temporary slowness, particularly with actions such as PDF exports or workflow executions. The migration was completed successfully, and the system has since returned to normal operation.

Our monitoring is complete, and the system is operating normally. The issue was related to networking problems with our service provider, Fly.io. We apologize for the inconvenience and are taking steps to prevent similar issues in the future.

The issue affecting Kuali Build and Kuali Next-Gen products is now resolved and our monitoring is complete. Our engineers have deployed a fix to improve the query performance that was causing this slowness. and we have scaled up our systems to ensure improved performance across environments. We apologize for the inconvenience this caused. If you have any further questions or issues please feel free to submit a support ticket.

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.