Online banking session keeps timing out? What to test

You are reading a bank statement or filling out a payment, then the page asks you to sign in again. A timeout can happen because your connection briefly dropped, but banks also end sessions automatically for security. The timing alone does not tell you which one happened.

Test your connection separately from the banking site, then check whether the browser, device, or bank session rules are a better fit. The Connection Stability test measures response time, jitter, lost requests, and dropouts over a few minutes. It does not test the bank's own servers or change your banking session.

Test your connection stability

Open the Connection Stability test in a separate tab. Do not enter banking details into the test.
Run it on the same device and connection you use for banking. If you normally bank over Wi-Fi, keep using Wi-Fi for this check.
Let the test run for a few minutes. Avoid starting a large download or moving far from the router while it measures the connection.
Look at the response time, jitter, lost requests, and any dropouts in the results. Note whether the connection stays consistent or has brief interruptions.
If the timeout happens again later, note the time and what you were doing. Compare that with another stability test, but do not repeatedly submit a payment to reproduce the problem.

If you use a banking app rather than a browser, the same network check can still help, but it cannot show what the app or bank server is doing. Do not keep a payment screen open just to run a test. Finish or cancel the banking task first, then check the connection separately.

What the result means

The test shows dropouts or lost requests

Some requests are not getting a reply, or the connection is briefly interrupted. That can make a page stall or fail to save information, especially if it happens while the bank is sending or receiving data. It does not prove that a network drop caused the timeout, and it does not show whether the bank received a payment request. Check your transaction history before attempting a payment again.

Response time or jitter changes sharply

Response time is how long a test request takes to get a reply. Jitter is how much that delay varies. Large changes can make a connection feel uneven, but a high reading by itself does not mean the bank session must expire. A session may end on a fixed timer even when the connection is steady.

The connection stays steady

A steady result makes a brief local connection problem less likely during the test. It does not rule out a short interruption at another time, a problem reaching the bank specifically, or a browser issue. If banking pages time out while other sites keep working, contact the bank using the phone number on your card or its official app.

The test is steady, but the bank signs you out after inactivity

This often matches an automatic security timeout. Banks commonly end sessions after a period without activity, and the exact limit depends on the bank. Do not use scripts or browser extensions to keep the session alive. Save work as you go, and follow the bank's instructions if it asks you to sign in again.

How to fix it

Check whether the bank completed the action. If a transfer or payment page timed out, look at your transaction history before trying again. If the status is unclear, contact the bank through an official channel instead of submitting it twice.
Sign in again and retry once. A single reload or fresh sign-in can clear a page that stopped responding. Do not refresh while a payment is being submitted, and do not share passwords or verification codes with anyone who contacts you unexpectedly.
Check the device clock. An incorrect date or time can interfere with secure connections. On Windows 11, open Settings › Time & language › Date & time and turn on automatic time. On a Mac, open System Settings › General › Date & Time and enable automatic time and date. On an iPhone, check Settings › General › Date & Time. On Android, open Settings › System › Date & time, though the wording can vary by phone.
Try a different connection. If you use Wi-Fi, test near the router or switch briefly to mobile data. On Windows 11, check Settings › Network & internet. On a Mac, open System Settings › Network. On an iPhone, open Settings › Wi-Fi; on Android, look under Settings › Network & internet or Connections. Use a trusted private connection for banking, not public Wi-Fi.
Check browser settings and extensions. Make sure cookies are not being blocked for the bank's site, since some banking pages need them to maintain a session. Temporarily turn off privacy or script-blocking extensions for that site, then reload. Avoid clearing all browser data unless you are prepared to sign in to other sites again.
Update the browser or banking app. Install updates from the browser's built-in update screen or the official app store, then restart it. If the problem continues only in one browser, try another updated browser to see whether the behavior changes.
Contact the bank if it persists. Tell support when the timeout occurs, which device and browser or app you use, and whether other sites also lose connection. Never send a password, one-time code, or full card number in an email or chat.

When the connection is probably not the cause

If the bank signs you out after roughly the same idle period each time, but other pages continue loading normally, the bank's session policy is a more likely explanation than Wi-Fi. A bank can also end a session after a security check, a password change, or activity it cannot verify. Only the bank can confirm the reason for a particular sign-out.

Connection Stability is a browser test, not a diagnostic tool for your bank account. It can help you identify a network that drops requests, but it cannot confirm whether a page saved a form or whether a payment went through.

For a timeout during a payment, verify the transaction with the bank before submitting it again.