iAdvize Outage History

iAdvize is up right now

Pingoru has recorded 53 incidents for iAdvize: 16 in the last 12 months and 4 in the last 90 days.

Source: status.iadvize.com

53incidents recorded
16last 12 months
4last 90 days
95 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking iAdvize 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 202632 of 720 (0%)
May 202600 of 744 (0%)
June 202620 of 720 (0%)
July 202600 of 744 (0%)
August 202610 of 744 (0%)
September 202600 of 720 (0%)
October 2026318 of 584 (3%)

Incidents, newest first

Major February 13, 2025 P1 - Bots stopped responding to visitors 44m

Started Feb 13, 2025, 03:54 PM UTC· resolved Feb 13, 2025, 04:38 PM UTC

  1. resolved Feb 14, 2025, 08:48 AM UTC

    On Thursday, February 13, there were disruptions related to the bots. From 16:54 to 17:38 CET, the chatbots did not receive visitor messages and were unable to respond to conversations. As a result, those conversations were left unanswered and were closed by the auto-closing bot feature.

Read the full incident report →

Major February 3, 2025 P1 - Perturbations in engagement and conversation creation 1h 58m Engagement Notification

Started Feb 03, 2025, 02:51 PM UTC· resolved Feb 03, 2025, 04:49 PM UTC

  1. investigating Feb 03, 2025, 02:51 PM UTC

    You may experience some disturbances on conversation routing since 3:39pm CET. We are currently investigating this issue and its impacts. We keep you informed, thanks for your patience and understanding.

  2. monitoring Feb 03, 2025, 02:57 PM UTC

    A fix has been implemented, and everything is back to normal. You should be able to see notifications on your Website again. We keep monitoring the production. Thank you.

  3. resolved Feb 03, 2025, 04:49 PM UTC

    This incident has been resolved since 3:48pm.

Read the full incident report →

Major December 18, 2024 P1 - Impossibility for visitors to start new conversations 49m Chat, Video, Mobile SDK

Started Dec 18, 2024, 01:39 PM UTC· resolved Dec 18, 2024, 02:28 PM UTC

  1. investigating Dec 18, 2024, 01:39 PM UTC

    It is not possible for visitors to start conversations. This incident is impacting all our services. Our technical team is currently looking into the issue, we will update you as we learn more.

  2. investigating Dec 18, 2024, 01:41 PM UTC

    Please note that ongoing conversations are not impacted. Only new conversations can't be created

  3. monitoring Dec 18, 2024, 01:47 PM UTC

    We found the root cause of the issue. Yet, a fix is live. All is working normally since 2:40pm (CET) We keep monitoring the production.

  4. resolved Dec 18, 2024, 02:28 PM UTC

    This incident has been resolved

Read the full incident report →

Major November 21, 2024 P1 - Disturbances on the Conversations Panel 4h 17m Login, Login, Chat, Engagement Notification and 26 more

