ClassLink logo

Is ClassLink Down?

Identity & AuthLive status, outages, and incident history

No. ClassLink is up right now.

Every monitored ClassLink system is operational as of November 10, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment ClassLink breaks

ClassLink is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official ClassLink status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

ClassLink Status Summary

As of 12:51 UTC on 10 November 2026, ClassLink is operational. PulsAPI checked ClassLink's official status page and found 11 of 11 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.99% uptime for ClassLink, counting degraded performance as up. The latest incident, "Roster Server Access Issue", was on Oct 30, 2026 and lasted 1h 4m.

Cite as: PulsAPI, “ClassLink status”, checked 10 November 2026, 12:51 UTC. https://www.pulsapi.com/services/classlink

ClassLink Component Status

The main ClassLink systems on this page. All 11 are operational right now.

11operational
Active Directory Integration
Operational
Analytics
Operational
Azure Integration
Operational

8 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Google Integration, Mobile apps, My Apps, My Classes, My Files, OneData, Partner Portal, Roster Server.

See all of them free

Component statuses may change independently during partial outages.

Recent ClassLink Outages & Incidents

Incident history from the official ClassLink status page, including resolution updates.

Roster Server Access IssueResolved Oct 30, 2026 · 1h 4mResolved

The issue affecting access to some Roster Server instances has been resolved and service has been restored. Thank you for your patience. --- [2026-10-30T13:32:23Z] (identified) We have identified the cause of the issue affecting access to some Roster Server instances and are working on a fix. We will post another update once service is restored. --- [2026-10-30T12:49:25Z] (investigating) We are investigating an issue affecting access to some Roster Server instances. Our team is actively working on this and we will post an update as soon as we have more information.

Intermittent 401 Errors When Signing In on Devices Receiving Google Update Resolved Oct 8, 2026 · 23h 13mResolved

The issue causing intermittent 401 errors when signing in on devices that received Google update 150, 154, 155 or 156 appears to be resolved. Sign-ins on affected devices are now completing as expected. If you or your users continue to experience 401 errors, please contact ClassLink Support so we can look into it right away. Thank you for your patience while we worked through this. --- [2026-10-09T17:25:57Z] (identified) 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 150-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.

ClassLink Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a ClassLink incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 12100.00% average · 3 days with incidentsNov 10

Going further back: ClassLink uptime by month and every recorded ClassLink outage.

Live ClassLink Outage Reports

Problems reported by engineers using ClassLink. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No ClassLink problems reported yet.

Something wrong with ClassLink on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About ClassLink

Is ClassLink down? ClassLink reports live availability for 12 components at status.classlink.com, among them Active Directory Integration, LaunchPad and Google Integration. Track ClassLink outages, degradations and past incidents here, with uptime history and alerts across your identity and access stack.

Over the past 30 days, PulsAPI has measured ClassLink uptime at 99.99%. Response times, incident history, and SLA tracking for ClassLink are available on the PulsAPI dashboard.

ClassLink Status FAQ

Is ClassLink down right now?

The verdict at the top of this page comes from the latest poll of the official ClassLink status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if ClassLink is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until ClassLink recovers.

How do I check ClassLink uptime history?

PulsAPI tracks ClassLink uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever ClassLink changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect ClassLink outages?

PulsAPI reads the official ClassLink status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual ClassLink components?

Yes. PulsAPI monitors 11 individual ClassLink components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when ClassLink goes down?

Yes. Create a free account and subscribe to ClassLink: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with ClassLink to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot ClassLink problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor ClassLink?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so ClassLink plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track ClassLink with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services