Kuali Outage History
Kuali is up right nowPingoru has recorded 53 incidents for Kuali: 27 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 1 of 720 (0%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 5 | 1 of 720 (0%) |
| July 2026 | 6 | 9 of 744 (1%) |
| August 2026 | 2 | 1 of 744 (0%) |
| September 2026 | 3 | 12 of 720 (2%) |
| October 2026 | 1 | 2 of 590 (0%) |
Incidents, newest first
Minor October 14, 2025 Platform/Build - Issues with submissions going to error 15h 41m United States (Oregon), Canada (Montreal)
Started Oct 14, 2025, 09:33 PM UTC· resolved Oct 15, 2025, 01:15 PM UTC
- investigating Oct 14, 2025, 09:33 PM UTC
We have received reports of document submissions going to error. We are actively investigating and we will keep you posted.
- monitoring Oct 14, 2025, 09:59 PM UTC
We've resolved the errors on document submit and the system is fully operational again. We are continuing to monitor and we apologize for the inconvenience.
- resolved Oct 15, 2025, 01:15 PM UTC
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.
- postmortem Dec 11, 2025, 04:59 PM UTC
After investigation we found this incident was caused by networking issues with one of our service providers \(Fly.io\). We are looking into adding additional alerts when our system jobs get into a bad state and long term infrastructure improvements that are more robust to help avoid in the future. We apologize for the inconvenience caused by this issue.
Minor August 19, 2025 Platform/Build slowness 1h 52m United States (Oregon), Canada (Montreal)
Started Aug 19, 2025, 09:10 PM UTC· resolved Aug 19, 2025, 11:03 PM UTC
- investigating Aug 19, 2025, 09:10 PM UTC
We are seeing slowness loading Kuali Build and Kuali Next-Gen products. Our engineers are currently investigating and we will keep you posted on our progress. We apologize for the inconvenience this may be causing.
- investigating Aug 19, 2025, 09:34 PM UTC
Our engineers have address the slowness issue with Kuali Build and Kuali Next-Gen products. We’re continuing to monitor and investigate the root cause and we’ll keep you posted as we know more.
- resolved Aug 19, 2025, 11:03 PM UTC
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.
- postmortem Sep 11, 2025, 04:44 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.
Critical August 19, 2025 Build/Platform not loading in US 48m United States (Oregon)
Started Aug 19, 2025, 12:51 AM UTC· resolved Aug 19, 2025, 01:39 AM UTC
- 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.
- 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.
- 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.
- 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.
Minor August 14, 2025 Platform/Build intermittent issues 1h 13m United States (Oregon), Canada (Montreal)
Started Aug 14, 2025, 08:44 PM UTC· resolved Aug 14, 2025, 09:57 PM UTC
- investigating Aug 14, 2025, 08:44 PM UTC
We are receiving reports of intermittent issues loading Kuali Build and Kuali Next-Gen products. Our engineers are currently investigating and we will keep you posted on our progress. We apologize for the inconvenience this may be causing.
- monitoring Aug 14, 2025, 09:02 PM UTC
Kuali Build and Kuali Next-Gen products should now be loading and our engineers are continuing to monitor performance. We'll keep you posted as we have more information.
- resolved Aug 14, 2025, 09:57 PM UTC
We wanted to provide an update on the recent errors in the Build/Platform system. These were caused by two separate issues that happened concurrently: 1. An outage with our third-party provider, Fly.io (more info can be found at https://status.flyio.net) 2. A database issue that reduced our system’s capacity We restarted our fly.io instances to restore operations and cycled our Mongo database clusters to alleviate the database issue. The system is now fully operational, and the database is stable. We’re continuing to work with our providers to fully understand what led to the outages and are continue to monitor performance closely to ensure everything runs smoothly. We apologize for the inconvenience and we appreciate your patience while we resolved these issues.
- postmortem Aug 14, 2025, 09:57 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.
Notice July 28, 2025 Build/Platform not loading –
Started Jul 28, 2025, 11:30 PM UTC· resolved Jul 28, 2025, 11:30 PM UTC
- resolved Jul 29, 2025, 07:47 AM UTC
Users experienced issues loading the application. The problem was due to a database-related issue and was resolved after services recovered.
- postmortem Jul 29, 2025, 01:42 PM UTC
The issue was caused by increased load on the database, which temporarily impacted application availability. We’re making performance improvements to help prevent future incidents.
Notice June 17, 2025 Platform/Build Momentary Access Interruption 1h
Started Jun 17, 2025, 02:00 PM UTC· resolved Jun 17, 2025, 03:00 PM UTC
- resolved Jul 21, 2025, 01:36 PM UTC
Between 8:52am and 9:10am CT, some users may have experienced intermittent access issues in the production environment. We suspected an issue with Fly.io and noted that they had implemented a temporary fix during the disruption. As minor issues persisted, we rotated infrastructure by scaling up new machines and retiring older ones. Access returned to normal shortly after.
- postmortem Jul 21, 2025, 01:36 PM UTC
The brief outage was caused by an infrastructure issue at [Fly.io](http://Fly.io), which was mitigated by their temporary fix. We’re tracking improvements on their end and enhancing visibility into upstream provider status.
Minor June 16, 2025 Error when initiating forms 15m United States (Oregon), Canada (Montreal)
Started Jun 16, 2025, 02:03 PM UTC· resolved Jun 16, 2025, 02:18 PM UTC
- investigating Jun 16, 2025, 02:03 PM UTC
Users are receiving an error message when initiating forms through links. Initiated forms are available in the user’s Drafts list. Our engineers are investigating the issue and will keep you posted as we have more information.
- resolved Jun 16, 2025, 02:18 PM UTC
Our team identified the root cause and have deployed a fix to restore access. We apologize for the inconvenience this caused and if you have any further questions or issues please feel free to submit a support ticket.
- postmortem Jul 15, 2025, 10:56 PM UTC
To follow up on this issue, our team identified the root cause as an issue retiring form redirects put in place related to the redesign of the popup modals for action list and my documents. This inadvertently affected form initiation on a specific path that hadn’t been caught in our verification. Once identified, we rolled out a fix to restore form creation and we’ll be adding additional testing in the future to avoid this type of issue in the future. Our apologies for the disruption and if you have any further questions please let us know.
Notice June 10, 2025 Platform/Build Quick Interruption - Canada –
Started Jun 10, 2025, 11:00 AM UTC· resolved Jun 10, 2025, 11:00 AM UTC
- resolved Jul 21, 2025, 01:16 PM UTC
Our Canada environments briefly went down due to a temporary issue with one of our service providers, Fly.io.
- postmortem Jul 21, 2025, 01:16 PM UTC
The root cause was a third-party outage at [Fly.io](http://Fly.io). We’re working with their team to stay ahead of such events and are reviewing our redundancy strategies to minimize future impact.
Notice June 4, 2025 Brief Platform/Build Disruption – Canada Region –
Started Jun 04, 2025, 04:00 PM UTC· resolved Jun 04, 2025, 04:00 PM UTC
- resolved Jul 21, 2025, 01:11 PM UTC
We experienced a brief disruption in our Canada environments due to a temporary spike in MongoDB traffic. The issue resolved quickly on its own.
- postmortem Jul 21, 2025, 01:11 PM UTC
The spike in MongoDB traffic temporarily overwhelmed resources, causing a short interruption. We are optimizing database traffic handling and refining monitoring thresholds to help prevent similar issues.
Minor May 19, 2025 Intermittent errors with notifications 5h 38m United States (Oregon), Canada (Montreal)
Started May 19, 2025, 09:56 PM UTC· resolved May 20, 2025, 03:35 AM UTC
- investigating May 19, 2025, 09:56 PM UTC
Our mail provider Mailgun.com is currently experiencing degraded performance, so Kuali system notifications are not currently sending as expected and you may see errors on Notification steps in workflow. They are investigating the issue, and we will keep you posted as we have more information.
- monitoring May 19, 2025, 10:58 PM UTC
Our mail provider (Mailgun.com) has confirmed that a fix has been implemented and Kuali system notifications should be sending as expected now. For those Notification workflow steps that went to error you can use the ‘retry’ option to successfully send. Our engineers are continuing to monitor and we apologize for the inconvenience.
- resolved May 20, 2025, 03:35 AM UTC
This incident has been resolved.
- postmortem Jul 16, 2025, 04:09 PM UTC
To follow-up on this issue, the issue was caused by degraded performance with our mail provider \(Mailgun.com\). Our monitoring shows that all impacted notifications sent as expected after the fix was implemented. We apologize for the inconvenience and if you have any further questions please let us know.
Major May 16, 2025 Build/Platform Access Issues for Canadian Customers 31m Canada (Montreal)
Started May 16, 2025, 08:55 PM UTC· resolved May 16, 2025, 09:26 PM UTC
- investigating May 16, 2025, 08:55 PM UTC
We are currently investigating an issue where the Build/Platform is not loading or displaying an error message. This issue appears to be affecting customers located in Canada only. Our team is actively working to identify the root cause and restore full functionality as quickly as possible. We apologize for the inconvenience and we will be provide updates as we learn more.
- investigating May 16, 2025, 08:55 PM UTC
We are continuing to investigate this issue.
- resolved May 16, 2025, 09:26 PM UTC
We identified that the access issues impacting users in Canada were caused by an overload of database connections. Our engineering team promptly scaled up resources to reduce the load and successfully restore normal performance. We are continuing to monitor the system closely to ensure ongoing stability.
- postmortem Jun 04, 2025, 03:52 PM UTC
The issue has been resolved. It was caused by an overload of database connections, and we are looking into implementing connection limits and alerts to help prevent future occurrences.
Minor May 1, 2025 Intermittent Connection Issues –
Started May 01, 2025, 09:00 AM UTC· resolved May 01, 2025, 09:00 AM UTC
- resolved May 08, 2025, 08:58 PM UTC
We experienced intermittent connection issues between 3:06 AM and 5:12 AM MT.
- postmortem May 08, 2025, 08:58 PM UTC
Our engineer noted that the proxy restart failed, which caused errors. The manual restart was successful and the issue is now resolved.
Notice April 10, 2025 Platform/Build brief system disruption –
Started Apr 10, 2025, 05:30 PM UTC· resolved Apr 10, 2025, 05:30 PM UTC
- resolved Jun 04, 2025, 03:47 PM UTC
We experienced a brief system disruption that quickly self-resolved.
- postmortem Jun 04, 2025, 03:47 PM UTC
The issue was caused by an unexpected database node outage and quickly self-resolved.
Minor March 31, 2025 Brief Interruption to Platform/Build Services –
Started Mar 31, 2025, 08:30 AM UTC· resolved Mar 31, 2025, 08:30 AM UTC
- resolved Apr 01, 2025, 04:16 PM UTC
We experienced a brief disruption that may have impacted access to some services for a short period.
- postmortem Apr 01, 2025, 04:17 PM UTC
Our engineers confirmed that one of the database nodes temporarily went down but immediately recovered on its own, restoring service without intervention.
Major February 4, 2025 Build/Platform not loading or going to error –
Started Feb 04, 2025, 02:30 PM UTC· resolved Feb 04, 2025, 02:30 PM UTC
- resolved Feb 04, 2025, 03:59 PM UTC
Users are seeing errors or slowness when accessing Build/Platform environments.
- postmortem Feb 04, 2025, 03:59 PM UTC
The issue was caused by a recent code deployment. Our team identified the problem and rolled back the change, successfully resolving the errors.
Major January 9, 2025 Build environments unable to load –
Started Jan 09, 2025, 05:45 PM UTC· resolved Jan 09, 2025, 05:45 PM UTC
- resolved Jan 09, 2025, 06:06 PM UTC
We are seeing an issue when loading Build environments, and we are actively troubleshooting the issue.
- postmortem Jan 09, 2025, 06:19 PM UTC
Our team identified the root cause as an issue with a recently deployed code. Once identified, the code was rolled back to restore service.
Notice January 8, 2025 Build database connection errors –
Started Jan 08, 2025, 11:30 AM UTC· resolved Jan 08, 2025, 11:30 AM UTC
- resolved Jan 17, 2025, 01:40 PM UTC
We are experiencing unexpected database connection errors that may result in intermittent API and application errors. Our team is actively investigating the issue and working to implement solutions to enhance system stability.
- postmortem Jan 17, 2025, 01:43 PM UTC
The issue was caused by an unexpected database connection error, which the system automatically resolved. While mitigation steps are in place, these errors still occur sporadically. We are actively working on further improvements to enhance database stability and reduce recurrence. Thank you for your understanding.