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 doesn't open, start with the basics: check whether other websites work, restart your router, and clear the browser cache. Chromium-based browsers sometimes hold onto outdated cached data that breaks the login page entirely. If you're on a school or university network, the institution's firewall may be blocking the connection — try switching to mobile data to confirm.
Wrong credentials are the obvious cause, but not the only one. The system ties accounts to institutions, so logging in with a student ID that belongs to a different school year or a deactivated account will fail silently or return a vague error. Contact your school's administrator to verify that your account is still active and linked correctly.
This usually points to a session timeout or a partial page load. Refreshing doesn't always help — log out completely, close the tab, then log back in. If specific sections like the grade overview or timetable stay blank, the issue is often a temporary backend hiccup on the service side. Waiting 10–15 minutes and retrying tends to resolve it.
Push notifications depend on background app refresh being enabled and battery optimization being turned off for the app. On Android, manufacturers like Xiaomi and Samsung aggressively kill background processes. Go into your battery settings and whitelist Somtoday so it can maintain a persistent connection.
Large PDF attachments sometimes fail to load over slow mobile connections. Switch to Wi-Fi, or try opening the file through a desktop browser instead of the mobile app. If the file still doesn't load, the document may not have been uploaded correctly by the teacher — check with them directly.
If the search bar returns empty results for things you know exist, it's typically a stale local index. Logging out and back in forces a data sync. If the problem persists across multiple sessions, the issue is likely on the server side and will resolve on its own within a few hours.