Spare incident

Service disruption in Spare Analytics.

Minor Resolved View vendor source →

Spare experienced a minor incident on September 8, 2025 affecting [United States 1] and [Canada] and 1 more component, lasting 3h 30m. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2025, 03:36 PM UTC
Resolved
Sep 08, 2025, 07:06 PM UTC
Duration
3h 30m
Detected by Pingoru
Sep 08, 2025, 03:36 PM UTC

Affected components

[United States 1][Canada][United States 2][Japan]

Update timeline

  1. investigating Sep 08, 2025, 03:36 PM UTC

    We have identified an issue in SpareAnalytics V1 where any report that includes a custom field will not display the associated data. Instead, affected fields will appear with a dash (“–”) as if no information were recorded. At the moment, there are no available workarounds. Please note that any reports generated or downloaded since Friday (Sep 5, 2025) may also be missing data for custom fields. Our team is investigating the cause and will share updates as soon as more information becomes available.

  2. investigating Sep 08, 2025, 03:40 PM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 08, 2025, 03:59 PM UTC

    We are continuing to investigate an issue impacting Spare Analytics. Our teams remain actively engaged in identifying the root cause, and we will share further updates as soon as they are available.

  4. identified Sep 08, 2025, 04:19 PM UTC

    We have identified the issue causing missing information in the custom fields within Spare Analytics. Our development team is actively working on a fix, and we will keep you updated on the progress.

  5. monitoring Sep 08, 2025, 04:29 PM UTC

    We are currently fixing the export functionality so that it works as expected again. You should notice improvements once the release is deployed. Please note that there will be no impact on users during the release process.

  6. monitoring Sep 08, 2025, 04:52 PM UTC

    We are still working on resolving the issue with the export functionality to ensure it operates correctly. Once the fix is released, customers will experience the expected improvements. We will keep you informed and share an update as soon as the release becomes available.

  7. monitoring Sep 08, 2025, 05:17 PM UTC

    We are rolling back two recent code changes linked to custom field exports, as these appear to be the likely cause of missing data in Analytics V1 reports for multiple organizations. At this time, no workaround is available. However, once the update is deployed, exported reports should once again include all expected custom fields.

  8. monitoring Sep 08, 2025, 06:04 PM UTC

    We are rolling back two recent code changes linked to custom field exports, as these appear to be the likely cause of missing data in Analytics V1 reports for multiple organizations. At this time, no workaround is available. However, once the update is deployed, exported reports should once again include all expected custom fields.

  9. monitoring Sep 08, 2025, 06:34 PM UTC

    We are rolling back two recent code changes linked to custom field exports, as these appear to be the likely cause of missing data in Analytics V1 reports for multiple organizations. At this time, no workaround is available. However, once the update is deployed, exported reports should once again include all expected custom fields.

  10. identified Sep 08, 2025, 06:51 PM UTC

    We are still working on resolving the issue with the export functionality to ensure it operates correctly. Once the fix is released, customers will experience the expected improvements. We will keep you informed and share an update as soon as the release becomes available.

  11. resolved Sep 08, 2025, 07:06 PM UTC

    We have deployed a fix to resolve the recent issue where some custom field data was missing from Analytics V1 report exports. This was caused by two recent code changes that have since been reverted. The fix has been confirmed to be working for many customers, and we are continuing to monitor the situation to ensure all data is fully restored. If you are still experiencing this issue, a hard refresh of your browser may be necessary to load the latest version of the application. We appreciate your patience.