Kuali experienced a minor incident on July 13, 2026 affecting United States (Oregon) and Canada (Montreal), lasting 2h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 13, 2026, 02:07 PM UTC
We are investigating a service disruption affecting Platform and Build customers. Users may experience issues loading pages, accessing applications, or completing actions within the system. Our team is actively working to restore normal service. We will provide additional updates as more information becomes available.
- investigating Jul 13, 2026, 02:35 PM UTC
We are continuing to investigate this issue. We will share another update as more information becomes available.
- investigating Jul 13, 2026, 03:01 PM UTC
Our engineers are continuing their investigation and working toward a resolution. We will provide another update as soon as additional information is available.
- investigating Jul 13, 2026, 03:38 PM UTC
Our engineers are still actively working to restore normal service. We will provide another update as soon as there is additional progress to share.
- investigating Jul 13, 2026, 04:06 PM UTC
We apologize for the disruption. Our engineers have increased system capacity, and performance has improved. The system is now loading as expected. We are continuing to monitor the environment and investigate the underlying cause, and we will provide additional updates as more information becomes available.
- resolved Jul 13, 2026, 04:24 PM UTC
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.
- postmortem Jul 21, 2026, 11:23 AM UTC
We experienced a disruption affecting the Platform and Build Service, which resulted in degraded platform performance and intermittent deployment failures. Our investigation identified a configuration issue that caused the service to operate with less capacity than intended. Our engineers corrected the configuration and restored the expected capacity, after which performance returned to normal. We continued monitoring the environment to confirm that the service remained stable. We are taking additional steps to improve service resilience and reduce the likelihood of similar disruptions in the future.