MerchantSpring incident

Major Database Outage

Notice Resolved View vendor source →

MerchantSpring experienced a notice incident on April 11, 2025 affecting Analytics Dashboard and Data Pipeline, lasting 3h 9m. The incident has been resolved; the full update timeline is below.

Started
Apr 11, 2025, 03:34 AM UTC
Resolved
Apr 11, 2025, 06:43 AM UTC
Duration
3h 9m
Detected by Pingoru
Apr 11, 2025, 03:34 AM UTC

Affected components

Analytics DashboardData Pipeline

Update timeline

  1. investigating Apr 11, 2025, 03:34 AM UTC

    One of our core database providers is experiencing an outage, which is impacting our application’s ability to deliver data. This is an external issue, and we are actively working with the provider to expedite their resolution. To minimize the impact on your experience, we are also implementing a temporary redundancy solution within our infrastructure. Our goal is to restore partial functionality as quickly as possible while the database provider resolves their outage. We sincerely apologize for this disruption and assure you we are doing everything possible to resolve it swiftly. We will share updates as the situation progresses. Thank you for your understanding and support during this time.

  2. investigating Apr 11, 2025, 04:41 AM UTC

    One of our core database providers is experiencing an outage, which is impacting our application’s ability to deliver data. This is an external issue, and we are actively working with the provider to expedite their resolution. To minimize the impact on your experience, we are also implementing a temporary redundancy solution within our infrastructure. Our goal is to restore partial functionality as quickly as possible while the database provider resolves their outage. We sincerely apologize for this disruption and assure you we are doing everything possible to resolve it swiftly. We will share updates as the situation progresses. Thank you for your understanding and support during this time.

  3. monitoring Apr 11, 2025, 05:13 AM UTC

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

  4. monitoring Apr 11, 2025, 05:21 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Apr 11, 2025, 05:22 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 11, 2025, 06:43 AM UTC

    This incident has been resolved.