Is Sardine down?

Last checked 2m ago
Current status
Sardine is up

No incidents right now.

Official status page: https://status.sardine.ai · Polled every 5 minutes · 7 components tracked

Sardine is operational right now. Last checked 2m ago; the most recent incident resolved 7d ago.

Real-time Sardine status, recent outages, and incident history — pulled directly from Sardine's official status page at https://status.sardine.ai every 5 minutes. Pingoru tracks 7 Sardine services and has captured 16 incidents in the last 90 days (97.62% uptime). Get email, Slack, Discord, or webhook alerts the moment Sardine reports a new incident — free for 5 monitors, no credit card.

Users who monitor Sardine also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
Sardine uptime 97.62% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 25m
    Started Jul 24, 2026, 12:42 AM UTC · Resolved Jul 24, 2026, 02:07 AM UTC
    Dashboard
    Timeline · 5 updates
    • investigating · Jul 24, 2026, 12:42 AM UTC

      We are currently investigating this issue.

    • identified · Jul 24, 2026, 12:58 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Jul 24, 2026, 01:19 AM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Jul 24, 2026, 01:41 AM UTC

      New sessions are being shown OK, a few older ones might still be missing, they'll be shown shortly.

    • resolved · Jul 24, 2026, 02:07 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1h 45m
    Started Jul 16, 2026, 12:40 PM UTC · Resolved Jul 16, 2026, 02:25 PM UTC
    Dashboard
    Timeline · 7 updates
    • investigating · Jul 16, 2026, 12:40 PM UTC

      We are currently experiencing degraded performance in retrieving the latest customer sessions in the Customer Intelligence page. Root cause has been determined. We are working on resolution.

    • identified · Jul 16, 2026, 12:40 PM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Jul 16, 2026, 12:41 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Jul 16, 2026, 12:41 PM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Jul 16, 2026, 01:13 PM UTC

      A fix has been implemented and results are being displayed in the Customer Intelligence page. We are monitoring the process until full service is restored.

    • monitoring · Jul 16, 2026, 01:13 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Jul 16, 2026, 02:25 PM UTC

      The issue has been resolved.

    Latest: The issue has been resolved.

  3. Resolved
    Started Jul 15, 2026, 07:56 PM UTC · Resolved Jul 15, 2026, 07:56 PM UTC
    Customer APIs
    Timeline · 3 updates
    • investigating · Jul 15, 2026, 02:34 PM UTC

      We are currently investigating this issue.

    • resolved · Jul 16, 2026, 02:36 AM UTC

      This incident has been resolved. A Postmortem will be published soon.

    • postmortem · Jul 16, 2026, 02:49 AM UTC

      **Summary** On 2026-07-15, API requests experienced elevated error rates and increased tail latency \(p99\). Median latency \(p50\) was not affected and there was little effect on 95th percentile latency \(p95\), so most requests performed normally. We began investigating at 14:34 UTC and applied a fix at approximately 19:56 UTC, after which performance returned to normal. **What happened?** Through the affected period, a portion of API requests returned errors, responded with reason code SITO \(Sardine internal timeout\) or timed out rather than completing, with intermittent spikes during which a larger share of requests were affected. **Why did it happen?** A scaling configuration prevented part of our platform from adding capacity as traffic increased. As traffic rose through the day, available capacity was exhausted, causing timeouts and errors for some requests. **What are we doing about this?** We corrected the configuration at **19:56 UTC**, which immediately restored normal performance. We are also making the affected part of the platform more resilient to sudden traffic increases and adding proactive monitoring so we can detect and respond to this class of issue faster in future. We apologize for the disruption.

    Latest: **Summary** On 2026-07-15, API requests experienced elevated error rates and increased tail latency \(p99\). Median latency \(p50\) was not affected and there was little effect on …

  4. Resolved 5h 42m
    Started Jun 30, 2026, 01:58 PM UTC · Resolved Jun 30, 2026, 07:41 PM UTC
    Issuing APICustomer APIs
    Timeline · 2 updates
    • investigating · Jun 30, 2026, 01:58 PM UTC

      We are currently investigating this issue.

    • resolved · Jun 30, 2026, 07:41 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1h 3m
    Started Jun 25, 2026, 03:20 PM UTC · Resolved Jun 25, 2026, 04:23 PM UTC
    Customer APIs
    Timeline · 3 updates
    • investigating · Jun 25, 2026, 03:56 PM UTC

      We are currently investigating this issue.

    • resolved · Jun 25, 2026, 06:13 PM UTC

      The incident regarding the latency increased has been resolved. It started at 15:20 UTC and lasting until 16:23 UTC. We'll include a postmortem into this status page in the future.

    • postmortem · Jun 30, 2026, 06:51 PM UTC

      ### 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.

    Latest: ### 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 o…

See the full Sardine outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Sardine outage history →

Or sign up free to get alerts when Sardine breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 11 incidents View full outage history →