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 ASN Bank app closes right after launch, first check whether the latest version is installed from the official app store. A crash at startup often comes from an outdated build, damaged local cache, or a phone OS update that the app has not fully synced with yet. Restart the phone, free some storage, and try again on Wi-Fi and mobile data to rule out a network-specific issue. If the app still hangs on the splash screen, remove it and install it again.
When the browser version stays blank, keeps spinning, or throws a generic error, the cause is often local browser data. Clear cookies and cache for the bank site, then open it in a private window or another browser. Also confirm that JavaScript is enabled and the device date and time are correct, because incorrect system time can break secure sessions.
A login error is not always a wrong password. Keyboard layout, autofill mistakes, expired saved credentials, or copied spaces before or after the username can all trigger rejection. Enter details manually once. If access is blocked after several attempts, wait for the temporary lock to expire and then reset credentials through the official recovery flow.
A transfer may fail because of maintenance, a timeout, or stricter fraud checks after unusual activity. Try a smaller amount, switch from mobile app to web banking, and check whether the recipient account format is accepted. If the transfer is urgent and repeatedly fails, save screenshots of the error text and time.
This usually points to temporary backend overload or planned maintenance rather than a problem on your device. Refreshing too often rarely helps. Wait a few minutes, then try again from another network to confirm whether the issue is local. If both app and website fail at the same time, it is likely on the service side.
Sometimes recent transactions, balance changes, or new statements do not appear immediately. Pull to refresh, sign out and back in, and check whether the app is showing cached data. On slower connections, transaction lists may load partially, making it look as if payments disappeared when they are simply delayed in display.