Historique des pannes de Kustomer

1. 9 septembre 2026 à 19:25 UTCinvestigating

   Kustomer a identifié un événement affectant Kustomer Voice sur tous les PRODS qui peut causer des problèmes lors de la tentative de faire des appels sortants. Notre équipe travaille actuellement à la mise en œuvre d'une résolution. Veuillez vous attendre à de nouvelles mises à jour dans les 30 prochaines minutes.

2. 9 septembre 2026 à 19:45 UTCmonitoring

   Kustomer a mis en place une mise à jour pour traiter un événement affectant Kustomer Voice dans tous les PROD. Notre équipe surveille actuellement cette mise à jour pour s'assurer que le problème est entièrement résolu. Afin de résoudre complètement le problème à votre fin, veuillez demander à tous les agents de rafraîchir leur instance Kustomer.

3. 9 septembre 2026 à 19:52 UTCresolved

   Kustomer a résolu un événement affectant Kustomer Voice dans tous les PROD. Pour résoudre ce problème, notre équipe a repoussé une mise à jour. Après un suivi attentif, notre équipe a déterminé que toutes les zones touchées sont maintenant entièrement restaurées. Veuillez contacter le support Kustomer à [email protected] si vous avez d'autres questions ou préoccupations.

4. 2 octobre 2026 à 17:55 UTCpostmortem

   Résumé Le 9 septembre 2026, un événement de service a empêché les utilisateurs de lancer des appels téléphoniques sortants. Lorsque les utilisateurs touchés ont sélectionné **Call**, l'appel n'a pas commencé. Impact L'événement a affecté l'initiation de l'appel vocal sortant pour quatre organisations. D'autres flux de travail peuvent avoir continué à fonctionner normalement. Aucune perte de données ni aucun impact sur la sécurité n'ont été identifiés. Calendrier * **Le 9 septembre, 12h27 ET :** Une mise à jour de l'application Voix a été publiée. * **Le 9 septembre, vers 14h00 ET:** Les rapports d'appels sortants touchés ont commencé. * **Le 9 septembre, environ 15 h 19 ET:** L'atténuation a commencé. * **Le 9 septembre, vers 15 h 30 ET:** L'appel vocal sortant a été rétabli. La cause profonde Une mise à jour d'applications vocales a provoqué des tentatives d'appel sortant. La mise à jour affectée a été reportée. Résolution La mise à jour affectée a été repoussée, rétablissant l'appel vocal sortant pour les utilisateurs touchés. L'enquête est terminée. Actions préventives * Améliorer les procédures de récupération afin de réduire le temps de restauration du service durant les événements futurs. * Ajouter une couverture de validation pour les configurations d'appel sortant prises en charge avant les futures versions. * Améliorer la surveillance, l'alerte interne et la rétroaction des utilisateurs lorsqu'un appel ne peut pas être lancé.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 8 septembre 2026 à 13:23 UTCinvestigating

   Kustomer est conscient d'un événement affectant les liens et le contenu en utilisant le domaine par défaut kustomer.help (pas les domaines clients personnalisés) - y compris les URL du Centre d'aide et les enquêtes CSAT - qui peut causer des problèmes de visibilité. Notre équipe s'efforce actuellement d'identifier la cause de cette question dans le but de mettre en oeuvre une résolution. Veuillez vous attendre à des mises à jour supplémentaires dans les 30 prochaines minutes, veuillez contacter Kustomer Support à [email protected] pour toute autre question ou mise à jour.

2. 8 septembre 2026 à 13:24 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 8 septembre 2026 à 13:39 UTCresolved

   Kustomer a résolu un événement affectant les liens et le contenu en utilisant le domaine kustomer.help par défaut (pas les domaines clients personnalisés) qui a causé des problèmes de visibilité. Après un suivi attentif, notre équipe a déterminé que toutes les zones touchées sont maintenant entièrement restaurées. Veuillez contacter Kustomer Support à [email protected] si vous avez des questions ou des préoccupations supplémentaires.

4. 10 septembre 2026 à 21:05 UTCpostmortem

   Résumé Du 7 au 8 septembre 2026, certains clients n'ont pas pu accéder aux pages de la base de connaissances et aux liens connexes hébergés sur le domaine `*.kustomer.help` par défaut. Les clients utilisant le domaine de la base de connaissances par défaut dans l'environnement prod1 ont rencontré des avertissements de certificat de navigateur qui ont empêché l'accès au contenu de la base de connaissances. Les liens connexes utilisant le même domaine, y compris certains liens d'enquête, ont également été touchés. Les clients utilisant des domaines de base de connaissances personnalisés et des domaines de base de connaissances partagés dans d'autres environnements de production n'ont pas été touchés. La cause de la mort Un certificat de sécurité utilisé par le domaine de la base de connaissances partagée a expiré avant la validation du renouvellement. Cela a amené les navigateurs à refuser les connexions aux liens desservis par ce domaine, tandis que le service de base de connaissances sous-jacent est resté disponible. **Échéancier** **Sep 7, 2026** **8:00 ET**: Le certificat de domaine de base de connaissances par défaut de Kustomer est expiré. À ce moment, les clients peuvent avoir commencé à rencontrer des avertissements de certificat lors de l'accès au contenu de la base de connaissances. (en milliers de dollars) **Sep 8, 2026** **8:37 ET** Kustomer reçoit des rapports d'avertissements de certificat pour le contenu par défaut du domaine de base de connaissances et des liens connexes **8:38 AM ET** Kustomer Engineering est avisé et commence notre processus de gestion des incidents sur appel **9:00 ET** Kustomer Engineering identifie la délivrance du certificat de domaine partagé et commence les étapes de remise en état **9:24 AM ET** Kustomer Engineering complète les étapes de remise en état **9:37 ET** Le fournisseur de certificat de Kustomer, reconnaissant que les étapes de remise en état étaient terminées et fournissant un nouveau certificat pour le domaine de la base de connaissances par défaut, restaure le service **Les leçons/améliorations** Kustomer Engineering dispose d'une équipe dédiée à l'infrastructure qui travaille en permanence pour maintenir et améliorer la disponibilité, la fiabilité, la tolérance aux défauts de Kustomer. Dans le cadre de nos investissements continus dans ces domaines, nous avons identifié les mesures suivantes liées à cette question : * Transférer le certificat de domaine partagé à une approche de renouvellement automatisée. * Ajouter une surveillance proactive et des alertes pour l'expiration du certificat dans les domaines communs à la clientèle. * Examiner d'autres certificats en utilisant la même approche de renouvellement et hiérarchiser les mises à jour nécessaires. * Procédures de recouvrement des documents et propriété des activités de renouvellement des certificats.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 25 août 2026 à 13:51 UTCmonitoring

   Kustomer est au courant d'un événement signalé par un de nos fournisseurs tiers (PubNub) affectant la messagerie en temps réel pour les orgs dans Prod1 qui peut causer des messages de chat, des notifications d'agent, et des mises à jour en direct à être retardé ou ne pas apparaître en temps réel dans la plate-forme. Notre équipe surveille activement l'incident et travaille avec le fournisseur lorsque c'est possible pour résoudre le problème. Vous pouvez également suivre le statut de PubNub ici: https://status.pubnub.com/incidents/cz6q37z3s1d5. Veuillez vous attendre à d'autres mises à jour dans les 3 prochaines heures, et contacter le support Kustomer à [email protected] si vous avez des questions ou des préoccupations supplémentaires.

