Kuali Status

All Systems Operational

About This Site

Please subscribe to receive updates on any outages or issues for Kuali products (Kuali Build, Next-Gen Ready, Next-Gen Research, and Next-Gen Student). If you have questions or issues on our Classic Kuali products please send an email to support@kuali.co and we'll add you to the appropriate lists for incident/outage communication.

United States (Oregon) Operational
90 days ago
100.0 % uptime
Today
Canada (Montreal) Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jun 5, 2026

No incidents reported today.

Jun 4, 2026

No incidents reported.

Jun 3, 2026
Resolved - 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.

Jun 3, 04:00 MDT
Jun 2, 2026

No incidents reported.

Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

No incidents reported.

May 27, 2026

No incidents reported.

May 26, 2026

No incidents reported.

May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026

No incidents reported.

May 22, 2026
Resolved - 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.
May 22, 06:30 MDT