We started checking Clever on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Clever reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Clever's own status page declared. Below it, any public chatter we saw about Clever and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Clever's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Clever in the last 24 hours, which is not evidence that nothing is wrong.
Clever's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Clever's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Clever next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
429
US-West
100.00%
325
Europe
100.00%
299
Asia-Pacific
99.45%
181
Their declared record
Clever's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Badge Expiration Notice Displaying in PortalAll systems operational
Oct 30, 2026, 2:46 PM UTC to Oct 30, 2026, 6:40 PM UTC (3h 54m)resolved
their latest update (Oct 30, 2026, 6:40 PM UTC): The issue causing an incorrect pop-up stating student Badges would expire in 24 hours has been resolved. Badges remain active and will not expire as long as they are being used. If you continue to see this notification or need assistance, please visit support.clever.com.
Badge downloads are timing out.All systems operational
Oct 22, 2026, 2:40 PM UTC to Oct 22, 2026, 4:14 PM UTC (1h 34m)resolved
their latest update (Oct 22, 2026, 4:14 PM UTC): This incident has been resolved.
Clever is updating our home page. Product login and usage is not impacted.All systems operational
Oct 21, 2026, 5:35 PM UTC to Oct 22, 2026, 2:14 AM UTC (8h 39m)resolved
their latest update (Oct 22, 2026, 2:14 AM UTC): This incident is resolved. We have completed the update to our main website.
Clever Login IssuesMinor incident
Oct 8, 2026, 1:47 AM UTC to Oct 8, 2026, 1:47 AM UTC (0 min)resolved
their latest update (Oct 8, 2026, 1:47 AM UTC): Between 5:08 and 5:59 pm PST, some users may have been unable to log in to the Clever Portal or launch apps. Service has recovered, and we’re monitoring it. If you see any additional issues, please reach out to our support team at support.clever.com.
Incorrect Task NotificationAll systems operational
Sep 18, 2026, 4:43 PM UTC to Sep 18, 2026, 4:43 PM UTC (0 min)resolved
their latest update (Sep 18, 2026, 4:43 PM UTC): Between 7:12 and 8:53 AM PT today, a task titled "1 Application waiting on you" was shown in error to district administrators who logged in to the Clever dashboard during that window. The task referenced another district's pending application invite and was intended for that dist…
Clever's Support Team Delayed in Assisting DistrictsMinor incident
Sep 16, 2026, 11:24 AM UTC to Sep 16, 2026, 11:43 PM UTC (12h 19m)resolved
their latest update (Sep 16, 2026, 11:43 PM UTC): Salesforce has resolved this incident. All previously affected channels are now functioning normally, and support case handling, notifications, and response times have returned to expected levels.
Aug 27, 2026, 2:18 PM UTC to Aug 27, 2026, 3:46 PM UTC (1h 28m)resolved
their latest update (Aug 27, 2026, 3:46 PM UTC): This incident has been resolved.
Sync Errors Impacting Some Aeries API SyncsAll systems operational
Aug 14, 2026, 5:09 PM UTC to Aug 18, 2026, 1:59 PM UTC (3d 20h)resolved
their latest update (Aug 18, 2026, 1:59 PM UTC): Aeries API syncs that were previously showing a sync error are now syncing to Clever. This issue has now been resolved and we appreciate your patience.
Sync Error with Districts Utilizing Aeries APIAll systems operational
Aug 13, 2026, 4:23 PM UTC to Aug 13, 2026, 9:38 PM UTC (5h 15m)resolved
their latest update (Aug 13, 2026, 9:38 PM UTC): The sync issue with some Aeries API syncs has been resolved. We thank you for your patience.
Teacher Pages unavailable for some studentsMinor incident
Aug 5, 2026, 6:50 PM UTC to Aug 5, 2026, 8:48 PM UTC (1h 58m)resolved
their latest update (Aug 5, 2026, 8:48 PM UTC): This incident has been resolved.
Showing the 10 most recent of 50 incidents Clever has declared in the history we hold.
These entries are Clever's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Clever's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.