2. 25 août 2026 à 14:17 UTCresolved

   L'événement lié à PubNub précédemment signalé affectant la messagerie en temps réel pour les orgs dans Prod1 a été résolu. PubNub a confirmé que le problème a été atténué à leur fin - aucun message n'a été manqué et aucun impact client n'a eu lieu pendant l'événement. Toutes les zones touchées restent pleinement opérationnelles. Veuillez contacter le support Kustomer à [email protected] si vous avez d'autres questions ou préoccupations.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 30 juillet 2026 à 17:43 UTCinvestigating

   Kustomer est au courant d'un événement touchant l'éditeur de texte qui peut causer des problèmes lors de la saisie et de l'ajout de contenu comme Raccourcis. Notre équipe s'efforce actuellement d'identifier la cause de cette question dans le but de mettre en oeuvre une résolution. S'il vous plaît attendre des mises à jour supplémentaires dans les 30 prochaines minutes, veuillez contacter Kustomer Support via [email protected] pour toute autre question ou mise à jour.

2. 30 juillet 2026 à 18:15 UTCmonitoring

   Kustomer a mis en place une mise à jour pour traiter un événement touchant l'éditeur de texte qui peut causer des problèmes lors de la saisie et de l'ajout de contenu comme Raccourcis. Rafraîchir votre navigateur résoudra complètement le problème. Notre équipe surveille actuellement cette mise à jour pour s'assurer que le problème est entièrement résolu. Veuillez vous attendre à d'autres mises à jour dans les 30 prochaines minutes, et contacter le support Kustomer à [email protected] si vous avez des questions ou des préoccupations supplémentaires.

3. 30 juillet 2026 à 19:15 UTCresolved

   Kustomer a résolu un événement affectant l'éditeur de texte qui peut causer des problèmes lors de la saisie et de l'ajout de contenu comme Raccourcis. Pour résoudre ce problème, notre équipe est revenue à une version précédente. Après un suivi attentif, notre équipe a déterminé que toutes les zones touchées sont maintenant entièrement restaurées. Veuillez contacter le support Kustomer à [email protected] si vous avez d'autres questions ou préoccupations.

4. 8 août 2026 à 04:49 UTCpostmortem

   # **Summary** On July 30, 2026, the draft text editor on Kustomer’s Timeline product experienced degraded functionality in certain user workflows. Impact included sporadic cursor behavior, text erasure, and issues with copying and pasting text and shortcuts. # **Root Cause** This issue was introduced by a change to the editor that was not fully caught before release. Due to misalignment in our QA process our pre-release validation did not adequately cover the real-world editing patterns affected by this change. Furthermore, this misalignment contributed to a delay in Kustomer’s understanding of the incident's resolution status. # **Timeline** ## **Jul 30, 2026** **11:12 AM ET:** The editor change was deployed **12:27 PM ET:** Kustomer Technical Support escalated the incident to Kustomer’s OnCall process, notifying Engineering immediately. **12:34 PM ET:** Kustomer Engineering identified the issue and completed a rollback **12:51 PM ET:** Internal testing incorrectly confirms that the issue has been fully resolved, due to some customers reporting the issue no longer presented itself **1:29 PM ET:** Continued reports of issue are received from customers who did not receive the full resolution rollout **1:34 PM ET:** Discovery made that  the rollback did not fully deploy to resolve the issue. Kustomer Engineering makes additional change to ensure resolution **2:01 PM ET:** Corrective change deployed, and fix is confirmed # **Lessons/Improvements** Kustomer Engineering maintains a robust CI/CD process, and a multi-environment release process designed to prevent issues of this nature. As part of our continual investment in these areas, we have identified the following action items: * Ensure that our internal pre-production environments align with our customer-facing experience, including but not limited to the editor experience, so that issues of this nature are caught earlier in development * Complete an audit of our automated CI/CD process and test coverage of major features, removing any gaps that are identified

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 26 juillet 2026 à 01:13 UTCidentified

   Kustomer a identifié un événement affectant les événements de plate-forme dans les orgs PROD1 qui peut causer des retards sur les données basées sur les événements. Notre équipe travaille actuellement à la mise en œuvre d'une résolution. Veuillez vous attendre à des mises à jour supplémentaires dans les 30 prochaines minutes, et contacter Kustomer Support à [email protected] pour toute autre question ou mise à jour.

2. 26 juillet 2026 à 01:16 UTCidentified

   Kustomer a identifié un événement affectant les événements de plate-forme dans les orgs PROD1 qui peut causer des retards sur les données basées sur les événements. Notre équipe travaille actuellement activement à la mise en œuvre d'une résolution. Veuillez vous attendre à des mises à jour supplémentaires dans les 30 prochaines minutes, et contacter Kustomer Support à [email protected] pour toute autre question ou mise à jour.

3. 26 juillet 2026 à 02:03 UTCidentified

   Kustomer continue de travailler sur la question touchant les événements de plate-forme dans les orgs PROD1 qui peuvent causer des retards sur les données basées sur les événements. Notre équipe travaille activement à la mise en œuvre d'une résolution. Veuillez vous attendre à des mises à jour supplémentaires dans les 30 prochaines minutes, et contacter Kustomer Support à [email protected] pour toute autre question ou mise à jour.

4. 26 juillet 2026 à 02:34 UTCmonitoring

   Kustomer a mis en place une mise à jour pour traiter un événement affectant les événements de plate-forme dans les orgs PROD1 qui a causé des retards sur les données basées sur les événements. Notre équipe surveille actuellement cette mise à jour pour s'assurer que le problème est entièrement résolu. S'il vous plaît attendre d'autres mises à jour dans les 30 prochaines minutes, et contacter Kustomer Support à [email protected] si vous avez des questions ou des préoccupations supplémentaires.

5. 26 juillet 2026 à 04:34 UTCresolved

   Kustomer a résolu un événement affectant les événements de plate-forme dans les orgs PROD1 qui a causé des retards sur les données basées sur les événements. Après un suivi attentif, notre équipe a déterminé que toutes les zones touchées sont maintenant entièrement restaurées. Veuillez contacter le support Kustomer à [email protected] si vous avez d'autres questions ou préoccupations.

