Qonversion experienced a major incident on September 23, 2025 affecting API, lasting 7h 34m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 23, 2025, 02:44 PM UTC
We are currently investigating this issue.
- identified Sep 23, 2025, 02:45 PM UTC
We are continuing to work on a fix for this issue.
- identified Sep 23, 2025, 03:14 PM UTC
We are continuing to work on a fix for this issue.
- identified Sep 23, 2025, 03:55 PM UTC
We identified the issue, fixed it, and will now switch from the backup backend solution to the main one.
- identified Sep 23, 2025, 05:11 PM UTC
We continue switching from the backup backend solution to the main one. We expect the switching to be finished within 3 hours.
- identified Sep 23, 2025, 06:31 PM UTC
We continue switching from the backup backend solution to the main one. We expect the switching to be finished within 1.5-2 hours.
- identified Sep 23, 2025, 08:48 PM UTC
Our comeback from the backup backend solution to the main one is coming to an end. We expect we'll be fully out of the incident within an hour. All the delayed events will be sent to integrations, webhooks, and raw/scheduled reports by this time.
- resolved Sep 23, 2025, 09:59 PM UTC
All work has been completed, and we are pleased to report that the API is operating normally. The problem was related to degradation on the part of our database provider. We have received their incident analysis and have taken preventative measures to avoid a similar situation in the future. Our team will continue to monitor the situation over the coming days. Thank you for your patience and understanding throughout this process.