Kard Status

Kard Status

Back

Incident history

Aug 2026 - Oct 2026

October

Oct 14
Investigating

8:14 PM UTC

Elevated error rates on Rewards API endpoints

Between 16:13 and 16:31 UTC on October 14, 2026, some requests to the Rewards API returned HTTP 500 errors after a delay of about 4 seconds. The issue was caused by a dependency of our offers service, and it has been resolved. All endpoints are working normally. We’re still investigating the root cause and will put safeguards in place to prevent this from happening again.

1 update
Oct 09

6:04 PM UTC - 6:58 PM UTC (53min duration)

Elevated 404 errors on the v1 Offers by User endpoint

The elevated 404 errors on the Offers by User endpoint (GET /rewards/merchant/offers/user/{id}) between 17:32 UTC and 18:15 UTC on October 9 have been resolved. The cause was a recent change to how issuer identity is resolved, which has been reverted. Error rates have been back to normal since 18:15 UTC and we continue to monitor.

4 updates

September

Sep 20

7:55 PM UTC - 8:25 PM UTC (30min duration)

Degraded offer eligibility responses

Capacity increased. Error rates returned to normal.

We are monitoring and following up with changes to prevent recurrence.

2 updates
Impacted:
Rewards API

August

Aug 31

6:12 PM UTC - Sep 1 5:29 PM UTC (23h17min duration)

Elevated API errors

Between August 23 and August 31, during several periods, some requests to our offers endpoints timed out or returned incomplete results, affecting a subset of customers.

This was caused by a capacity limit in an internal service that evaluates offer eligibility. We have increased that capacity and verified the limit is no longer reached at peak traffic.

This incident is resolved.

2 updates
Aug 25

6:34 PM UTC - Aug 26 10:42 PM UTC (1d4h8min duration)

Elevated errors and latency on the Offers API

Between August 14 and August 25, 2026, a subset of requests to Kard's Eligibility API returned errors or timed out during several brief windows, the longest on August 23–24 (UTC).

The cause was a supporting policy-evaluation service that exhausted its allocated memory under peak load, causing it to restart and briefly stop responding. Requests that did not hit the affected instances were served normally, and no data was lost or incorrectly processed.

We have increased the service's capacity and adjusted its autoscaling configuration. The service has been stable since. We are also making changes to the component responsible for the memory growth to prevent recurrence.

2 updates
Aug 10

8:45 PM UTC - 9:28 PM UTC (43min duration)

Slow Responses and Errors for Offer Requests

Latency and error rates on the affected APIs have returned to normal.

3 updates