LoyaltyLion Outage History

LoyaltyLion is up right now

LoyaltyLion had 3 outages in the last 2 years totaling 5h 25m of downtime — averaging 0.1 incidents per month.

There were 3 LoyaltyLion outages since August 20, 2025 totaling 5h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.loyaltylion.com

Major October 9, 2025

Delays in data processing

Detected by Pingoru
Oct 09, 2025, 04:25 PM UTC
Resolved
Oct 09, 2025, 07:40 PM UTC
Duration
3h 14m
Affected: APIPlatform and SDK
Timeline · 3 updates
  1. investigating Oct 09, 2025, 04:25 PM UTC

    We're currently experiencing delays in data processing and high error rate in incoming webhooks. Our team is investigating.

  2. identified Oct 09, 2025, 04:48 PM UTC

    We've identified the issue. Webhooks are being accepted again. We're working through the backlog of webhooks now.

  3. resolved Oct 09, 2025, 07:40 PM UTC

    The backlog of webhooks has been cleared. This incident has been resolved.

Read the full incident report →

Major September 24, 2025

SDK unavailable

Detected by Pingoru
Sep 24, 2025, 09:00 AM UTC
Resolved
Sep 24, 2025, 09:44 AM UTC
Duration
43m
Affected: Platform and SDK
Timeline · 3 updates
  1. investigating Sep 24, 2025, 09:43 AM UTC

    The LoyaltyLion SDK was unavailable for 10 minutes

  2. investigating Sep 24, 2025, 09:43 AM UTC

    We are continuing to investigate this issue.

  3. resolved Sep 24, 2025, 09:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 20, 2025

High response time on API endpoints

Detected by Pingoru
Aug 20, 2025, 02:08 PM UTC
Resolved
Aug 20, 2025, 03:35 PM UTC
Duration
1h 26m
Affected: API
Timeline · 3 updates
  1. identified Aug 20, 2025, 02:08 PM UTC

    We're currently experiencing elevated response times on our API endpoints. We have identified the issue and should have a fix deployed in the next hour.

  2. monitoring Aug 20, 2025, 03:02 PM UTC

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

  3. resolved Aug 20, 2025, 03:35 PM UTC

    This incident has been resolved.

Read the full incident report →