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 e.teismas.lt returns a blank page or times out, start with the basics: clear your browser cache, try a different browser (the portal works best in Chrome or Firefox on desktop), and check whether your internet connection is stable. The site occasionally goes under maintenance during off-peak hours, usually late at night. If the outage lasts more than 20–30 minutes during business hours, the issue is likely on the server side — wait and retry later.
Authentication on the portal relies on Smart-ID, mobile signature, or bank login through the Lithuanian e-identity infrastructure. If the login page freezes after selecting your method, the problem is often a session cookie conflict. Clear cookies for the domain and try again. If you're using bank authentication and your bank's own portal is also sluggish, the bottleneck is on the bank's side, not the court portal.
This is where system errors and format errors are easy to confuse. If you get a specific message about file type or size, that's a format issue — the portal accepts PDF/A and has a per-file size limit, typically around 10 MB. Convert your document and retry. If the upload bar freezes mid-way or you get a generic failure code, that's a system-side problem unrelated to your file.
After sending a procedural document, the portal should generate a confirmation with a timestamp. If you don't receive it within a few minutes:
Digital signing through the portal can stall if your signing app (like Smart-ID or mobile signature) doesn't respond in time. The portal session may expire while you're waiting. Refresh the page, start the process again, and make sure your phone has a stable signal before initiating the signature request.
The case search function sometimes fails to return results even with correct data. This usually happens after a session timeout. Log out fully, log back in, and repeat the search. If the results table loads but won't paginate or scroll, disabling browser extensions often resolves the freeze.