Greenwood

We have implemented a partial workaround for the currently identified affected domains. Customers should begin seeing restored access to these domains. The underlying issue has not been fully resolved, and other Akamai-hosted domains may continue to return SERVFAIL responses. We are monitoring the effectiveness of this mitigation and continuing to work with Akamai toward a full resolution. Customers who continue to experience issues can use the previously provided workaround to bypass affected domains from Cisco DNS. Additional updates will be provided as new information becomes available.

Google has begun a phased rollout of an updated ChromeOS (reports are of versions 154 and 150) which started on October 6 and is expected to reach all devices by October 20. We have identified that this update can cause some ClassLink sign-in attempts to return a 401 error. Who is affected: Users on devices that have received Google update 156. Not every sign-in is affected. For districts where Google is the identity provider, this error can prevent users from signing in to the device. Workaround: If a user sees a 401 error, refresh the page or restart the device and try signing in again. This resolves the issue in most cases. Next steps: ClassLink engineering has identified the cause and is developing a fix, which we expect to have ready no later than Friday, October 9. We will update this page when the fix is deployed, or sooner if anything changes. We apologize for the disruption and appreciate your patience. If the workaround does not resolve the issue, please contact ClassLink Support.

We're performing maintenance in our staging environment, which may result in some ACME clients receiving timeouts or errors for brief periods. Our production environment will not be affected.

Twilio customers may be experiencing SMS delivery delays from Twilio to Verizon network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.