LoyaltyLion status history
Current state: operational — “All Systems Operational” per https://status.loyaltylion.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do LoyaltyLion incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Elevated API/SDK response times and error rates — 5.1 h (2026-07-01 17:56 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-01 17:56 UTC | Elevated API/SDK response times and error rates | resolved | minor | 5 h 04 min |
| 2025-10-09 16:25 UTC | Delays in data processing | resolved | major | 3 h 14 min |
| 2025-09-24 09:00 UTC | SDK unavailable | resolved | major | 43 min |
| 2025-08-20 14:08 UTC | High response time on API endpoints | resolved | major | 1 h 26 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch LoyaltyLion with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"loyaltylion"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