6. 30 juillet 2026 à 16:17 UTCpostmortem

   Résumé Le 25 juillet 2026, certains clients ont connu une latence de plate-forme élevée affectant la messagerie, les mises à jour de conversation, le routage, la voix et d'autres flux de travail du service à la clientèle. Les clients peuvent avoir vu des messages rester dans un état d'envoi, des messages d'arrivée ou d'arrivée retardés, des réponses de page et d'API plus lentes, un acheminement ou une affectation retardés et des retards d'appels téléphoniques intermittents. Cet incident a été causé par une explosion exceptionnelle du traitement des données de base. Cela a provoqué une augmentation soudaine de la demande sur l'infrastructure des plateformes partagées. Une mise à l'échelle automatique a ajouté la capacité, mais elle n'a pas pu absorber l'éclatement assez rapidement pour empêcher la dégradation des flux de travail dépendants. Nous avons rétabli le service en augmentant la capacité disponible, en réduisant le taux de la charge de travail initiale et en traitant soigneusement le travail retardé tout en surveillant la santé de la plateforme. Impact * ** Effet client :** Latence de la plate-forme intermittente; messageries à l'arrivée et à l'arrivée retardées; conversation plus lente et mises à jour de l'API; routage ou affectation retardés; et retards d'appels téléphoniques intermittents * **Durée :** La dégradation visible du client a commencé à environ 17 h 22. Le service s'est initialement rétabli à environ 7:31 PM ET, mais la dégradation s'est reproduite plus tard. La performance de la plate-forme a été rétablie et l'incident a été résolu à 22 h 30 HNE. * ** Portée :** L'incident a touché un sous-ensemble de clients dans un seul environnement de production. Nous n'avons pas identifié la dégradation correspondante face au client dans d'autres environnements de production. Calendrier * **Environ 17h22 ET:** Le traitement des retards de latence et des messages a commencé à augmenter. * **6:51 PM ET:** L'équipe d'intervention a commencé à coordonner les enquêtes et le rétablissement. * **Environ 7h–7h23 ET:** Nous avons identifié les chemins de traitement touchés et nous avons commencé à récupérer soigneusement les travaux retardés à des taux contrôlés. * **7:31 ET:** Des capacités supplémentaires avaient été mises en ligne, les performances des clients s'étaient sensiblement améliorées et l'incident avait été résolu au départ tout en poursuivant la surveillance. * **8:28 ET:** L'incident a été rouvert après que de nouveaux rapports de dégradation intermittente aient été signalés. * **Environ 20h38 ET:** L'enquête a confirmé que la messagerie, le routage, le canal et les symptômes de la voix partageaient la même dépendance sous-jacente à la plate-forme. * **Environ 9h52 ET:** Nous avons réduit le taux de la charge de travail initiale pour protéger le trafic vers le client. * **10:08 ET:** La surveillance a confirmé que la charge de travail avait considérablement diminué et que la santé des plates-formes continuait de s'améliorer. * **10h30 ET:** Après une surveillance continue confirmée, l'incident a été résolu. * **Après résolution :** Le recouvrement des retards restants s'est poursuivi à des taux contrôlés sous surveillance. Cause profonde Une explosion de l'activité de traitement des données de base à grande échelle a généré plus de travaux en aval que l'infrastructure de plate-forme partagée ne pourrait absorber en toute sécurité sur une courte période. L'échelle automatique a répondu et a ajouté la capacité, mais la capacité a été ajoutée progressivement et n'est pas venue en ligne assez rapidement pour la taille et la vitesse de l'éclatement. Alors que la plate-forme était en train de rattraper son retard, l'augmentation de la latence des demandes et des délais ont affecté les flux de travail orientés vers le client qui dépendaient de la même infrastructure. Résolution Nous avons restauré les performances de la plateforme par: * Augmenter les capacités disponibles et améliorer le rythme auquel des capacités supplémentaires pourraient être ajoutées. * Réduire le taux de la charge de travail initiale. * Récupérer le travail retardé à des taux contrôlés pour éviter de créer un autre pic de trafic. * La surveillance continue après le retour des performances face au client aux niveaux prévus. Actions préventives Nous prenons les mesures suivantes pour réduire la probabilité et l'impact de la récidive : * Ajouter des limites plus strictes et des commandes de contre-pression pour les opérations de fond à volume élevé. * Améliorer la vitesse à laquelle les infrastructures partagées augmentent au cours d'un trafic soudain. * Améliorer l'isolement entre le traitement de fond et les flux de travail sensibles à la latence. * Étendre l'alerte pour une croissance rapide de l'arriéré, une pression sur les ressources et des modèles inhabituels de charge de travail. * Renforcer les procédures de récupération contrôlées pour les travaux retardés. * Étendre les essais de charge d'éclatement et de récupération des défaillances pour les services de plate-forme partagée. Situation actuelle La performance de la plate-forme est revenue aux niveaux prévus, et la charge de travail initiale est restée maîtrisée. Nous avons continué à surveiller la santé des services et le rétablissement du travail retardé après la résolution.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 25 juin 2026 à 22:24 UTCinvestigating

   Kustomer is aware of an event affecting PROD 1 that may affect the ability to send outbound messages for MessageBird. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support at [email protected] for any further questions or updates.

2. 25 juin 2026 à 22:49 UTCidentified

   Kustomer has identified the cause affecting PROD 1 that is impacting the ability to send outbound messages through MessageBird. Please expect another update within the next 30 minutes, as we reach a resolution. If you have any additional questions or concerns, please reply to this conversation or contact Kustomer Support at [email protected]. Thank you for your patience while we work to resolve this issue.

3. 25 juin 2026 à 23:05 UTCidentified

   Kustomer has identified and implemented a fix for the issue affecting PROD 1 that impacted the ability to send outbound messages through MessageBird. Our team is actively monitoring the platform to ensure the fix remains effective and that service has fully recovered. If you continue to experience issues sending outbound MessageBird messages, please contact Kustomer Support at [email protected]. We will provide another update once monitoring is complete or if there are any significant developments. Thank you for your patience.

4. 25 juin 2026 à 23:06 UTCmonitoring

   Kustomer has identified and implemented a fix for the issue affecting PROD 1 that impacted the ability to send outbound messages through MessageBird. Our team is actively monitoring the platform to ensure the fix remains effective and that service has fully recovered. If you continue to experience issues sending outbound MessageBird messages, please contact Kustomer Support at [email protected]. We will provide another update once monitoring is complete or if there are any significant developments. Thank you for your patience.

5. 25 juin 2026 à 23:30 UTCresolved

   Kustomer has resolved the issue affecting PROD 1 that impacted the ability to send outbound messages through MessageBird. Our team has verified that the fix has been successfully deployed and service has been restored. If you continue to experience issues sending outbound MessageBird messages, please contact Kustomer Support at [email protected] We apologize for the disruption and appreciate your patience while we worked to resolve the issue.

6. 6 août 2026 à 14:13 UTCpostmortem

   ## **Summary** On June 25, 2026, some customers were unable to send outbound WhatsApp replies from within Kustomer. The issue affected reply sending for a subset of WhatsApp channel configurations, which disrupted agent workflows and prevented some automated outbound messages from being sent through the same path. The issue was identified and resolved the same day. Service was fully restored, and the platform is operating normally. ## **Root cause** A change released earlier that day introduced stricter validation in the outbound WhatsApp reply flow. For a subset of supported channel configurations, valid sender values were incorrectly rejected before messages were sent. This caused reply attempts in those configurations to fail. The issue was limited to specific WhatsApp channel setups and did not affect all WhatsApp traffic equally. ## **Timeline** * **June 25, 2026, approximately 22:12 UTC** — Reports began coming in that outbound WhatsApp replies were failing for some customers. * **Shortly after detection** — Investigation confirmed the issue was tied to a recently released validation change in the outbound reply flow. * **June 26, 2026, approximately 01:07 UTC** — A fix was deployed and reply sending was restored. ## **Lessons and improvements** * Validation changes for messaging flows now require broader test coverage across supported channel configuration variants before release. * Additional safeguards are being added to reduce the risk of valid outbound requests being rejected. * Monitoring and regression checks around outbound messaging paths are being strengthened to detect similar issues more quickly.

1. 12 juin 2026 à 14:31 UTCinvestigating

   Kustomer is aware of an ongoing WhatsApp issue that may cause outbound messages to not be delivered to end users. While the issue appears to originate with WhatsApp, our team is actively monitoring the situation and working closely to assess the impact on the platform. We will continue to provide updates as more information becomes available. Please expect an additional update within the next 30 minutes. If you have any questions, please contact Kustomer Support at [email protected].

2. 12 juin 2026 à 14:46 UTCidentified

   Kustomer has identified an ongoing issue with WhatsApp that may cause outbound messages to not be delivered to end users. Our team is closely monitoring the situation and actively working to assess impact. Clients can refer to https://metastatus.com/whatsapp-business-api for the latest WhatsApp service status. Please expect further updates within the next 30 minutes, and reach out to Kustomer Support at [email protected] if you have additional questions or concerns.

