Vendor Status Watch

← all vendors

LoyaltyLion status history

Current state: operational — “All Systems Operational” per https://status.loyaltylion.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
1incidents, last 90 days
4incidents on record
Incidents per week, last 12 weeks:
Get LoyaltyLion alerts in your Slack — free templateRSS for LoyaltyLion

How long do LoyaltyLion incidents last?

2.3 hmedian incident duration4 measured
5.1 h90th percentile1 in 10 ran longer
86 minmedian, major/critical only3 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-01 17:56 UTCElevated API/SDK response times and error ratesresolvedminor5 h 04 min
2025-10-09 16:25 UTCDelays in data processingresolvedmajor3 h 14 min
2025-09-24 09:00 UTCSDK unavailableresolvedmajor43 min
2025-08-20 14:08 UTCHigh response time on API endpointsresolvedmajor1 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
}