System status

Our service health
in real time

Monitor Centeem's operational status. Page updated automatically. In case of an incident, we publish the details + the resolution here.

All services are operational.

Last check: a few seconds ago

Monitored services

Backend API

All API requests from the mobile app and the admin panel

Operational
99.94% uptime / 90d

Mobile App (iOS + Android)

Sign-in, payments, top-ups, withdrawals

Operational
99.98% uptime / 90d

Push Notifications

Real-time notifications (payment received, withdrawal approved, security alert)

Operational
99.81% uptime / 90d

Admin Panel

Admin interface for validating top-ups/withdrawals/CCP

Operational
99.92% uptime / 90d

KYC Service (HF Space)

Gemini Vision OCR for ID card/passport/RC/NIF + CCP receipt analysis

Operational
99.5% uptime / 90d

Supabase Storage

Storage of KYC documents, cheques, receipts, supporting documents

Operational
99.99% uptime / 90d

Resend Email

Sending of transactional emails (confirmations, security alerts)

Operational
99.97% uptime / 90d

Incident history

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

500 error on BaridiMob withdrawal (Prisma timeout)

24 May 2026

Resolved
Backend API

BaridiMob withdrawals were failing with 'Server error' for some users. Cause: the Prisma transaction exceeded its 5s timeout due to an out-of-transaction operation (platformFeeOps using the global prisma instead of tx). Fix: switch from prisma → tx + bump the timeout to 15s.

▶Detailed timeline
03:05First user report via support — 5k DZD withdrawal stuck
03:12Investigation: Sentry surfaces 1 PrismaClientKnownRequestError P2028 issue
03:25Root cause identified — buggy pattern present in 3 controllers
03:35Fix deployed to production on Railway
03:45Incident resolved — all withdrawals go through ✓

CCP cheque photo not persisted for auto-validated requests

23 May 2026

Resolved
Backend APISupabase Storage

When KYC OCR automatically validated the CCP number (KYC name match), the cheque photo was not saved → admin saw 'No CCP cheque configured'. Fix: add multer single('cheque') on PATCH /profile/ccp + Supabase upload + reference in CcpSupportRequest.chequePath.

▶Detailed timeline
MorningAdmin reports: 5 CCP requests with no photo in the panel
AfternoonCause identified: 100% of auto-validated requests had never persisted the photo for 6 months
EveningBackend + mobile multipart fix deployed

Excessive lazy loading on 3 mobile screens

22 May 2026

Resolved
Mobile App (iOS + Android)

The Withdraw, Top-up and Send screens showed a full-screen spinner every time you returned to the screen even if the data had not changed. Migration to React Query (MMKV cache + staleTime 30s-10min) → screens open instantly from the cache.

▶Detailed timeline
ReportSeveral testers report 'spinner too frequent'
InvestigationuseFocusEffect refetching systematically with no dedup
FixMigration of 3 screens to useWallet/useRechargeInfo/useBeneficiaries hooks

Report a problem

Running into a bug not listed here? Let us know.

Open a ticket

Get alerts

Automatic email in case of a major incident or planned maintenance.

Subscribe by email