Resolved -
This incident has been resolved. Our team completed additional corrective maintenance to rebalance workloads across the affected server, and continuous monitoring since has confirmed the environment remains stable. We apologize for any disruption this may have caused and thank you for your patience.
Aug 14, 13:27 PDT
Monitoring -
The unplanned maintenance has been completed, and OneRoster API services have been successfully restored. We are currently monitoring the environment to verify continued stability. Our team will continue to closely observe the environment and will provide an update within 60 minutes, or sooner should any changes occur.
Aug 14, 12:53 PDT
Update -
We are continuing to investigate the issue affecting one of our API servers. At this time, there are no significant updates to share. Traffic remains redirected away from the affected server, and our team continues to monitor the environment and work toward resolution. We will provide another update within 60 minutes or sooner if new information becomes available.
As a workaround, customers using the Aeries API (not the OneRoster API) should ensure they are using the standard district.aeries.net base URL rather than the api base URL. The standard URL is load balanced and will help distribute traffic more effectively while we continue to address the issue.
Aug 14, 12:34 PDT
Update -
We have identified an issue affecting one of our API servers. To minimize customer impact, traffic has been redirected away from the affected server while our team continues to investigate and implement corrective actions.
We are closely monitoring the environment and working to restore full service. Our next update will be provided within 60 minutes
Aug 14, 11:29 PDT
Investigating -
We are investigating reports of the API being unavailable. Our team is actively working to identify the cause and will provide an update within 30 minutes.
Aug 14, 11:18 PDT