Bank of Muscat runs core banking, digital channels, cards, and a national payment switch that have to stay available around the clock. By replacing a stack of siloed monitoring tools with Applicare’s single causal entity graph, the bank’s operations team now pinpoints root cause in seconds — and has held core-banking availability at 99.95%.
The real change is that we stopped arguing about whose component was at fault. Applicare shows the whole chain — app, transaction, and the query underneath — and tells us exactly where it broke. On the last salary-day peak we caught a database lock before it ever reached customers.
— Head of IT Operations, Bank of Muscat
Bank of Muscat is the flagship bank of Oman, serving millions of retail, corporate, and government customers across a nationwide branch, ATM, and digital footprint. Its core banking, card, and payment-switch workloads have to be available every hour of every day — and the operations team needed observability that could keep pace with peak-load spikes and tell them why something was failing, not just that it was.
Core banking, digital channels, the card system, and the payment switch were each watched by a separate tool, and the databases beneath them by another. When a customer-facing slowdown hit — usually during salary-day or end-of-day batch peaks — alerts fired from every console at once. Engineers spent the critical first hour stitching together dashboards and pointing fingers across teams before anyone could even confirm which layer was actually at fault. Database contention was a frequent culprit, but it surfaced only as a vague “the app is slow,” never as a specific query.