Is Sumeria Down? Live status & outage reports

Service info and troubleshooting

App Won't Load or Crashes on Launch

If the Sumeria app freezes on the splash screen or crashes immediately, start by force-closing it and clearing the cache. On Android: Settings → Apps → Sumeria → Storage → Clear Cache. On iOS, offload and reinstall the app. Make sure you're running a supported OS version — the app typically requires iOS 15+ or Android 9+. If the issue persists after reinstall, the problem may be a corrupted local database; logging out before reinstalling usually helps.

Login Errors in Personal Account

Failed login attempts are most often caused by an expired session token or a mismatched device fingerprint. Try the following:

• Clear browser cookies and site data if you're using the web version
• Disable browser extensions that modify headers or block scripts
• Check that your system clock is accurate — token validation fails if the device time is off by more than a few minutes
• Request a fresh SMS code rather than reusing an old one

If two-factor authentication messages aren't arriving, check that your number isn't blocking short codes from financial services.

Payment Fails at the Last Step

A payment getting stuck or rejected at confirmation usually points to one of three things: insufficient funds including the service fee, a card limit set by your issuing bank, or a temporary anti-fraud hold. Log into the app, go to transaction history, and check the error code shown next to the failed operation. Error codes in the 4xx range typically mean a bank-side decline — contact your card issuer directly. If there's no error code and the amount just doesn't move, wait 10–15 minutes and check again; processing queues sometimes back up.

Transfers Not Going Through

If a transfer hangs in 'Pending' for more than 30 minutes, do not retry immediately — duplicate submissions can result in double charges. Instead, refresh the transaction list and verify the status. SEPA transfers may take until the next business day if submitted after the bank's cut-off time. For instant transfers that stall, confirm the recipient's IBAN is entered without spaces and matches the account currency.

Interface Frozen or Unresponsive

A frozen dashboard or unresponsive buttons are often caused by a stale WebSocket connection. Reload the page or restart the app — this re-establishes the real-time connection. If the problem appears consistently on a specific screen, the issue might be tied to a large transaction history payload. Try filtering the date range to reduce the data load.

Slow Performance and High Response Times

Sluggish screen transitions or long waits for balance data to appear usually come down to a weak mobile signal or congested Wi-Fi. Switch between Wi-Fi and mobile data to isolate the source. If both are slow, check your ping to a general server — anything above 150 ms will noticeably degrade real-time banking features. Restarting your router or toggling Airplane Mode for 10 seconds often resolves temporary network hiccups.