Is Kuali down?

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.

A routine security upgrade to a third-party networking library changed how outbound secure connections were handled, causing integrations in our US regions to fail from approximately **September 5 at 7:43 PM MDT through September 7 at 6:41 AM MDT**, Canada was not affected. ### Resolution and Follow-Up We rolled back the upgrade and retried affected documents. We have also added automated testing and are improving monitoring and alerting to help prevent and more quickly identify similar issues in the future.

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.

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 review confirmed that an unexpected configuration issue at [Fly.io](http://Fly.io) disrupted inbound network traffic to Platform and Build. The third-party provider corrected the configuration, and we are reviewing our monitoring and escalation processes to improve how quickly similar upstream incidents are identified and communicated.

We are investigating an issue that is causing PDF generation to fail intermittently for some users. Our team is working to identify the cause and restore reliable functionality as quickly as possible. We will share additional updates as more information becomes available.

Our team has identified a potential cause of the issue affecting browser-based PDF exports and workflow notifications with PDF attachments. We are currently testing a fix and will provide another update as soon as testing is complete.

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.

The issue was caused by an unexpected change introduced during a routine deployment. Our engineers deployed a fix and are taking steps to help prevent similar disruptions in the future.

We are investigating an issue causing browser-based PDF exports to fail in the US environment. Workflows that generate or attach a PDF may time out after several minutes and move the affected document into an Error status. Notifications that do not include a PDF are not affected.

Our engineers are continuing to investigate the underlying cause of the PDF export failures in the US environment. We will provide another update as soon as more information is available.

We are continuing to investigate this issue.

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.

A change to a third-party service disrupted the PDF generation process, causing some PDF exports and workflow notifications with PDF attachments to fail. The issue has been resolved, and affected notification steps were retried.