Spektrix incident

API issue with syncing between Spektrix and websites

Minor Resolved View vendor source →

Spektrix experienced a minor incident on November 5, 2025 affecting APIs - UK and Ireland and APIs - US and Canada and 1 more component, lasting 20h 49m. The incident has been resolved; the full update timeline is below.

Started
Nov 05, 2025, 05:43 PM UTC
Resolved
Nov 06, 2025, 02:32 PM UTC
Duration
20h 49m
Detected by Pingoru
Nov 05, 2025, 05:43 PM UTC

Affected components

APIs - UK and IrelandAPIs - US and CanadaAPIs - Australia and New Zealand

Update timeline

  1. identified Nov 05, 2025, 05:43 PM UTC

    We’ve identified an issue where the API is sporadically returning 500 errors, which may affect how Spektrix is syncing with your website CMS for event listings, including instance dates and statuses. If you are noticing any impact on your website, such as incorrect show dates or status of instances, we recommend contacting your web developer, sending them a link to this page and directing them to the 'Note for web developers and integrators' below. We’ll continue to update with any progress or now info here. Note for web developers and integrators: We are noticing transient and intermittent 500 errors in the API, which we are investigating. In general - regardless of today's issues - to ensure 500, 401 or any other unexpected responses do not impact your syncing between Spektrix and your website / partner platform, you may wish to implement a resilience strategy such as retrying failed requests and/or retaining your last 'good' sync.

  2. monitoring Nov 05, 2025, 06:21 PM UTC

    We identified the cause of the sporadic API issue that is affecting how some websites are syncing with Spektrix via the API. We have put a fix in place to mitigate the issue and will continue to monitor the issue closely through tomorrow. You should start to see improvement in your website syncing, and any issues with event/instance information should be resolving.

  3. resolved Nov 06, 2025, 02:32 PM UTC

    We have been monitoring the fix that was put in place and have not seen any issues with the API through the evening and into this morning. We will be marking this as resolved and will continue to monitor our API.