Notice history

Resolved
July 24, 2024 at 7:18 PM
Resolved
July 24, 2024 at 7:18 PM
This incident has been resolved.
Identified
July 24, 2024 at 7:12 PM
Identified
July 24, 2024 at 7:12 PM
Today at around 3:13pm ET there was a problem with a database change we deployed that caused a number of actions to start failing across the site.
The following actions failed during this time:
- Placing new orders
- Approving orders
- Redemptions
This problem lasted for about five minutes from 3:12:30 pm to 3:18:22 pm ET.
Failed redemptions retry automatically and recipients should have received their payout by now. However, you will have to retry newly placed orders as well as order approvals via the API.

Resolved
July 19, 2024 at 3:12 PM
Resolved
July 19, 2024 at 3:12 PM
Prepaid card issues seem to have subsided, but we are continuing to monitor for new issues.
Update
July 19, 2024 at 1:22 PM
Update
July 19, 2024 at 1:22 PM
Vendor APIs seem to be coming back online now, and fulfillment is slowly resuming back to normal.
Update
July 19, 2024 at 1:12 PM
Update
July 19, 2024 at 1:12 PM
We're seeing progress from our upstream vendors. Though gift card fulfillment isn't working yet, their APIs seem to be coming online again.
Identified
July 19, 2024 at 12:48 PM
Identified
July 19, 2024 at 12:48 PM
Our best guess is that this is related to the Crowdstrike global outage, given it's affecting multiple gift card fulfillment vendors that we rely on.
Investigating
July 19, 2024 at 12:18 PM
Investigating
July 19, 2024 at 12:18 PM
Due to internal issues with an upstream fulfillment provider, redemptions for 100+ gift cards in the US are experiencing errors, including brands like Amazon, Walmart, Target, Starbucks.
We are monitoring the product status with the fulfillment provider and should have redemption become available again soon.

Resolved
July 16, 2024 at 1:36 PM
Resolved
July 16, 2024 at 1:36 PM
This incident has been resolved.
Identified
July 16, 2024 at 10:42 AM
Identified
July 16, 2024 at 10:42 AM
Over the past year we have been gradually and methodically migrating customers away from the usage of multi-reward orders. Today, we added a new validation to ensure that no new customers could start using multi-reward orders.
Unfortunately there was a bug in our validation and we started rejecting create order payloads that contained only one reward, but did so in an array under the rewards key rather than the singular reward key. This was not intentional, and orders using that format continue to be valid today and into the future.
Any order affected by this issue would have received a 422 response with the error message "Send data for a single reward in the reward field"
This affected orders placed between 10:28 and 13:36 UTC (that's 6:42am to 9:36am ET). We apologize profusely for this issue. We are implementing additional tests and monitors to ensure this doesn't happen again.
None of the affected orders were placed in our system; please retry them now and they should succeed.

All systems operational