Tremendous - Notice history

API - Operational

100% - uptime
May 2024
Jun 2024
Jul 2024

Reward redemptions - Operational

100% - uptime
May 2024
Jun 2024
Jul 2024

Marketing site - Operational

100% - uptime
May 2024
Jun 2024
Jul 2024

Dashboard - Operational

100% - uptime
May 2024
Jun 2024
Jul 2024

Notice history

Jul 2024

Fulfillment errors for Amazon.com, Visa Cards and other 100+ products
  • Resolved
    Resolved

    Prepaid card issues seem to have subsided, but we are continuing to monitor for new issues.

  • Identified
    Update

    Vendor APIs seem to be coming back online now, and fulfillment is slowly resuming back to normal.

  • Identified
    Update

    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
    Identified

    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
    Investigating

    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.

API incorrectly rejecting some new orders
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    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.

Jun 2024

No notices reported this month

May 2024

No notices reported this month

May 2024 to Jul 2024

Next