All Systems Operational

About This Site

This ClassLink Status page gives you information on the accessibility and performance of ClassLink. If there is a system-wide disruption to any part of ClassLink, incident notes will be updated here.

Use the 'subscribe to updates' option above and select the desired components to be immediately notified whenever an incident is initially reported or updated on this page.

Contact helpdesk@classlink.com or call 888-963-7550 ext#1 with any questions.

Sign in to ClassLink Operational
Active Directory Integration ? Operational
Google Integration ? Operational
Azure Integration ? Operational
My Files ? Operational
Roster Server ? Operational
Analytics ? Operational
Mobile apps ? Operational
Partner Portal ? Operational
My Apps Operational
My Classes ? Operational
My Apps Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 20, 2025

No incidents reported today.

Jan 19, 2025

No incidents reported.

Jan 18, 2025

No incidents reported.

Jan 17, 2025

No incidents reported.

Jan 16, 2025

No incidents reported.

Jan 15, 2025

No incidents reported.

Jan 14, 2025

No incidents reported.

Jan 13, 2025

No incidents reported.

Jan 12, 2025

No incidents reported.

Jan 11, 2025

No incidents reported.

Jan 10, 2025

No incidents reported.

Jan 9, 2025

No incidents reported.

Jan 8, 2025

No incidents reported.

Jan 7, 2025

No incidents reported.

Jan 6, 2025
Resolved - The issue affecting group sync and subsequent logins has been resolved. Thank you for your continued patience.
Jan 6, 20:22 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 6, 19:47 EST
Update - We have identified a fix for the issue and its impact is extremely limited. Due to its nature, the fix will be implemented after hours to minimize disruption. We apologize for the inconvenience.
Jan 6, 10:49 EST
Identified - A subset of users are experiencing intermittent issues with group sync which can cause login issues into LaunchPad. Our teams have identified the issue and are actively working on a fix.
Jan 6, 10:13 EST