Started Nov 21, 2024, 08:52 AM UTC· resolved Nov 21, 2024, 01:09 PM UTC

  1. investigating Nov 21, 2024, 08:52 AM UTC

    We have some disturbances on the platform. You may notice blank page on the conversation panel or on the administration. Also difficulties to close conversations. The technical team is investigating the issue. We keep you informed.

  2. monitoring Nov 21, 2024, 09:01 AM UTC

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

  3. resolved Nov 21, 2024, 01:09 PM UTC

    After a period of monitoriy, we confirm that this incident is resolved. A post-mortem will be published soon. We are sorry for the inconvenience caused.

  4. postmortem Nov 25, 2024, 01:40 PM UTC

    **Incident:** On November 20th \(17:19 > 17:52 CET\) and November 21st \(9:30 > 9:43 CET\), we experienced two incidents degrading the user experience on the Conversation panel and Administration. During this period, conversation processing by agents was disrupted by white screens or error messages. In addition, the monitoring of stats reports by managers has also been impacted by error messages. These disturbances are the result of changes made to the platform infrastructure as part of our regular and scheduled system maintenance. Although initially qualified as non major risk and validated in a pre-prod environment, these planned actions had an unexpected impact on platform stability. Access to services critical to the proper operation of the platform have been temporarily cut. ‌ **Resolution** To solve this issue, our technical team had to manually change some settings on these critical services and then to restart them. Getting the required underlying services back to their nominal state allowed the Conversation panel and the Administration application to return to their own nominal state. ‌ **Actions for the future** * \(Done\) Review our internal processes to ensure that customer communication on our [status page](https://status.iadvize.com/) is more responsive * \(Done\) Review our maintenance process to better identify and scope potential negative impacts on the iAdvize platform and adapt our execution plans subsequently * \(Done\) Improve probes and alerting on failing services to improve reactivity ‌ **Focus on the Black Friday period** Looking ahead to the next critical period, we're confident that we'll handle incoming traffic on the iAdvize platform without disruption. This incident is the consequence of manual actions whose impact has not been adequately anticipated. This is not a problem related to traffic management or platform scaling. In the meantime, we have been proactive in getting the iAdvize platform ready and we reviewed teams' preparation for this high-traffic period. Our modus operandi is based on three pillars which have already been identified and implemented: - freezing period : no new code added in production - stress test : test the platform’s scalability with heavy load pick traffic - team’s mobilization : assigning the right people to monitor the main components 24/7 Be assured that our team and platform are ready for the end of the year.

Read the full incident report →

Major November 20, 2024 P1 - Disturbances on the Conversations Panel and Administration App 9m Login, Login, Chat, Engagement Notification and 26 more

Started Nov 20, 2024, 05:12 PM UTC· resolved Nov 20, 2024, 05:21 PM UTC

  1. monitoring Nov 20, 2024, 05:12 PM UTC

    From 5:19PM CET to 5:52PM CET, we encountered disturbances on all the platform. You may have noticed blank page on the conversation panel or on the administration. Also difficulties to close conversations. This has been identified, and the technical team has restored the situation. We keep on monitoring the platform.

  2. resolved Nov 20, 2024, 05:21 PM UTC

    This incident has been resolved. More information on this status will be provided in the coming days. Thank you for your patience.

  3. postmortem Nov 25, 2024, 01:45 PM UTC

    **Incident:** On November 20th \(17:19 > 17:52 CET\) and November 21st \(9:30 > 9:43 CET\), we experienced two incidents degrading the user experience on the Conversation panel and Administration. During this period, conversation processing by agents was disrupted by white screens or error messages. In addition, the monitoring of stats reports by managers has also been impacted by error messages. These disturbances are the result of changes made to the platform infrastructure as part of our regular and scheduled system maintenance. Although initially qualified as non major risk and validated in a pre-prod environment, these planned actions had an unexpected impact on platform stability. Access to services critical to the proper operation of the platform have been temporarily cut. ‌ **Resolution** To solve this issue, our technical team had to manually change some settings on these critical services and then to restart them. Getting the required underlying services back to their nominal state allowed the Conversation panel and the Administration application to return to their own nominal state. ‌ **Actions for the future** * \(Done\) Review our internal processes to ensure that customer communication on our [status page](https://status.iadvize.com/) is more responsive * \(Done\) Review our maintenance process to better identify and scope potential negative impacts on the iAdvize platform and adapt our execution plans subsequently * \(Done\) Improve probes and alerting on failing services to improve reactivity ‌ **Focus on the Black Friday period** Looking ahead to the next critical period, we're confident that we'll handle incoming traffic on the iAdvize platform without disruption. This incident is the consequence of manual actions whose impact has not been adequately anticipated. This is not a problem related to traffic management or platform scaling. In the meantime, we have been proactive in getting the iAdvize platform ready and we reviewed teams' preparation for this high-traffic period. Our modus operandi is based on three pillars which have already been identified and implemented: * freezing period : no new code added in production * stress test : test the platform’s scalability with heavy load pick traffic * team’s mobilization : assigning the right people to monitor the main components 24/7 Be assured that our team and platform are ready for the end of the year.

Read the full incident report →