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.
Clear your browser cache and try a hard reload. If the site still doesn't respond, switch to a different browser — Chrome, Firefox, or Safari — since outdated cached data or broken extensions can silently block the connection. Check whether your ISP is throttling HTTPS traffic on port 443, which occasionally causes banking sites to time out without an obvious error message.
This usually comes down to three things:
If none of that helps, request a credential reset through the official support line, since the account may be temporarily locked after repeated failed attempts.
Force-close the BPER Banca app and reopen it. If it keeps freezing, check for a pending update in the App Store or Google Play — banking apps are tightly coupled to backend API versions, and running an outdated build often causes the interface to hang on load. As a last resort, uninstall and reinstall; your account data lives on the server, not on the device.
A payment can fail at the final step even when card details look correct. The most common reasons are a mismatched billing address, an expired SMS authorization code, or a daily transaction limit already reached. Check the limit inside your account settings, and make sure the one-time code arrives and is entered before it expires — most codes are valid for only 90 seconds.
Delayed or missing OTP messages are almost always a network issue on the carrier side. Move to an area with better signal, then request a new code. If the problem persists, contact your mobile operator to confirm that premium short codes are not blocked on your number, since some prepaid plans filter them by default.
If a transfer shows as pending for longer than expected, do not resubmit it immediately — duplicate submissions can cause both to process once the delay clears. Log out, wait a few minutes, log back in, and check the transaction history. If the status hasn't changed after a few hours, call support with the transaction reference number ready.
Heavy network latency usually affects all pages equally. Run a quick speed test to rule out a local connection problem. If your connection is fine but the app still feels sluggish, the issue is likely server-side load — wait 10 to 15 minutes and try again during off-peak hours.