Sardine AI Status Page

Jun 30, 2026 · resolved Jun 30

This incident has been resolved.

Jun 25, 2026 · resolved Jun 25

### Summary Due to a database performance issue, API calls to `/v1/customer` , `/v1/issuing/risks` and `/v1/feedbacks` in June 25th faced increased latency. ### What happened One of the database we use to load certain customer and transaction data experienced slow latency for queries used in our customer and feedback APIs, causing latency issues on those APIs from 15:20 UTC to 16:23 UTC at June 25th. We've identified the root cause and are working on fixes to mitigate the issue. ### Why it happened One of our clients has very high volume and a particular usage pattern that didn't match well with our current database design for this data, causing the entire cluster to degrade in performance. ### What We’re Doing About It We are actively working on a solution to this issue, which includes moving the affected customer/transaction data to more performant databases, eliminating the risk altogether. In parallel we are also looking into actions to gracefully handle the usage patterns that cause degradation in the entire cluster.

Jun 2, 2026 · resolved Jun 2

### Summary On June 2, 2026, some customers experienced elevated latency on `/v1/issuing/risks` and `/v1/customers` requests in `prod-eu`. We’re sorry for the disruption and for any delays this caused in customer risk decisions. ### What Happened A subset of issuing risk requests became slower than expected due to delayed customer data lookups. During the main impact window, affected requests could take up to approximately 5 seconds before continuing through a soft-fail path. ### Why It Happened The issue was caused by a customer lookup path not enforcing its intended short timeout. When some customer lookups stalled, they waited on the broader request deadline instead of failing fast at the operation-level timeout. ### What We’re Doing About It We deployed a hotfix to reduce the customer-load timeout and limit how long issuing requests can wait on stalled lookups. We are also adding follow-up improvements to reduce Datastore dependency in low-latency paths and investigate the underlying cause of the lookup stalls.

May 22, 2026 · resolved May 22

#### Summary Our cache service experienced intermittent latency issues on May 22, 2026. Service has been fully restored. #### What Happened Our cache infrastructure experienced three distinct periods of elevated latency: * 22:23-22:31 UTC * 22:46-22:52 UTC * 23:00-23:05 UTC The system partially recovered between incidents but experienced cascading failures before full restoration at 23:05 UTC #### Why It Happened The incident began with an unusual spike in cache sets and cache deletes that stressed the caching infrastructure. #### What We're Doing About It * Implementing infrastructure improvements to prevent similar incidents resulting from noisy neighbor pattern * Enhancing cache monitoring, alerting and run books * Working with SME’s from our cloud provider to identify and address any contributing factors We apologize for the disruption and appreciate your patience.

May 20, 2026 · resolved May 20

This has been resolved, documentation is available.

Is Sardine AI down right now?

No — Sardine AI is up. All systems operational as of Jul 13, 11:49 PM UTC.

What is Sardine AI's current status?

Sardine AI: All Systems Operational. Alert24 checks Sardine AI's status page continuously and can notify you the moment it changes.

How do I get alerted when Sardine AI goes down?

Alert24 monitors Sardine AI and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.