Spiff Commerce incident

Platform Performance Degradation

Major Resolved View vendor source →

Spiff Commerce experienced a major incident on September 7, 2026 affecting Hub and API and 1 more component, lasting 3h 12m. The incident has been resolved; the full update timeline is below.

Started
Sep 07, 2026, 02:06 AM UTC
Resolved
Sep 07, 2026, 05:19 AM UTC
Duration
3h 12m
Detected by Pingoru
Sep 07, 2026, 02:06 AM UTC

Affected components

HubAPIWorkflow ExperiencesFile GenerationOrchestration

Update timeline

  1. identified Sep 07, 2026, 02:06 AM UTC

    We're currently investigating increased server load causing pages and API calls to return errors. Note that things like orders and backend orchestration are built to handle failure and they will process in due time. Please return to this notice for further updates

  2. identified Sep 07, 2026, 02:06 AM UTC

    NOTE: This issue affects the AU region only.

  3. monitoring Sep 07, 2026, 02:50 AM UTC

    A fix has been implemented and we're monitoring the stability of the platform

  4. resolved Sep 07, 2026, 05:19 AM UTC

    This incident has been resolved.

  5. postmortem Sep 07, 2026, 05:19 AM UTC

    Due to bulk operations communicated to us via one of our third party connections our platform was hit but a massively unexpected number of messages. This resulted in resources receiving hugely unintended amounts of traffic causing our platform to effectively become unresponsive. We’ve put in place additional methods to catch and also throttle in situations like this moving forwards to help prevent this problem type. We apologize for any inconvenience. NOTE: Any orders or orchestrations expected to have run should be processed at this point and available inside the platform. If you are concerned this isn’t the case or are seeing otherwise please reach out to [email protected]