3. 12 juin 2026 à 16:35 UTCidentified

   Kustomer continues to monitor the ongoing issue on Whatsapp that may cause outbound Whatsapp messages to not be delivered to end users. Clients can also refer to https://metastatus.com/whatsapp-business-api for the latest WhatsApp service status. Please expect further updates within the next 30 minutes, and reach out to Kustomer Support at [email protected] if you have additional questions or concerns

4. 12 juin 2026 à 19:29 UTCmonitoring

   Kustomer is aware of an event reported by one of our third party vendors affecting ALL PRODS that may cause Issues with WhatsApp messages not being delivered to end users. Our team is monitoring the incident, and working with the vendor where possible to resolve the issue. We are working on redriving previously unsent messages to ensure all messages are sent successfully. Please expect further updates within the next 3 hours, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

5. 12 juin 2026 à 21:38 UTCresolved

   WhatsApp has confirmed that all services are fully recovered. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

6. 22 juin 2026 à 14:57 UTCpostmortem

   ## Summary On June 12, 2026, customers using WhatsApp through Kustomer experienced a service event that prevented some outbound messages from being delivered to end users. During the event, messages could appear as sent in Kustomer before final delivery was confirmed by WhatsApp. Service recovered the same day, and affected messages from the incident window were successfully reprocessed. ## Root cause This event was caused by a disruption in WhatsApp Business Platform services operated by Meta. While that disruption was active, Kustomer was unable to complete delivery for some outbound WhatsApp messages and queued affected messages for retry after the upstream service recovered. ## Timeline * **10:14 AM EDT** — Customer reports led to investigation of outbound messaging behavior. * **10:34 AM EDT** — Meta reported high disruptions affecting WhatsApp Business Platform services. * **1:45 PM EDT** — Reprocessing of queued messages began as upstream recovery progressed. * **2:32 PM EDT** — Meta reported recovery for the remaining affected WhatsApp services. * **4:07 PM EDT** — Active message sending was healthy again. * **4:34 PM EDT** — Messages from the incident window had been successfully reprocessed. ## Lessons and improvements * We are improving monitoring and alerting for queued WhatsApp messages so degraded delivery is identified earlier. * We are documenting a safer reprocessing procedure for queued WhatsApp traffic to reduce the chance of retry-related rate limiting during recovery. * We are reviewing backlog-handling procedures to make recovery more predictable when an upstream provider disruption occurs. At this time, system health for WhatsApp message delivery through Kustomer is stable.

1. 9 juin 2026 à 14:00 UTCinvestigating

   Kustomer is aware of an event affecting Chat and other channels that may cause delayed message delivery and slower conversation load times. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes and please reach out to Kustomer Support at [email protected] for any further questions or updates.

2. 9 juin 2026 à 14:11 UTCmonitoring

   Kustomer has identified the cause of the event affecting Chat and other channels that resulted in delayed message delivery and slower conversation load times. The situation has stabilized and our team is continuing to monitor to ensure full resolution. Please reach out to Kustomer Support at [email protected] if you have additional questions or concerns.

3. 9 juin 2026 à 15:18 UTCresolved

   Kustomer has resolved an event affecting Chat and other channels that caused delayed message delivery and slower conversation load times. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer Support at [email protected] if you have additional questions or concerns.

4. 11 juin 2026 à 21:18 UTCpostmortem

   **Summary** On June 9, 2026, customers experienced delays in chat message delivery and related real-time updates for a portion of the morning. The issue was caused by a third-party service event affecting the infrastructure used to propagate real-time messaging updates. Service recovered the same morning, and current system health is stable. **Root cause** A third-party real-time messaging provider experienced elevated latency and intermittent publish failures in one of its regions. That disruption delayed delivery acknowledgements and other real-time updates in Kustomer. Messages continued to be stored successfully, but some updates were not reflected immediately in the client until the external service recovered or the client refreshed. **Timeline** * **9:05 AM EDT** — Customer impact began, including delayed chat message delivery and stale real-time updates. * **9:45 AM EDT** — The third-party provider reported active latency affecting its service. * **9:48 AM EDT** — The provider reported mitigation and recovery. * **Shortly after recovery** — Real-time behavior returned to normal and monitoring confirmed stability. **Lesson/improvements** * We added additional monitoring tied to the third-party provider's public service health signals so similar service events can be identified faster. * We are improving alerting around real-time messaging errors to reduce time to diagnosis. * We are continuing to review operational signals to better distinguish external service issues from internal platform issues.

1. 2 juin 2026 à 14:47 UTCinvestigating

   Kustomer is aware of an event affecting chats, emails, and routing that may cause latency with sending, receiving, and routing messages. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support at [email protected] for any further questions or updates.

2. 2 juin 2026 à 15:19 UTCidentified

   Kustomer has identified an event affecting chats, emails, and routing that may cause latency with sending, receiving, and routing messages. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

3. 2 juin 2026 à 15:27 UTCmonitoring

   Kustomer has implemented an update to address an event affecting chat, email, and routing that caused latency in sending and delivering messages. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

4. 2 juin 2026 à 15:53 UTCresolved

   Kustomer has resolved an event affecting Prod 1 that caused chat, email, and routing latency. To resolve this issue, our team reverted an underlying infrastructure change as a precaution, which helped stabilize the service. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

5. 11 juin 2026 à 21:17 UTCpostmortem

   **Summary** On June 2, 2026, customers in our prod1 environment experienced elevated latency affecting chat creation, email sending, and conversation routing. The event caused delayed processing for a subset of customer interactions during the incident window. Service performance recovered the same day after mitigation steps were applied, and the environment is currently operating normally. **Impact** * Scope: prod1 only * Customer effect: delayed chat creation, delayed email sends, and slower conversation routing * Duration: customer-visible impact began in the morning ET on June 2 and materially improved after mitigation later that afternoon * Other environments: prod2 and prod4 were not impacted by the customer-facing degradation **Timeline** * Early June 2: We detected elevated processing latency in services supporting chat, email, and routing in prod1. * Midday to afternoon ET: Customer reports confirmed delayed system behavior in prod1. * Afternoon ET: We increased service capacity and adjusted resource limits to reduce backlog and restore throughput. * Later that day: We completed an infrastructure rollback on affected worker hosts and confirmed stable recovery. * June 3: Monitoring confirmed the environment remained healthy. **Root cause** The incident was caused by infrastructure-level resource exhaustion on a set of worker hosts in prod1. That reduced the availability of a metadata-dependent service and created message backlog, which in turn increased latency for customer-facing workflows such as chat creation, email sending, and routing. The issue was isolated to prod1. **Resolution** We restored service by increasing available capacity, raising resource limits for the affected service, and rolling impacted worker infrastructure back to a stable configuration. After those changes were applied, backlog cleared and latency returned to expected levels. Current system health is stable. **Preventative actions** * Strengthen host-level capacity and disk safeguards before future infrastructure rollouts * Add earlier alerting for infrastructure resource pressure to reduce time to detection * Expand validation for production-scale logging and resource usage prior to promotion * Continue tuning service capacity thresholds and recovery procedures for metadata-dependent workloads

1. 26 mai 2026 à 22:14 UTCmonitoring

   Kustomer has implemented an update to address an event affecting WhatsApp that caused messaging failures. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

2. 27 mai 2026 à 00:21 UTCresolved

   This incident has been resolved. Our teams have confirmed recovery and platform stability following mitigation efforts. We will be reaching out independently to affected orgs to provide additional context and follow-up as needed. Thank you for your patience while we worked through this issue.

