Spiff Commerce Outage History

Spiff Commerce is up right now

Spiff Commerce had 4 outages in the last 2 years totaling 7h 48m of downtime, averaging 0.2 incidents per month.

There were 4 Spiff Commerce outages since July 24, 2025 totaling 7h 48m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: spiffcommerce.statuspage.io

Major September 7, 2026

Platform Performance Degradation

Detected by Pingoru
Sep 07, 2026, 02:06 AM UTC
Resolved
Sep 07, 2026, 05:19 AM UTC
Duration
3h 12m
Affected: HubAPIWorkflow ExperiencesFile GenerationOrchestration
Timeline · 5 updates
  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]

Read the full incident report →

Major May 25, 2026

Orchestration Issues

Detected by Pingoru
May 25, 2026, 07:00 AM UTC
Resolved
May 25, 2026, 08:04 AM UTC
Duration
1h 3m
Affected: Orchestration
Timeline · 2 updates
  1. identified May 25, 2026, 07:54 AM UTC

    We've identified an issue causing executions to hang and are in the process of deploying a fix for the problem.

  2. resolved May 25, 2026, 08:04 AM UTC

    We've resolved the issue & any existing unfinished executions are now being run.

Read the full incident report →

Major September 9, 2025

Orchestration Performance Degraded

Detected by Pingoru
Sep 09, 2025, 02:00 AM UTC
Resolved
Sep 09, 2025, 05:32 AM UTC
Duration
3h 31m
Affected: APIOrchestration
Timeline · 5 updates
  1. identified Sep 09, 2025, 03:48 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Sep 09, 2025, 03:48 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 09, 2025, 03:49 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Sep 09, 2025, 04:36 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Sep 09, 2025, 05:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 24, 2025

Platform Outage - Unprecedented Spike in Traffic

Detected by Pingoru
Jul 24, 2025, 05:00 AM UTC
Resolved
Jul 24, 2025, 05:00 AM UTC
Duration
–
Timeline · 2 updates
  1. resolved Jul 24, 2025, 06:42 AM UTC

    At 3PM AEST on 24/7/2025, we experienced an unusually large number of requests from one of our external partners, Shopify. During this period our database was overwhelmed and our platform became unresponsive; this behaviour is equivalent to a denial-of-service attack.

  2. postmortem Jul 24, 2025, 06:47 AM UTC

    As a result of this incident, we have taken two actions to prevent future reoccurrence. 1. We have done an audit of customers that utilise our platform via Shopify. Using this audit, we can now confirm no one is relying on old methods of communication to notify us about changes in their Shopify store. 2. We have dismantled the old system entirely. All new connections will be through our new system, built late last year. This system was purpose-built to handle large traffic spikes by correctly throttling requests to our server. All partners that have installed the plugin between now and when that new system was put in place would not have been involved in this incident. Only a small subset of partners who installed within a certain time range were involved. We apologise for any inconvenience caused by this event. We strive to ensure a reliable platform and have investigated all potential improvements we can make moving forwards to keep it that way.

Read the full incident report →