TrueLoyal Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded TrueLoyal Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Webhook delivery failures | 152h 36m | Resolved |
| Oct 26, 2026 | Loyalty API and rewards dashboards unavailable | 229h 10m | Resolved |
| Oct 20, 2026 | Intermittent timeouts on the loyalty member widget | 379h 12m | Resolved |
| Oct 18, 2026 | Multiple Alert Related to Gamification Feature | 435h 1m | Resolved |
| Aug 14, 2026 | Instagram and Facebook Feeds Connectivity Issues | 1873h 33m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next TrueLoyal incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This TrueLoyal Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before TrueLoyal acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single TrueLoyal outage in this window ran 78d 1h, against a mean recovery of 25d 13h. If you depend on TrueLoyal in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.