Issue with API

Incident Report for Qonversion

Resolved

The incident has been fully resolved. Over the past 12 hours, we have been monitoring our infrastructure and transitioning back from our backup backend solution (Aegis). Our team is currently restoring data for some previous purchases.

All services are operating normally.
Posted Sep 08, 2025 - 07:15 UTC

Update

We continue switching from backup backend to the main and merging historical events.

In addition to previous, the following API endpoints works fine now:
- `identity` (SDK identify()),
- `init` (SDK inits),
- GET `entitlements` (SDK method checkEntitlements), POST `entitlements`.
Posted Sep 08, 2025 - 07:04 UTC

Update

The main issue was resolved at approximately 16:30 UTC on September 7th. Earlier we entered incident mode and switched to the backup backend. We are now merging historical events stage.

At approximately 19:30 UTC, we resumed the delivery of delayed purchase events. Normal processing was fully restored by 21:00 UTC. The endpoints `users`, `purchases`, and `restores` are functioning well for now. The remaining endpoints are still operating through the backup backend and will be merged later.
Posted Sep 08, 2025 - 00:01 UTC

Update

We have fixed the main issue and are currently testing it.
We are working on switching back from the reserve backend solution to the main one.
Posted Sep 07, 2025 - 16:59 UTC

Update

We located the main issue, it is connected with one of our cloud providers.
We're preparing the workaround.
Posted Sep 07, 2025 - 15:42 UTC

Update

We're still on fixing the main issue.
Posted Sep 07, 2025 - 14:53 UTC

Update

We switched our backend to the reserved backend solution, we're answering codes 200 for most of our API endpoints (public and SDK).
These requests will be processed as it should be later.
We confirmed the main issue, and we're on the way to fixing it.
Posted Sep 07, 2025 - 13:37 UTC

Identified

The issue has been identified and a fix is being implemented.
Posted Sep 07, 2025 - 12:29 UTC

Investigating

We're experiencing an elevated level of API errors and are currently looking into the issue.
Posted Sep 07, 2025 - 11:20 UTC
This incident affected: API (API, User Properties) and Realtime Dashboards.