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 TARA authentication page doesn't open at all, start with the basics: clear your browser cache and cookies, then try a hard reload. Chromium-based browsers sometimes cache a broken redirect from the identity provider. If that doesn't help, switch to a different browser entirely — Firefox tends to behave more predictably with Estonian eID flows. Also check that your system clock is accurate, since token validation is time-sensitive and even a few minutes of drift can silently break the handshake.
This is one of the most common friction points. The authentication challenge gets sent, but the push notification never appears on your phone.
The browser plugin or web extension for ID-card authentication relies on the ID-card software running in the background. If the card isn't detected, open the DigiDoc4 client first to confirm the card reader is seen at the system level. On Windows, a pending driver update can block communication between the browser and the card reader daemon. Reinstalling the ID-software package usually resolves it.
TARA sessions are short by design. If you spend time filling out a form on the target service before initiating login, the authentication context may already be stale by the time you submit. Always start the login process as the last step before you actually need access, not while navigating around the site.
Sometimes authentication completes on the TARA side but the relying party application drops you back to the login screen. This usually means the service's own session cookie got corrupted. Clear cookies specifically for the target domain — not just for the authentication endpoint — and retry from a fresh tab.
If your browser flags an untrusted certificate on the authentication domain, do not proceed and do not add a security exception. Instead, check whether your antivirus is doing HTTPS inspection and intercepting the connection. Disabling SSL scanning in the antivirus settings typically restores the correct certificate chain immediately.