Kuali Incident History

Operational

kuali.co ↗2 components

checked Sep 7, 2026 6:11 PM UTC · Kuali's official status page

Kuali is up and running.

Kuali is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.

Kuali status

Be the first to know

Statusfield watches Kuali alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

Kuali incident history

2 reports published by Kuali in the last 30 days

When Kuali breaks, it is typically resolved in 1h 43m — median across 1 resolved incidents over 90 days.

September 7, 2026

Integrations going to 500 Error in Kuali Platform (US region only)

Last update Sep 7, 2026 · 17:16 UTC

resolvedSep 6 · 01:30 UTC
From approximately Sat Sep 5, 7:43 PM MDT to Mon Sep 7, 6:41 AM MDT, integrations in our US regions were failing with status 500 errors. We've corrected the issue and scripted a retry on all affected documents. This was caused by a routine security upgrade to a third-party networking library, which changed how outbound secure connections are made and prevented integration requests from reaching their destination. No data was transmitted to external systems — affected steps simply did not run. We've rolled back the upgrade and added automated test coverage for this path to prevent a recurrence. Our Canada region was not affected.

Reported by Kuali on their status page.

September 2, 2026

Platform/Build Service Interruption

Last update Sep 2, 2026 · 16:34 UTC

resolvedSep 2 · 14:51 UTC
From approximately 10:51 a.m. to 10:56 a.m. ET, 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.

Reported by Kuali on their status page.