3. 11 juin 2026 à 21:19 UTCpostmortem

   ## Summary On May 26, 2026, some customers experienced failures when sending WhatsApp messages from existing conversations. The issue affected outbound message delivery for a subset of WhatsApp configurations. Service was restored after the responsible change was rolled back, and the issue is now resolved. ## Impact During the incident window, outbound WhatsApp messages failed for some existing conversations. Newly created conversations were less consistently affected, and impact varied by account configuration. Customers may have seen message-send failures or provider errors while attempting to send WhatsApp messages. ## Timeline All times EDT. * **4:05 PM:** The incident window is believed to have begun after a recent WhatsApp-related change. * **5:54 PM:** Active investigation began. * **5:56 PM:** The team identified a likely connection to recent WhatsApp sender-selection behavior and started a rollback. * **6:05 PM:** Rollback completed. * **6:17 PM – 7:47 PM:** The team validated recovery across affected examples and narrowed the underlying cause. * **8:21 PM:** The incident was declared resolved. ## Root cause The incident was caused by an issue in WhatsApp phone-number lookup and sender selection. A recent change expanded support for multiple valid phone-number formats in certain countries. In some cases, that allowed the system to resolve the wrong sender configuration for an existing conversation. When that happened, outbound sends could target an invalid or unavailable sender identity, causing WhatsApp message delivery to fail. ## Resolution We mitigated the incident by rolling back the relevant WhatsApp change. After the rollback, we verified recovery against affected examples and confirmed that the incident was resolved. ## Preventative actions * Move WhatsApp sender resolution toward more stable identifier-based matching rather than relying on ambiguous phone-number formatting. * Expand regression coverage for country-specific phone-number formatting edge cases. * Improve monitoring and alerting for message delivery failures and queue growth. * Improve testing workflows for WhatsApp changes before production rollout.

1. 14 mai 2026 à 16:24 UTCinvestigating

   Kustomer is aware of an event affecting Chats that may cause messages to fail and assistants to not follow the configured flow. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support for any further questions or updates.

2. 14 mai 2026 à 16:48 UTCmonitoring

   Kustomer has implemented an update to address an event affecting Chats on Prod 1 that caused messages to fail and assistants to not follow the configured flow. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support if you have additional questions or concerns.

3. 14 mai 2026 à 17:23 UTCresolved

   Kustomer has resolved an event affecting Chat on Prod 1 that caused messages to fail and assistants to not follow the configured flow. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support if you have additional questions or concerns.

4. 4 août 2026 à 21:09 UTCpostmortem

   ## **Summary** Between May 13 and May 14, 2026, Kustomer Chat experienced a service event that affected chat availability and performance for a subset of customers. During this period, some customers may have seen intermittent failures, elevated error rates, or degraded behavior in chat-related settings and runtime flows. The event was mitigated through service rollback, additional capacity, and targeted configuration changes. Service health returned to normal after these actions were completed. ## **Root cause** The event was caused by a combination of reduced service capacity during a deployment rollback and higher-than-expected traffic through chat-related request paths. Under those conditions, the affected chat service became unstable and restarted repeatedly, which reduced available capacity further and increased customer-facing errors. Our investigation also identified specific high-volume request patterns that increased memory pressure during the event. We addressed those patterns with caching, traffic protections, and capacity changes. ## **Timeline** * May 13, 2026, early afternoon ET: We detected elevated instability in the chat service and began incident response. * May 13, 2026, afternoon ET: We rolled back affected changes, increased infrastructure capacity, and stabilized dependent services. * May 13, 2026, evening ET: We continued monitoring after initial mitigation and investigated recurring memory pressure. * May 14, 2026: We deployed additional mitigations, including higher minimum service capacity and request-path protections. * Following the mitigation deployments, service health returned to normal and remained stable. ## **Lessons and improvements** We completed several improvements to reduce the likelihood of recurrence: * Increased minimum service capacity to provide more headroom during deployments and recovery. * Added caching for high-volume chat settings requests. * Hardened URL processing behavior with stricter filtering, failure caching, and concurrency limits. * Added improved memory telemetry to speed up detection and diagnosis of similar issues. * Continued follow-up work on deployment recovery procedures and service safeguards for cross-service rollbacks. ## **Current status** The mitigations above have been deployed, and the affected chat service is operating normally.

1. 1 mai 2026 à 13:39 UTCidentified

   Kustomer is aware of an event affecting Gmail Connectivity and Send & Receive that may cause emails to not route into your Kustomer Platform and impact your ability to send messages on conversations. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Chat for any further questions or updates.

2. 1 mai 2026 à 14:02 UTCmonitoring

   Kustomer has released a fix for the event affecting Gmail Connectivity and Send & Receive functionality that was causing emails to not forward as expected into your Kustomer Platform and impacted sending functionality on conversations. Our team is currently monitoring the released fix to ensure the issue is resolved. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Chat for any further questions or updates.

3. 1 mai 2026 à 14:17 UTCresolved

   Kustomer has resolved an event affecting Gmail Connectivity and Send & Receive functionality in Prod 1 and Prod 2. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

4. 5 mai 2026 à 14:06 UTCpostmortem

   ## Summary On May 1, 2026, customers using the Gmail integration experienced a service event that caused Gmail connections to disappear and the email channel to stop functioning. The issue affected customers across different regions, more specifically: * EU-based clients, from 2:40 AM ET. * US-based clients, from 5 AM ET. The issue was fully resolved by 9:20 AM ET. No customer data was lost during this event. Messages that were delayed during the incident were fully recovered once service was restored. Current system health is stable. ## Root cause A configuration issue in the infrastructure used by the Gmail integration prevented replacement service tasks from starting correctly during routine task rotation. As running capacity declined over several hours, the Gmail integration became unavailable. ## Timeline | Time \(ET\) | Event | | --- | --- | | May 1, ~12:30 AM | Service task replacement failures began in production. | | May 1, ~2:40 AM | Engineering was alerted after service capacity dropped to zero in one production environment. | | May 1, 2:40–9:20 AM | Teams investigated the failure, identified the configuration problem, prepared a fix, and deployed it. | | May 1, 9:20 AM | Fix deployed and service restored. | ## Lessons and improvements * We are auditing related infrastructure configurations to identify and correct similar patterns in other services. * We are standardizing how service roles are managed so this class of configuration issue is less likely to recur. * We are improving alerting so teams are notified earlier when running service capacity drops below expected levels, before a full service interruption occurs. * We are adding additional checks to catch configuration drift and invalid service role references earlier in the deployment lifecycle.

1. 24 avril 2026 à 21:02 UTCmonitoring

   Kustomer has identified an event affecting Prod1 that may cause internal API errors and latency. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

2. 24 avril 2026 à 21:31 UTCmonitoring

   Kustomer has implemented an update to address an event affecting Prod1 that caused internal API errors and latency. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

3. 24 avril 2026 à 21:47 UTCresolved

   Kustomer has resolved an event affecting Prod1 that caused API errors and latency. To resolve this issue, our team has released an update. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

