Issue with API

The incident has been resolved. Attribution data (ASA and others) is still paused; we’re working on restoring it. You’ll start seeing data affected by the incident in your dashboard within the next 24 hours.

On top of that, our team is entirely focused on making several urgent changes that will be implemented during this week:
- Add extra caching mechanism for our APIs, enabling them to work in case databases are fully down
- Add additional replicas to the base cluster
- Collaborate with the cloud provider to prevent the reoccurrence of the issue

The incident has been resolved. Attribution data (ASA and others) is still paused; we’re working on restoring it. You’ll start seeing data affected by the incident in your dashboard within the next 24 hours.

On top of that, our team is entirely focused on making several urgent changes that will be implemented during this week:
- Add extra caching mechanism for our APIs, enabling them to work in case databases are fully down
- Add additional replicas to the base cluster
- Collaborate with the cloud provider to prevent the reoccurrence of the issue

Resolved
- Analytics & Subscription Management modes are fully operational
- Subscription Events are being sent to enabled integrations

In progress:
- Charts’ data & older revenue events actualisation are in progress
- Attribution (ASA and other) is paused at the moment; we’re working on restoring it
- We’re adding an additional caching layer between our cloud provider and us to avoid potential service interruptions

Integrations are up and running.

The next steps:
- To resend events affected by the incident
- To have other Qonversion’s system parts work as expected.

We’ll keep you updated.

Qonversion API is operational, and purchases are working as expected. We’re monitoring the situation and working on problems with other parts of the service (integrations, raw data reports, etc.). Data in dashboards is still delayed. We’re working on this at the moment. We’ll be providing more updates soon.

We are continuing to monitor for any further issues.

We keep monitoring the situation. The Subscription management mode & API have been restored. Data in dashboards is delayed and actual for the time before the incident starts.

We have yet to deal with the aftermath of the incident. We will get back to you with details as soon as the technical work is completed.

A fix has been implemented and we are monitoring the results.

Our team is continuing to work on getting the service back up and running on the new cluster. We’re closely working with our cloud provider. Our team is integrating the recently released patch for the MySQL software to resolve the incident.

Our team is currently trying to get the service back up and running on the new cluster. We’re closely working with our cloud provider, which is also trying to run our service back up on the old cluster with our backup data. We’re planning to complete the final steps for migration to a new database and assuming to fix this issue as soon as possible.

We are still working on resolving this problem and will give you more information soon.

Unfortunately, the patch was not successful. Our engineers are now exploring next steps.

Our team is currently in the process of integrating the recently released patch for the MySQL software. This patch includes various updates and fixes that will improve the overall performance and security.

The issue has been identified. We have escalated that to our database provider. We are working on the fix.

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