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 DigiD site does not load, the cause is often local: unstable mobile data, overloaded Wi-Fi, aggressive content blocking, or an outdated browser. First open another secure site to check whether your connection is working. Then reload the page, switch between Wi-Fi and mobile internet, and clear the browser cache. If the page still hangs or returns a timeout, the service may be temporarily overloaded. In that case, try again later rather than retrying continuously.
A failed sign-in is not always a wrong password. Saved autofill data may insert an old username, the keyboard language may switch unexpectedly, or extra spaces may be pasted from a password manager. Enter the credentials manually once, check caps lock, and verify that the correct DigiD username is being used. If too many attempts were made, wait for the lock period or use the official recovery flow.
SMS verification can fail because of weak signal, delayed carrier delivery, roaming issues, or an outdated phone number linked to the account. Check whether ordinary text messages arrive from other senders. If not, move to a location with better reception, restart the phone, and confirm that airplane mode is off. If other SMS messages work but the code still does not arrive, request a new one after a short wait instead of pressing resend repeatedly.
When logging in by scanning a QR code, problems usually come from poor camera focus, a dim screen on the computer, or the app missing camera permission. Increase screen brightness, hold the phone steady, clean the camera lens, and confirm that the app can use the camera in system settings. On older devices, reopening the scanner often helps.
Activation can fail if the device clock is wrong, the internet connection drops during setup, or the activation code has expired. Set date and time to automatic, reconnect to a stable network, and restart the activation from the beginning. If multiple failed attempts were made, wait a while before trying again.
Push notifications may be disabled for the app, blocked by battery saving mode, or delayed when the phone has no background data access. Check notification permissions, disable strict battery optimization for the app, and allow mobile data in the background. On some phones, vendor-specific power saving settings also need to be relaxed.
If a form or confirmation step ends with an error message, the session may have expired while the page was left open. Open a fresh session, sign in again, and repeat the action without using old browser tabs. Also avoid using the browser back button during authentication, because that can break the transaction state.
Sometimes the platform is unavailable because of maintenance or a backend incident. Typical signs are generic 500 errors, endless loading, or being thrown back to the start page after authentication. There is little to fix on the user side beyond checking your connection, trying another browser or device, and waiting until the system is stable again.