4. 30 avril 2026 à 18:21 UTCpostmortem

   ## Summary On April 24, 2026, customers in our prod1 environment experienced a service event that caused elevated errors and latency in messaging-related workflows. The broad cross-customer impact was limited to approximately 41 minutes, from 3:26 PM ET to 4:07 PM ET. During that window, some customers saw failed or delayed messaging operations. The immediate platform impact was resolved the same day, and overall system health returned to normal. We then completed follow-up mitigation to stop the underlying event source and reduce the risk of recurrence. ## Impact * Customers in prod1 experienced elevated API errors and latency in messaging-related workflows. * The broad cross-customer impact lasted about 41 minutes. * A subset of messaging workflows failed or were delayed during that period. ## Timeline * **~3:25 PM ET** — A newly enabled automation began processing a large backlog of historical conversations for one tenant. * **3:26 PM ET** — Elevated errors and latency began affecting shared messaging workflows in prod1. * **4:01 PM ET** — We published a status update for the production issue. * **4:07 PM ET** — Broad cross-customer impact ended as the affected services stabilized. * **~5:17 PM ET** — We disabled the triggering automation configuration for the affected tenant. * **~5:23 PM ET** — The remaining retry activity stopped. ## Root cause The event was triggered when a newly enabled automation for one tenant processed a much larger set of eligible conversations than intended. That sudden volume overloaded a shared downstream service and caused elevated errors and timeouts in dependent workflows. The incident was amplified by missing safeguards in how this automation handled backlog volume and retries. In particular, the system did not sufficiently limit the number of conversations processed at once or prevent the same failed work from being retried too aggressively. ## Resolution We restored platform stability during the incident by allowing the affected services to recover under increased capacity, then disabled the triggering automation configuration and cleared the remaining retry backlog. System health is currently normal. ## Preventative actions We are treating the following preventative actions as a priority bug effort. These actions are expected to be resolved by the end of May in accordance with our SLOs: * Prevent newly enabled automation settings from processing large historical backlogs unintentionally. * Add stronger batch limits and tenant-level throttling for this workflow. * Reduce retry amplification by improving how failed work is tracked and re-queued. * Improve error handling so rate-limit conditions are classified correctly and handled with the right retry behavior.

1. 14 avril 2026 à 14:44 UTCinvestigating

   Kustomer is aware of an event affecting Knowledge bases and forms that may be displaying a 500 error code and preventing access to these urls. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via kustomer.com for any further questions or updates.

2. 14 avril 2026 à 15:01 UTCresolved

   Kustomer has resolved an event affecting Knowledge Bases and forms that caused a 500 error and preventing access to these pages. To resolve this issue, our team has performed a roll back in this area. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer Support via kustomer.com if you have additional questions or concerns.

3. 24 avril 2026 à 17:14 UTCpostmortem

   ## **Summary** ‌ On April 14, 2026, customers experienced errors accessing the Kustomer Knowledge Base, with all KB pages returning 500 errors. The issue was caused by a dependency upgrade in a recent deployment that introduced a TLS certificate mismatch in internal service communication. Customer impact began at 9:51 AM ET when the deployment reached the first production environment, and was fully resolved by 10:38 AM ET — a ~47 minute impact window. Engineers identified the root cause and completed a full rollback across all production environments within 12 minutes of the initial alert. ‌ ## **Root Cause** ‌ A recent deployment to the KB service included an upgrade to an internal library that contained a known issue with TLS hostname verification. This caused internal service-to-service requests to fail, resulting in 500 errors for all KB requests. The affected library version had previously been identified as problematic in a staging environment, but the fix had not been fully applied across all services before this deployment reached production. ## **Timeline** ‌ **Apr 14, 2026** ‌ 9:51 AM ET — Deployment reached the first production environment; customers began experiencing 500 errors when accessing the Knowledge Base ‌ 10:26 AM ET — Automated alerting fired; incident response began ‌ 10:31 AM ET — Engineers identified a recent deployment as the likely cause and began investigating rollback options ‌ 10:35 AM ET — Root cause confirmed as a problematic internal library version; rollback initiated across all production environments ‌ 10:37 AM ET — Rollback completed on prod1; KB restored for affected customers ‌ 10:38–10:39 AM ET — Rollback completed across remaining production environments ‌ 10:45 AM ET — Full KB functionality confirmed restored for all customers ‌ 12:09 PM ET — Corrected fix deployed to the Knowledge Base service; remediation completed across all other affected services ‌ ## **Lessons/Improvements** * Implementing stricter controls to prevent pre-release or beta library versions from being deployed to production * Improving the process for tracking and completing cross-service remediation work when an issue is identified in one service, to ensure all affected services are addressed * Enhancing our pre-production validation process to improve detection of this class of issue before it reaches production environments

1. 19 mars 2026 à 14:42 UTCinvestigating

   Kustomer is aware of an event affecting AI for Customers and Reps that have resulted in them not responding. Our team is currently working to identify the cause for the issue in order to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via kustomer.com for any further questions or updates.

2. 19 mars 2026 à 15:44 UTCidentified

   Kustomer has identified an event in AIC/AIR that may cause unresponsive functionality. Our team is still continuing to work on implementing a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Kustomer.com for any further questions or updates.

3. 19 mars 2026 à 16:16 UTCidentified

   Kustomer has identified an event that is causing unresponsiveness in AIC/AIR. Our team is working directly with our database provider in order to implement a resolution for this event. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Kustomer.com for any further questions or updates.

4. 19 mars 2026 à 16:58 UTCidentified

   Kustomer has identified an event affecting PROD 1 that may cause failing Kustomer AI-Agent features. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

5. 19 mars 2026 à 17:34 UTCidentified

   Kustomer has identified an event affecting PROD 1 that may result in failures with Kustomer AI Agent features. Our team is still actively working to implement a resolution. Please expect further updates within the next 30 minutes, and feel free to reach out to Kustomer Support at [email protected] if you have any additional questions or concerns.

6. 19 mars 2026 à 17:52 UTCmonitoring

   Kustomer has implemented an update to address an event affecting Prod 1 that caused failures with Kustomer's AI features. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

7. 19 mars 2026 à 18:29 UTCresolved

   Kustomer has resolved an event affecting Prod 1 that caused failures with Kustomer's AI features. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

8. 27 mars 2026 à 15:38 UTCpostmortem

   ## Summary On March 19, 2026, some Kustomer AI features were unavailable for customers hosted in one production environment \(Prod1\). The disruption affected AI-powered responses and related AI workflows for 41 customers in our Prod 1 instance. Other production environments were not affected. Service was fully restored within 4 hours, and the platform is operating normally. ## Root cause The incident was caused by a production database index change that was introduced during a service deployment. That change caused database performance to degrade significantly for a high-traffic dataset used by our AI services. As performance deteriorated, dependent services were unable to start or process requests normally, which led to broad disruption across affected AI features. Recovery was prolonged by duplicate records created during the incident window, which complicated restoration of normal database constraints and required additional remediation before services could be brought back cleanly. ## Timeline All times below are in EDT \(UTC-4\) on March 19, 2026. * **~10:27 AM** — A production deployment introduced a database index change that degraded performance for AI-related services. * **~10:37 AM** — Customer impact was confirmed and incident response began. * **~10:42 AM** — We published a public status update and began active mitigation. * **~11:37 AM** — We identified the primary cause and focused recovery on database stability and service restoration. * **~12:10 PM** — After scaling database capacity and reducing load, service recovery began. * **~1:43 PM** — AI services began recovering and queued work started draining. * **~2:19 PM** — Backlogged work had been processed and core functionality was restored. * **Later that afternoon** — Follow-up cleanup was completed and normal safeguards were re-applied. ## Lessons and improvements We take this incident seriously and are making changes to reduce the likelihood of recurrence. * We are tightening how database schema and index changes are deployed in production, including stronger pre-deployment validation and safer rollout sequencing. * We are removing index-management behavior from service startup paths where it can create unnecessary risk during deployment. * We are improving monitoring and alerting so service health failures and database stress are detected earlier. * We are refining incident response procedures, access readiness, and operational runbooks to speed mitigation during future incidents. * We are reviewing capacity and resilience safeguards for this part of the platform to better handle abnormal database load.

1. 20 février 2026 à 22:01 UTCmonitoring

   Kustomer has implemented an update to address an event affecting inbound Voice calls in PROD 1 & 2 that caused inbound calls to drop before getting answered by an agent. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at Email or Chat if you have additional questions or concerns.

