Permutive Incident History

1. resolvedSep 3 · 20:00 UTC

   Between 21:14 and 22:13 UTC on 3 September, the CCS (Custom Cohort Segmentation) API experienced degraded performance. During this period the large majority of segmentation requests failed with HTTP 500 errors after a delay of several seconds. Events sent in the affected requests were still collected. However, users were not segmented and no cohorts were returned from those requests. This only affected segmentation done via direct calls to the CCS API. Requests outside this window were unaffected. The issue is now resolved and the API has returned to normal. This was caused by a failure in an upstream service which impacted the CCS API. Improvements to both the upstream service and the CCS API have been identified and are being worked on which will prevent a reoccurrence of this failure and its impact.

Reported by Permutive on their status page.

1. resolvedSep 1 · 14:43 UTC

   Between 14:10 and 14:30 UTC, the Permutive API experienced an outage. During this period we were unable to receive events and identities. User targeting was unaffected. However, events sent during this window were not collected, and will therefore be missing from two areas: Routing Insights Data collected outside this window is unaffected. The issue is now resolved and event collection has returned to normal.

Reported by Permutive on their status page.