Centeem
System status

Our service health
closely monitored

Monitor Centeem's operational status. Our team updates this page as soon as an incident occurs. In case of an incident, we publish the details + the resolution here.

No ongoing incident reported.

Status updated manually by our team — last update: October 2, 2026

Monitored services

Mobile app

Access to the app and your account (iOS and Android)

Operational

Payments

Payments, transfers, top-ups and withdrawals

Operational

Login

Account login and confirmation of new devices

Operational

Website

centeem.com and payment link pages

Operational

Incident history

All recent incidents with their resolution. Full transparency, even on our bugs.

Login unavailable for about 8 hours

September 30, 2026

Resolved
Login

Following a security update, logging in to the app was impossible for about 8 hours. No funds were lost. Once the problem was fixed, every user had to log in again and confirm their device.

▶Detailed timeline
StartA security update prevents logins to the app
DiagnosisCause identified: a missing server-side setting
ResolutionFix applied — logins restored, all users asked to log in again

500 error on BaridiMob withdrawal (technical slowdown)

24 May 2026

Resolved
Payments

BaridiMob withdrawals were failing with a server error for some users, due to a temporary technical slowdown on an internal operation. No funds were lost: affected withdrawals were successfully reprocessed after the fix.

▶Detailed timeline
03:05First user report via support — 5k DZD withdrawal stuck
03:12Investigation: technical cause identified via our internal monitoring
03:25Cause identified — the same issue affected several related functions
03:35Fix deployed to production
03:45Incident resolved — all withdrawals go through ✓

CCP cheque photo not persisted for auto-validated requests

23 May 2026

Resolved
Mobile app

In a specific case of automatic CCP number validation, the associated cheque photo was not saved correctly. A fix was deployed to ensure the photo is always saved, with no impact on users' funds or accounts.

▶Detailed timeline
MorningOur team notices CCP requests saved without a photo
AfternoonCause identified: a specific auto-validation case wasn't persisting the photo
EveningFix deployed on both server and mobile app

Excessive lazy loading on 3 mobile screens

22 May 2026

Resolved
Mobile app

The Withdraw, Top-up and Send screens showed a loading spinner every time you returned to the screen even if the data had not changed. We optimized our caching system: these screens now open instantly.

▶Detailed timeline
ReportSeveral testers report loading too frequently
InvestigationCause identified: data was being reloaded every time the screen was reopened
FixOptimization deployed on the 3 screens affected