2. 20 février 2026 à 22:21 UTCinvestigating

   Kustomer is aware of an event affecting Voice conversations that may cause inbound calls to not be accepted properly in the system. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Chat or Email for any further questions or updates.

3. 20 février 2026 à 22:53 UTCinvestigating

   Kustomer is continuing to investigate an event impacting Voice conversations that may cause inbound calls to not be accepted properly within the system. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide another update within the next 30 minutes or sooner as more information becomes available. If you have any urgent questions or need assistance, please contact Kustomer Support via Chat or Email.

4. 20 février 2026 à 23:08 UTCidentified

   Kustomer is aware of an issue affecting inbound call acceptance in our PROD1 environment where inbound calls were not properly being accepted in the system. Our team has identified the cause of the issue within the code and are actively working on a fix to restore system behavior back to normal. Please expect additional updates within the next 30 minutes, and reach out to Kustomer Support at Email or Chat Channels if you have additional questions or concerns.

5. 20 février 2026 à 23:33 UTCmonitoring

   Kustomer has implemented an update to address an event affecting Voice conversations in PROD 1 that caused inbound calls to be dropped when trying to accept calls. Our team is currently monitoring this update to ensure the issue is fully resolved. If your agents are continuing to experience this issue please have them refresh their browser to apply the fix. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at Email or Channel if you have additional questions or concerns.

6. 21 février 2026 à 00:01 UTCresolved

   Kustomer has resolved an incident affecting Voice in PROD 1 that caused inbound calls to drop after being initially accepted. To remediate the issue, our team rolled back a recent code change to a previously stable version, which successfully resolved the error. After thorough monitoring, we have confirmed that all impacted services are fully restored. If any agents continue to experience issues, please have them refresh their browser to ensure the fix is applied. If you have any additional questions or concerns, please reach out to Kustomer Support via Email or Chat.

7. 2 mars 2026 à 16:53 UTCpostmortem

   ## Summary On February 20, 2026, a frontend change intended to improve performance unintentionally disrupted call setup in our Voice experience. As a result, agents could see an incoming call and click accept/decline, but audio would not connect and calls would time out. We rolled back the change and then deployed an additional fix to make startup more reliable and prevent recurrence. ## What happened When the Voice widget starts, it needs to receive a small set of configuration settings \(including feature-flag values\) from the main app before it can route and connect calls correctly. A pre-existing timing edge case meant that, in some cases, that initial configuration could be sent before the Voice widget was fully ready to receive it. Historically, the widget would receive the same configuration again shortly afterward, which masked a state issue. The performance change reduced those repeated configuration sends \(which is normally a good optimization\). But because the widget sometimes missed the first configuration during startup, it could start with incomplete settings and fall back to legacy call-routing behavior. In that fallback mode, calls could appear answerable in the UI but fail to fully connect audio. ## Root cause A performance optimization changed how/when configuration settings were delivered during Voice widget startup. Combined with a pre-existing startup timing edge case, some sessions did not receive the required configuration in time and fell back to legacy call-routing behavior, preventing audio from being bridged correctly. ## Timeline * 3:04 PM ET: Frontend change deployed * 4:38 PM ET: Reports received that calls could not be answered \(accept/decline visible, no audio\) * 4:44 PM ET: Initial rollback attempt of an unrelated change did not resolve the issue * 4:50 PM ET: Incident communication initiated via status page * 6:24 PM ET: Frontend change reverted/rolled back * 8:47 PM ET: Reports continued for some agents * 10:31 PM ET: Identified that affected sessions could persist without a browser refresh due to cached UI state; refresh/new session restored correct behavior * Saturday 9:00 AM ET: Confirmed reports that calls were successfully connecting ## Lessons / improvements * Harden Voice widget startup so required configuration can’t be missed during initialization. * Add automated smoke/E2E coverage for core Voice call flows \(answer/connect audio\) to detect regressions before production. * Improve safeguards and monitoring around call-connect failures to reduce time-to-detect and time-to-mitigate.

1. 12 février 2026 à 15:11 UTCmonitoring

   Kustomer is aware of an event reported by one of our third party vendors affecting Prod1 that may cause AIC and AIR failures within the platform. Our team is monitoring the incident, and working with the vendor where possible to resolve the issue. OpenAI's status page for this incident can be found here: https://status.openai.com/incidents/01KH94NGSXNH9H4WBPXB3RFZWX Please expect further updates within the next 3 hours, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

2. 12 février 2026 à 18:07 UTCresolved

   OpenAI has confirmed that all services are fully recovered. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

1. 27 janvier 2026 à 19:31 UTCinvestigating

   Kustomer is aware of an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

2. 27 janvier 2026 à 19:58 UTCinvestigating

   Kustomer is aware of an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is continuing to work to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

3. 27 janvier 2026 à 20:29 UTCinvestigating

   Kustomer is aware of an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is continuing investigate the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

4. 27 janvier 2026 à 21:03 UTCinvestigating

   Kustomer is aware of an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is continuing to work to investigate the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

5. 27 janvier 2026 à 21:32 UTCidentified

   Kustomer has identified an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is currently working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

6. 27 janvier 2026 à 21:51 UTCidentified

   Kustomer has identified an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is continuing to work to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

7. 27 janvier 2026 à 22:23 UTCidentified

   Kustomer has identified an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team continues to work to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

8. 27 janvier 2026 à 23:01 UTCidentified

   Kustomer has identified an event affecting Satisfaction surveys that may cause surveys to not be sent, once conversations are marked done within the platform. Our team is working to implement a resolution. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

9. 28 janvier 2026 à 00:16 UTCmonitoring

   The team has identified the problem and mitigations have been applied. Jobs are gradually catching up and the team continues to monitor.

10. 28 janvier 2026 à 22:05 UTCinvestigating

    Kustomer has resolved an event affecting Satisfaction Surveys that may cause Surveys to not be sent. To resolve this issue, our team has released an update. After careful monitoring, our team has determined that our systems are now fully restored, but our engineering team is still redriving surveys that did not originally send. During this redriving period lingering issues may still be present. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

11. 28 janvier 2026 à 23:10 UTCresolved

    Kustomer has resolved an event affecting Satisfaction Surveys that may cause Surveys to not be sent. To resolve this issue, our team has released an update. After careful monitoring, our team has determined that our systems are now fully restored, but our engineering team is still redriving surveys that did not originally send. During this redriving period lingering issues may still be present. Please reach out to Kustomer support at [email protected] if you have additional questions or concerns.

