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 Užimtumo tarnyba website refuses to open, start with the basics. Clear your browser cache and cookies, then try again. If that doesn't help, switch to a different browser entirely — Chromium-based browsers tend to handle government portals more reliably than Firefox or Safari in some cases. Also check whether your DNS settings are causing the delay: switching to 8.8.8.8 or 1.1.1.1 can resolve slow or failed lookups instantly.
Authentication issues on the self-service portal are common, especially after system updates. First, make sure you're using the correct login method — the portal supports login via national e-ID, smart card, or mobile signature. If the mobile signature flow gets stuck, check that your phone number is correctly registered with your mobile operator for that service. Try initiating the login sequence again from scratch rather than refreshing the confirmation page, since a stale session token often causes the loop.
File upload failures usually come down to format or size. The portal typically accepts PDF and JPEG files under a certain size limit — if your file exceeds it, compress it before uploading. Also avoid special characters in filenames; rename the file to something simple before trying again.
Accessing the portal on a smartphone can be frustrating when the layout breaks or buttons become unresponsive. If you're using a mobile browser, switch to desktop view temporarily to access forms that don't render properly on small screens. Mobile signal quality also matters — on a weak 4G connection, session timeouts happen faster, so completing longer forms over Wi-Fi is more reliable.
Temporary 500 or 503 errors tend to appear on Monday mornings or after public holidays when traffic spikes. Waiting 10–15 minutes and retrying usually resolves this. If the error persists beyond an hour, try a different device to rule out a local caching issue before concluding the service itself is down.