Is there an iAdvize (HA) outage?
iAdvize (HA) status: Systems Active
Last checked: 5 seconds ago
Get notified about any outages, downtime or incidents for iAdvize (HA) and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 5 seconds ago
Get notified about any outages, downtime or incidents for iAdvize (HA) and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for iAdvize (HA).
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Mobile App | Active |
| Administration | Active |
| Channel settings | Active |
| Distribution settings | Active |
| Engagement settings | Active |
| Login | Active |
| Sending email | Active |
| Statistics | Active |
| Users management | Active |
| APIs | Active |
| GraphQL API | Active |
| Rest API | Active |
| Webhook | Active |
| Bot | Active |
| Bot service (except IA features) | Active |
| Copilot Agent | Active |
| Copilot Shopper | Active |
| Conversation Panel | Active |
| Canned answer | Active |
| Conversation closure | Active |
| Conversation transfert | Active |
| Conversation views | Active |
| Login | Active |
| Message exchange | Active |
| Mirroring / Cobrowsing | Active |
| Onsite Channels | Active |
| Call | Active |
| Chat | Active |
| Mobile SDK | Active |
| Video | Active |
| Third Party Channels | Active |
| Active | |
| Facebook Messenger | Active |
| SMS | Active |
| Active | |
| X | Active |
| Visitor’s interface | Active |
| Engagement Notification | Active |
| iAdvize Messenger | Active |
View the latest incidents for iAdvize (HA) and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Jan. 23, 2023, 2:25 p.m.
Description: ## **Incident** The iAdvize platform has encountered a major instability degrading the user experience on December 14th, 2022 between 9:42 to 10:00 \(UTM\+1\). During this disturbance, we experienced a break in access on our Main core database. As this database is central to many critical services, the iAdvize platform has experienced a breakdown on major components : the discussion panel for agents, administration for managers/administrators and livechat tag for visitors. Once this first incident was resolved, we experienced a second major disruption in the processing of social conversations from the discussion panel \(Whatsapp, Facebook Messenger, Twitter, SMS, Google Business Messages, Apple Business Messages\) between 10:00 to 12:14 \(UTM\+1\). ## **Reasons** This major instability on our main Core database is due to an unexpected crash of a data cleaning routine. This action, which is regularly carried out during off-peak hours, went beyond its original schedule and led to a stop in reading/writing new data. As a result, our Core database was no longer accessible for our critical services necessary for the proper functioning of the iAdvize platform. Concerning the social channels, we were unable to restart the social routing service properly due to an internal error never before encountered by our technical teams. ## **Resolution** We carried out several successive actions to fix the initial problem : * First we identified the maintenance script responsible for the data read/write break * We manually killed this maintenance script * Then we failed over to our Core backup database in order restore the platform accesses Concerning the social channels : * Once the internal error identified, we were able to apply a hotfix on the social routing service and thus enable its restart ## **Actions for the future** * Optimise the data cleaning routine to automatically shut it down when it reaches an abnormally high execution time * Study on the implementation of fastest failover system in case our main Core database is inaccessible * Apply regular major updates in order to keep our social routing service up-to-date
Status: Postmortem
Impact: Critical | Started At: Dec. 14, 2022, 8:58 a.m.
Description: After a monitoring period, we close this incident. Thank you for your patience and understanding.
Status: Resolved
Impact: Minor | Started At: Nov. 25, 2022, 8:42 a.m.
Description: WhatsApp confirms the end of the incident. The messages waiting to be sent could be sent.
Status: Resolved
Impact: Major | Started At: Oct. 25, 2022, 8:24 a.m.
Description: _This incident occurred after a deployment made early in the morning. The release content is not the cause of the incident._ _The problem lies in restarting the services affected by the deployment. This action requires a large amount of memory and CPU._ _It seems that the node used this morning was too limited in CPU preventing the bot services from starting properly._ _Around 9:25am \(CEST\), we manually ejected this node in order to force a reboot on a node with enough CPU._ _We will adapt the server configuration to prevent this problem in the future._
Status: Postmortem
Impact: Critical | Started At: Sept. 28, 2022, 6:39 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
