Memsource incident

Degraded Performance of Phrase (EU & US) starting on July 16, 2026 17:24 CEST

Memsource is currently experiencing a major incident affecting Identity management - IDM (EU) and Identity management - IDM (US), which began 1d ago. The vendor's full update timeline is below.

Started
Jul 16, 2026, 03:47 PM UTC
Resolved
Ongoing
Duration
● 1d 7h
Detected by Pingoru
Jul 16, 2026, 03:47 PM UTC

Affected components

Identity management - IDM (EU)Identity management - IDM (US)

Update timeline

  1. investigating Jul 16, 2026, 03:47 PM UTC

    We are currently investigating an issue affecting our Metrics service that may result in duplicated metrics consumption for some customers. Our team is actively working to identify the affected components and determine the root cause. We will provide further updates as more information becomes available.

  2. identified Jul 16, 2026, 04:29 PM UTC

    We have identified the root cause as instability on a specific broker, which is causing repeated consumer group rebalancing in our Metrics service and leading to duplicate processing of metric updates. This may result in some customers experiencing incorrect consumption calculations or unexpected account blocking. We continue working on a fix.

  3. monitoring Jul 16, 2026, 05:31 PM UTC

    We have stopped the progression of the issue and are now working to identify the full scope of impact, including which organizations are affected or blocked. Affected accounts will be prioritized for resolution through a deduplication process, though this will take some time to complete.

  4. identified Jul 16, 2026, 07:04 PM UTC

    We have successfully deduplicated metrics consumption for all blocked organizations. We are continuing work to develop per-organization deduplication tooling to ensure accurate billing cycle data, with the full team scaling these fixes tomorrow morning.

  5. monitoring Jul 17, 2026, 01:02 PM UTC

    We continue to make progress resolving the duplicated metrics consumption issue first identified on July 16. The root cause has been identified and addressed. Since our last update, our team has corrected the duplicated data for all previously blocked accounts. We are now working through a remaining set of affected accounts and expect this cleanup to continue over the coming days. No further duplication is occurring, this work addresses historical data only.