Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If the platform refuses to open, start with the basics: clear your browser cache, try a different browser, or switch from Wi-Fi to mobile data. Sometimes a stale DNS cache is the culprit — flushing it with ipconfig /flushdns on Windows often helps. If the issue persists across devices, the service itself may be temporarily down. Wait a few minutes and try again.
Wrong credentials are the obvious cause, but not always. If you're sure the password is correct and still can't get in, check whether Caps Lock is on or whether your keyboard language switched mid-input. Try resetting the password through the recovery option. If the system doesn't send a reset email, check your spam folder and make sure the email address on the account is still active.
This usually comes down to bandwidth. Run a speed test — streaming educational video typically needs at least 5 Mbps stable. If your connection is fine but the player still freezes, try lowering the video quality in the player settings. Reloading the page or switching to a different browser also fixes playback issues in most cases.
Smartschool relies on browser permissions to deliver in-app notifications. Go to your browser's site settings and confirm that notifications are allowed for the platform. On mobile, check that the app has permission to send alerts in your device system settings. If messages appear sent on your end but recipients don't see them, it's worth asking them to refresh — the interface sometimes needs a manual reload to display new content.
A frozen interface is almost always a JavaScript issue. Hard-refresh the page with Ctrl+Shift+R to bypass cached scripts. If specific buttons do nothing, open the browser console and look for errors — a failed script load is usually visible there. Switching to a private/incognito window rules out extension conflicts quickly.