Is Qonversion down?

Between approximately 11:01 and 11:08 UTC, requests to the Qonversion API returned errors or timed out. For about two minutes most requests were affected; for the rest of the window a portion of requests to SDK initialization, purchases and entitlements failed or were slow. Service recovered at 11:08 UTC without data loss on our side; SDK retries covered most affected calls. We are monitoring closely and will post an update within 60 minutes.

This incident has been resolved.

Between August 17 and August 20, 11:10 UTC, a defect caused some iOS subscription transactions to be duplicated under more than one user profile. Affected projects may see inflated revenue and subscription-event counts in dashboards and exports, and some duplicate events were delivered to connected integrations and webhook endpoints. No payments or end-user purchases were affected — this is limited to analytics data. The defect is disabled and no new duplicates are being created. We are removing the duplicated data and will contact affected accounts directly with details.

Removal of duplicated records from dashboards and exports is in progress. If your project ingests Qonversion webhooks or integration events and you store them raw, duplicated events can be identified by the same App Store transaction ID appearing under different Qonversion user IDs; deduplicating on (store transaction ID, event type) is safe.

Duplicated records have been removed — dashboards and exports now show corrected figures, and per-user payment summaries have been recalculated.

We are continuing to monitor for any further issues.

data repair is complete end-to-end

Between 18:00 and 18:03 UTC, some API requests were unavailable or returned errors. Service availability has recovered, and we are monitoring the results.

The issue has been resolved and service performance has returned to normal.

Between 21:18–21:23 UTC the Qonversion API experienced elevated error rates. Service has fully recovered and all systems are operating normally.

This incident has been resolved.

Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.

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

The root cause has been identified and fixed. The issue affected Google Play processing only — Apple App Store was not impacted. Google Play subscription updates, webhooks, and dashboard data may be delayed while our systems catch up over the next few hours. No data has been lost.

Recovery is progressing well: the processing backlog is down more than 85% and draining quickly.

Real-time purchase processing has been operating normally — the backlog affected only background subscription checks. Webhook delivery remained near real-time throughout; only a small share of events was delayed while the backlog cleared.

This was a minor incident with limited customer impact. All systems are operating normally and the processing backlog has fully cleared. No data was lost. This incident has been resolved.