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 website refuses to open, start with the basics: clear your browser cache and cookies, then try a hard reload (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). If that doesn't help, switch to a different browser or try incognito mode. DNS issues can also block access — switching to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) often resolves this quickly.
Failed login attempts are usually caused by one of these:
If none of these work, use the password reset flow directly from the login page.
Force-close the Citadele app completely and relaunch it. If it keeps freezing, check whether the app is up to date in the App Store or Google Play — outdated versions frequently cause interface lockups. As a last resort, clear the app cache (Android: Settings → Apps → Citadele → Clear Cache).
A failed payment doesn't always mean the money is gone. First, check your transaction history to confirm whether the operation was recorded. Common reasons for failures include incorrect IBAN format, daily transfer limits being reached, or the recipient's bank temporarily rejecting requests. If the amount was debited but the transfer shows no status, contact support with the transaction timestamp.
Without notifications, you miss one-time codes and payment confirmations. On iPhone, go to Settings → Notifications → Citadele and make sure alerts are enabled. On Android, check that battery optimization isn't killing the app in the background — add it to the exceptions list.
High latency inside the app or web banking usually points to a local network issue rather than a server problem. Run a quick speed test — if your connection is below 5 Mbps, that's likely the cause. Switching from Wi-Fi to mobile data (or the reverse) often restores normal response times immediately.