Is Qonversion down?

We're experiencing an elevated level of API errors and are currently looking into the issue.

Between approximately 06:03 and 06:13 UTC, most requests to the Qonversion API returned errors, and the dashboard was briefly unavailable. We have identified the cause as an infrastructure availability event with our cloud provider and have switched API traffic to a fallback path. The API is responding again; some functionality, including remote configuration delivery, remains degraded and some purchase events may be processed with a delay. We are working on full recovery and will post the next update within 30 minutes.

Update 07:50 UTC — The API continues to operate on a fallback path and is responding normally. We have started processing the backlog of requests received during the incident; purchase and user-data updates from that period are being applied progressively and may appear with a delay. Remote configuration delivery remains degraded until the recovery completes. The original impact window was approximately 06:03–06:13 UTC, when most API requests returned errors. Next update within 60 minutes.

Recovery is complete. API traffic has been returned to the primary path and all services are operating normally. The backlog of requests received during the incident has been fully processed; purchases, user data and remote configuration updates from that period have been applied. We will continue to monitor closely and post a final update within 60 minutes.

This incident is resolved. Between approximately 06:03 and 06:13 UTC on 20 October, most requests to the Qonversion API returned errors and the dashboard was briefly unavailable, due to an infrastructure availability event with our cloud provider. From 06:13 UTC the API was served through a fallback path: requests were accepted, while remote configuration delivery was degraded and purchase and user-data updates were applied with a delay until the backlog was processed. Full service on the primary path has been restored since 09:43 UTC, and we have confirmed no recurrence since. We're sorry for the disruption.

Between approximately 08:01 and 08:03 UTC on 24 September, most requests to the Qonversion API returned errors, and the dashboard briefly returned errors for some requests. The cause was an infrastructure capacity event that temporarily left the API without enough serving capacity. Service recovered automatically at 08:03 UTC and has been stable since. We're sorry for the disruption.

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.