12. 4 février 2026 à 21:50 UTCpostmortem

    # Post Mortem: Chat, Voice Routing, CSAT, Oauth, Scheduled Send Issues # **Summary** On January 22, 2024, customers experienced chat and voice conversations failing to route to agents due to a recent change in the assistant service. This triggered cascading failures across multiple backend services, degrading platform performance for several orgs.  On January 27th, a subsequent incident occurred due to our scheduled jobs queue being flooded by assistant service jobs. This caused some CSAT Surveys to not send, Oauth connections to fail to refresh, and scheduled messages to not send. ‌ **Root Cause** A recent change to the assistant backend service increased the maximum workflow loops before transferring a conversation to an available agent. This allowed a single rate-limited WhatsApp conversation to become stuck in an infinite retry loop while attempting to transfer. The transfer requests themselves were also rate-limited, overwhelming shared infrastructure \(e.g. “job” engine which is shared by CSAT\) and causing service degradation across multiple orgs. # **Timeline** **Jan 22, 2026** 1:33 PM – Users began experiencing errors with chat and voice conversations failing to route to agents 1:44 PM – Engineers identified the problematic deployment and initiated rollback across all environments 1:54 PM – Rollback completed across all environments; on-call engineers continued monitoring system status 2:02 PM – Full assistant functionality restored for all customers 6:07 PM - Customers begin to report Oauth connections that failed to refresh ‌ **Jan 24, 2026** 6:24 PM - Customers begin to report that scheduled messages were not sending ‌ **Jan 27, 2026** 1:00 PM - Customers begin to report that CSAT surveys are not being sent 4:00 PM - Identified cause of CSAT scheduled job processing delays 6:00 PM - Started a script to manually increase processing throughput of scheduled jobs ‌ **Jan 28, 2026** 12:08 PM - Deployed code change to programmatically increase processing throughput of scheduled jobs 3:49 PM - Backlog of all delayed jobs processed and system restored ‌ **Lessons/Improvements** * Implementing new alerts to detect when scheduled job processing falls behind, enabling faster identification of similar issues * Improving alert prioritization to reduce noise and ensure critical alerts are acted upon immediately * Enhancing monitoring for downstream service dependencies * Evaluating queue architecture changes to prevent a single conversation from impacting other customers \("noisy neighbor" isolation\) * Investigating improvements to make our job scheduling service more resilient to backlogs * Creating documentation of all services that depend on scheduled jobs to better understand incident ripple effects

1. 22 janvier 2026 à 18:44 UTCinvestigating

   Kustomer is aware of an event affecting Chat and Voice conversations that may cause the conversation to not be routed to an available agent. Our team is currently working to identify the cause of this issue in an effort to implement a resolution. Please expect additional updates within the next 30 minutes, please reach out to Kustomer Support via Email or Chat for any further questions or updates.

2. 22 janvier 2026 à 19:02 UTCmonitoring

   Kustomer has implemented an update to address an event affecting Chats and Voice calls in PROD 1 & 2 that caused conversations to not be routed to available agents. Our team is currently monitoring this update to ensure the issue is fully resolved. Please expect further updates within the next 30 minutes, and reach out to Kustomer support at Chat and Email if you have additional questions or concerns.

3. 22 janvier 2026 à 19:30 UTCresolved

   Kustomer has resolved an event affecting Conversational Assistants in PROD1 and 2 that caused conversations to not route to available agents. To resolve this issue, our team has completed a rollback our codebase to address the failures in the assistants. After careful monitoring, our team has determined that all affected areas are now fully restored. Please reach out to Kustomer support at Chat or Email if you have additional questions or concerns.

4. 4 février 2026 à 21:52 UTCpostmortem

   # Post Mortem: Chat, Voice Routing, CSAT, Oauth, Scheduled Send Issues # **Summary** On January 22, 2024, customers experienced chat and voice conversations failing to route to agents due to a recent change in the assistant service. This triggered cascading failures across multiple backend services, degrading platform performance for several orgs.  On January 27th, a subsequent incident occurred due to our scheduled jobs queue being flooded by assistant service jobs. This caused some CSAT Surveys to not send, Oauth connections to fail to refresh, and scheduled messages to not send. ‌ **Root Cause** A recent change to the assistant backend service increased the maximum workflow loops before transferring a conversation to an available agent. This allowed a single rate-limited WhatsApp conversation to become stuck in an infinite retry loop while attempting to transfer. The transfer requests themselves were also rate-limited, overwhelming shared infrastructure \(e.g. “job” engine which is shared by CSAT\) and causing service degradation across multiple orgs. # **Timeline** **Jan 22, 2026** 1:33 PM – Users began experiencing errors with chat and voice conversations failing to route to agents 1:44 PM – Engineers identified the problematic deployment and initiated rollback across all environments 1:54 PM – Rollback completed across all environments; on-call engineers continued monitoring system status 2:02 PM – Full assistant functionality restored for all customers 6:07 PM - Customers begin to report Oauth connections that failed to refresh ‌ **Jan 24, 2026** 6:24 PM - Customers begin to report that scheduled messages were not sending ‌ **Jan 27, 2026** 1:00 PM - Customers begin to report that CSAT surveys are not being sent 4:00 PM - Identified cause of CSAT scheduled job processing delays 6:00 PM - Started a script to manually increase processing throughput of scheduled jobs ‌ **Jan 28, 2026** 12:08 PM - Deployed code change to programmatically increase processing throughput of scheduled jobs 3:49 PM - Backlog of all delayed jobs processed and system restored ‌ **Lessons/Improvements** * Implementing new alerts to detect when scheduled job processing falls behind, enabling faster identification of similar issues * Improving alert prioritization to reduce noise and ensure critical alerts are acted upon immediately * Enhancing monitoring for downstream service dependencies * Evaluating queue architecture changes to prevent a single conversation from impacting other customers \("noisy neighbor" isolation\) * Investigating improvements to make our job scheduling service more resilient to backlogs * Creating documentation of all services that depend on scheduled jobs to better understand incident ripple effects

1. 10 décembre 2025 à 03:38 UTCidentified

   Kustomer is aware of an event affecting outbound webhook delivery in our Prod2 environment. Customers may experience failures due to 404 and 503 errors when the platform attempts to send outbound webhooks. Our team is actively investigating the cause and working toward a resolution. Please expect additional updates within the next 30 minutes, and reach out to Kustomer Support at [email protected] if you have additional questions or concerns.

2. 10 décembre 2025 à 03:55 UTCidentified

   We are continuing to work on a fix for this issue.

3. 10 décembre 2025 à 04:22 UTCmonitoring

   Kustomer has implemented a fix for the event impacting outbound webhooks in the Prod2 and Prod4 environments. We are backporting this fix across environments, and our team is monitoring to ensure service stability and continued recovery. Please expect additional updates within the next 30 minutes, and reach out to Kustomer support at [email protected] if you have additional questions or concerns.

4. 10 décembre 2025 à 04:52 UTCresolved

   Kustomer has resolved the event that impacted outbound webhooks in the Prod2 and Prod4 environments. The backported fix has been fully deployed, and webhook delivery is functioning as expected across all affected environments. Our team has verified stability, and no further impact is anticipated. If you have additional questions or concerns, please reach out to Kustomer support at [email protected]

5. 12 février 2026 à 16:57 UTCpostmortem

   ### **Summary** On December 9, 2025, Kustomer experienced an interruption to outbound webhook delivery affecting customers in our **prod-2 \(EU\)** and **prod-4 \(IN\)** production regions. During this time, some outbound webhook requests were unable to reach customer endpoints, resulting in delivery failures and error responses. The disruption occurred during a routine platform update related to our deployment systems. An underlying inconsistency from a previous infrastructure change caused a required backend service to become temporarily unavailable while updates were in progress. As a result, webhook endpoints could not accept or process delivery attempts for a limited period. Engineering teams identified the issue quickly and restored full service shortly thereafter. Once the affected systems were brought back online, normal webhook delivery resumed and any queued events were successfully processed. There was no permanent data loss, and webhook functionality returned to normal operation across all impacted regions. ### **Impact** * **Duration:** Approximately 1 hour and 40 minutes * **Scope:** Production regions prod-2 and prod-4 * **Customer Impact:** * Outbound webhook delivery failures during the incident window * Webhook requests may have returned HTTP 503 or 404 responses * Webhook events were delayed but not lost ### **Next Steps** While safeguards already exist to protect core platform services, we are implementing additional improvements to reduce the likelihood of similar disruptions in the future. These include strengthening validation during platform updates, improving detection of incomplete infrastructure changes, and enhancing internal visibility when critical services are modified.