Is Qonversion Down?

Starting at 18:12 UTC we observed degraded performance and an increased error rate from Apple's StoreKit 1 receipt verification servers. Projects with a valid In-App Purchase Key (App Store Server API) configured in Qonversion were not affected for new purchases: those were processed through Apple's unaffected StoreKit 2 servers. For projects without this key, some App Store purchases made during this period were not processed. In addition, scheduled subscription status checks for part of iOS subscribers were not completed, so renewal events and webhooks for them may be delayed. Android, Stripe and Paddle were not affected. We have reprocessed all affected purchases and subscription checks. Events for them keep their original purchase dates; webhooks were delivered later than usual. The incident is resolved.

Between approximately 07:57 and 08:01 UTC on October 29, a majority of requests to the Qonversion API failed during a brief incident, affecting SDK initialization, purchase processing, and other API operations. Service recovered and has remained stable for over an hour. We apologize for the disruption and the delay in posting this update.

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. --- [2026-10-20T09:41:34.818Z] (monitoring) 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. --- [2026-10-20T07:52:40.935Z] (identified) 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. --- [2026-10-20T06:52:37.491Z] (identified) 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. --- [2026-10-20T06:11:59.955Z] (investigating) We're experiencing an elevated level of API errors and are currently looking into the issue.