Qonversion Outage History

Qonversion is up right now

Pingoru has recorded 52 incidents for Qonversion: 31 in the last 12 months and 15 in the last 90 days.

Source: status.qonversion.io

52incidents recorded
31last 12 months
15last 90 days
3 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Qonversion in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202617 of 720 (1%)
May 202600 of 744 (0%)
June 202625 of 720 (1%)
July 202600 of 744 (0%)
August 20261234 of 744 (5%)
September 202621 of 720 (0%)
October 202614 of 590 (1%)

Incidents, newest first

Minor July 28, 2025 MRR, New subscription charts are not correct 10d 14h Realtime Dashboards

Started Jul 28, 2025, 07:42 PM UTC· resolved Aug 08, 2025, 10:11 AM UTC

  1. investigating Jul 28, 2025, 07:42 PM UTC

    The data in the MRR and New Subscription charts is inaccurate once again. This is the same issue for which we closed an incident on July 15, 2025. We are investigating the problem. Core services remain unaffected.

  2. identified Aug 08, 2025, 10:08 AM UTC

    The main cause has been found. The team is beginning to address the inaccuracy and correct the historical data.

  3. monitoring Aug 08, 2025, 10:09 AM UTC

    The problem has been resolved, and the historical data is now correct. The team is now monitoring the situation.

  4. resolved Aug 08, 2025, 10:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 14, 2025 API Performance Update 1d 19h API

Started May 14, 2025, 12:59 AM UTC· resolved May 15, 2025, 08:55 PM UTC

  1. identified May 14, 2025, 12:59 AM UTC

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

  2. monitoring May 14, 2025, 01:07 AM UTC

    API request spike observed causing unexpected behavior; however, everything is currently stable. We are continuing to investigate the details.

  3. monitoring May 14, 2025, 09:22 AM UTC

    We have identified several suspicious API users and are investigating their origin while implementing additional protections.

  4. monitoring May 14, 2025, 07:37 PM UTC

    We are continuing to monitor the situation and implement changes to optimize core requests.

  5. resolved May 15, 2025, 08:55 PM UTC

    We have completed the active phase of our work. Scheduled maintenance will follow to perform several database operations aimed at speeding up requests.

Read the full incident report →

Major March 20, 2025 API outage 1h 3m API, User Properties

Started Mar 20, 2025, 06:51 PM UTC· resolved Mar 20, 2025, 07:54 PM UTC

  1. investigating Mar 20, 2025, 06:51 PM UTC

    We are currently investigating this issue.

  2. identified Mar 20, 2025, 07:11 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 20, 2025, 07:44 PM UTC

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

  4. resolved Mar 20, 2025, 07:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2025 Partial API outage 1h 9m API

Started Mar 19, 2025, 12:20 AM UTC· resolved Mar 19, 2025, 01:30 AM UTC

  1. investigating Mar 20, 2025, 10:22 PM UTC

    We are currently investigating this issue.

  2. identified Mar 20, 2025, 10:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 20, 2025, 10:22 PM UTC

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

  4. resolved Mar 20, 2025, 10:23 PM UTC

    This incident has been resolved.

Read the full incident report →