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 Riigitöötaja Iseteenindus login page won't open, start with the basics: clear your browser cache and cookies, then try a hard reload. Chromium-based browsers sometimes cache a broken session state that blocks the authentication flow entirely. If that doesn't help, switch to a different browser or try an incognito window. Also check that your system clock is accurate — ID-card and Mobile-ID authentication rely on certificate validation, which fails if your device time is off by more than a few minutes.
Smart card login depends on both browser support and local software. Make sure the ID-card utility and browser extension are up to date. Try removing and reinserting the card, and confirm the card reader is recognized by your operating system. Firefox requires the PKCS11 security module to be manually registered — if you recently updated the browser, that link may have broken and needs to be re-added through the browser's security device settings.
When a Mobile-ID or Smart-ID login request just hangs without delivering a prompt to your phone, the issue is usually a momentary sync problem between the portal and the authentication provider. Wait 30 seconds and try again. If it keeps failing, check whether your mobile data or Wi-Fi connection is stable — Smart-ID in particular needs a reliable connection on the phone side to receive and process the challenge.
The portal enforces a short inactivity timeout. If you're filling in a form or preparing a document and the session drops before you submit, try to keep the tab active. Avoid opening the same account in multiple tabs simultaneously, as this can trigger an early session invalidation.
Frozen forms or unresponsive submit buttons are often caused by a JavaScript conflict. Disable browser extensions one by one to find the culprit — ad blockers and script managers are frequent offenders. If the interface is still stuck, try zooming the browser to 100%, as some layout-triggered rendering bugs only appear at non-default zoom levels.
When the portal responds slowly, first rule out your own connection — run a quick speed test and check whether other government portals load normally. If only RTIP feels sluggish, the server may be under load, which tends to happen on Monday mornings or after public holidays when many employees access the system at once. Waiting a few minutes and refreshing usually resolves it.