Resolved -
The service disruption that occurred today was due to an outage with one of our infrastructure providers, Fly.io. This impacted our ability to deploy services and resulted in temporary unavailability of our environments. The issue has been resolved, and all services are now operational and performing as expected. We are reviewing our deployment processes to further reduce the risk and impact of similar provider-related incidents in the future. Additional details are available on the Fly.io status page at https://status.flyio.net/
Feb 5, 14:07 MST
Update -
We are continuing to monitor the status with our provider Fly.io to ensure stability.
Feb 5, 13:28 MST
Update -
While the environments are back up and operational, our service provider, Fly.io, is still working to ensure stability on their end. We are continuing to monitor until the issue is fully resolved.
Feb 5, 12:57 MST
Monitoring -
The environment is back up and operational. Our service provider, Fly.io, has pushed out a fix, and we are continuing to monitor the situation closely to ensure stability. We will share additional updates if anything changes. Thank you for your patience while this was resolved.
Feb 5, 12:22 MST
Update -
We are continuing to work on a fix for this issue. While progress has been made, we are still experiencing problems in one of the regions. Our engineers are currently investigating and will continue to provide updates as more information becomes available. We apologize for the inconvenience this may be causing and appreciate your patience.
Feb 5, 12:07 MST
Identified -
Our engineers have identified an issue with our service provider, Fly.io, and they are actively working towards a resolution. We will provide additional updates as we have more information.
Feb 5, 11:02 MST
Update -
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.
Feb 5, 10:34 MST
Investigating -
We are currently investigating this issue.
Feb 5, 10:30 MST