Historique des pannes de Kajabi

1. 17 août 2026 à 18:02 UTCmonitoring

   Nous avons reçu des rapports d'erreurs lors de l'enregistrement des changements dans plusieurs zones de Kajabi. Une correction a été déployée pour les erreurs affectant l'épargne dans plusieurs zones de Kajabi, et l'épargne devrait maintenant fonctionner comme prévu. Notre équipe surveille activement pour confirmer la résolution complète. Les héros qui continuent à éprouver des problèmes devraient essayer de rafraîchir leur navigateur, et peuvent contacter notre équipe de support si le problème persiste.

2. 17 août 2026 à 20:04 UTCresolved

   Cet incident a été résolu.

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

1. 14 août 2026 à 17:21 UTCidentified

   Heroes may see previous values after saving changes in Course content. Updates are being processed and applied normally, but may not immediately display. You can refresh the page to see the updated content in the meantime. Our engineering team is investigating and we will share another update as we have more information.

2. 14 août 2026 à 19:30 UTCmonitoring

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

3. 14 août 2026 à 20:41 UTCresolved

   This incident has been resolved.

1. 6 août 2026 à 15:09 UTCinvestigating

   We're investigating an issue affecting countdown timer blocks in email campaigns. Affected users may see errors when editing, previewing, or sending emails that contain a countdown block. Our team is actively looking into this with a vendor and we will post an update as soon as we have more information.

2. 6 août 2026 à 16:04 UTCmonitoring

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

3. 6 août 2026 à 17:10 UTCresolved

   This incident has been resolved.

1. 4 août 2026 à 16:29 UTCidentified

   We have identified the cause of the error occurring when accessing the Communities product. Our engineering team is implementing a fix and working as quickly as possible to restore normal functionality. We will share another update once the fix has been deployed.

2. 4 août 2026 à 16:38 UTCmonitoring

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

3. 4 août 2026 à 17:46 UTCresolved

   This incident has been resolved.

1. 3 août 2026 à 14:24 UTCidentified

   Nous avons remarqué certains problèmes affectant nos interactions de soutien. Il peut y avoir un retard dans la réponse de nos agents. Notre fournisseur de chat enquête et cherche à résoudre le problème. Nous fournirons une mise à jour dès que nous aurons plus d'informations. Veuillez contacter [email protected] pour répondre à vos besoins. Merci de votre patience, nous continuerons à mettre à jour cette page au fur et à mesure que la situation évoluera.

2. 3 août 2026 à 17:09 UTCresolved

   Notre fournisseur a mis en place un correctif et ceci est maintenant résolu.

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

1. 29 juillet 2026 à 00:22 UTCidentified

   Notre équipe a identifié un problème que notre équipe d'ingénieurs s'emploie activement à résoudre. Certaines vidéos nouvellement téléchargées peuvent afficher des vignettes manquantes ou bloquées, et certaines nouvelles notifications postales peuvent ne pas avoir été envoyées. La lecture vidéo dans les applications iOS et Android peut également être affectée.

2. 29 juillet 2026 à 18:26 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 29 juillet 2026 à 19:06 UTCresolved

   Cet incident a été résolu.

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

1. 15 juillet 2026 à 19:08 UTCidentified

   Nous avons identifié la cause du problème du tableau de bord de Community Meetup et notre équipe d'ingénieurs travaille sur une solution. Nous apprécions votre patience dans cette résolution.

2. 15 juillet 2026 à 19:10 UTCidentified

   Nous savons que la page Community Meetup est inaccessible et notre équipe d'ingénieurs travaille sur une solution. Nous apprécions votre patience dans cette résolution.

3. 15 juillet 2026 à 19:42 UTCmonitoring

   Une correction a été mise en œuvre et nous surveillons les résultats.

4. 15 juillet 2026 à 20:02 UTCresolved

   Cet incident a été résolu.

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

1. 30 juin 2026 à 09:49 UTCinvestigating

   We’re currently investigating reports of slow page loads and intermittent issues accessing Kajabi. Our engineering team is actively investigating and will provide updates as more information becomes available.

2. 30 juin 2026 à 11:29 UTCinvestigating

   We're continuing to investigate reports of slow page loads and issues accessing Kajabi. Our engineering team is actively working to identify the root cause and restore normal performance as quickly as possible. We'll continue to provide updates as more information becomes available.

3. 30 juin 2026 à 11:38 UTCmonitoring

   A fix has been implemented, and we are seeing the platform recover. Users are once again able to access Kajabi, and services are returning to normal. We will continue to closely monitor to ensure stability and will provide additional updates if necessary.

4. 30 juin 2026 à 13:37 UTCresolved

   This incident has been resolved.

1. 26 juin 2026 à 17:41 UTCinvestigating

   We've identified an issue affecting the text field in email campaigns. Our engineering team is investigating the root cause and working to resolve this as quickly as possible. We'll provide updates as soon as we have more information.

2. 26 juin 2026 à 17:50 UTCidentified

   We've identified the root cause of the text field issue in email campaigns. Our engineering team is actively working on a fix and will deploy it as soon as it's ready. Thank you for your patience.

3. 26 juin 2026 à 18:28 UTCidentified

   We are continuing to work on a fix for this issue. We've identified that this also affects Coaching live room sessions. We'll continue to provide updates as soon as we have more information.

4. 26 juin 2026 à 18:50 UTCmonitoring

   A fix has been implemented. We're monitoring the situation closely to ensure everything is working as expected.

5. 26 juin 2026 à 19:41 UTCresolved

   This incident has been resolved.

1. 24 juin 2026 à 21:00 UTCinvestigating

   The Kajabi platform is currently unavailable. Our engineering team is actively investigating the cause and working to restore service as quickly as possible.

2. 24 juin 2026 à 21:04 UTCinvestigating

   The Kajabi platform may currently be unavailable for some Heroes. Our engineering team is actively investigating the cause and working to restore service as quickly as possible.

3. 24 juin 2026 à 21:09 UTCmonitoring

   A fix has been implemented and we are seeing the platform recover. We will continue to monitor the situation.

4. 24 juin 2026 à 21:21 UTCresolved

   This incident has been resolved.

1. 17 juin 2026 à 19:16 UTCinvestigating

   Some Heroes and members are currently unable to access their Kajabi Communities and/or are experiencing other issues within the Community. Our engineering team is actively investigating. We will provide updates as soon as more information is available.

2. 17 juin 2026 à 22:35 UTCmonitoring

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

3. 17 juin 2026 à 22:59 UTCresolved

   This incident has been resolved.

1. 12 juin 2026 à 15:13 UTCinvestigating

   We're currently investigating an issue affecting Community Direct Messages (DMs) on both the web and the Kajabi Mobile App (KMA), where users may be unable to load previous messages or new messages may not appear. Our engineering team is actively looking into the issue. We'll share more updates as soon as we've identified the root cause. We highly appreciate your patience at this time.

2. 12 juin 2026 à 15:54 UTCmonitoring

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

3. 12 juin 2026 à 15:56 UTCmonitoring

   We have identified the root cause and pushed out a fix. Your Community DMs should now be loading up properly. We'll continue to monitor the situation for any changes.

4. 12 juin 2026 à 16:26 UTCresolved

   This incident has been resolved.

1. 3 juin 2026 à 16:11 UTCidentified

   We are currently investigating reports that mykajabi.com subdomains are inaccessible for users located in Turkey. This may also impact Users making changing to their content.

2. 3 juin 2026 à 16:11 UTCidentified

   We have identified the cause of the issue affecting mykajabi.com subdomains for users in Turkey. We will continue to provide updates as we make progress.

3. 7 juin 2026 à 01:32 UTCresolved

   This incident has been resolved.

1. 2 juin 2026 à 17:13 UTCinvestigating

   We are currently investigating reports of participants being unexpectedly disconnected from Live Rooms sessions. Our team is actively looking into the issue and will provide updates as they become available. We apologize for the disruption.

2. 2 juin 2026 à 19:20 UTCinvestigating

   We are continuing to investigate this issue and will continue to provide further updates as they become available. We appreciate your patience.

3. 2 juin 2026 à 20:52 UTCmonitoring

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

4. 2 juin 2026 à 22:39 UTCresolved

   This incident has been resolved.

1. 31 mai 2026 à 02:45 UTCmonitoring

   One of our vendors is undergoing scheduled maintenance from 7:30 PM – 8:30 PM PST. During this window, video and audio uploads may be delayed or appear stuck. We'll continue to provide updates here as they come.

2. 31 mai 2026 à 03:30 UTCresolved

   The maintenance has completed successfully.

1. 29 mai 2026 à 17:03 UTCinvestigating

   We are currently investigating reports of errors affecting community access. Some users may be unable to load or interact with community content. Our team has been alerted and is actively looking into the issue.

2. 29 mai 2026 à 20:14 UTCmonitoring

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

3. 29 mai 2026 à 21:32 UTCresolved

   This incident has been resolved.

1. 27 mai 2026 à 15:29 UTCinvestigating

   We are currently investigating reports of slower than expected response times with CoFounder. Our team is actively looking into the cause and working to restore normal performance as quickly as possible. We'll provide updates as we learn more.

2. 27 mai 2026 à 16:32 UTCidentified

   We've identified the cause as an ongoing incident with OpenAI, which CoFounder relies on. CoFounder response times will remain delayed until OpenAI resolves the upstream issue. You can monitor OpenAI's status directly at https://status.openai.com. We'll continue to provide updates here as we learn more.

3. 28 mai 2026 à 15:07 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 à 15:48 UTCidentified

   We are aware of an issue where the "Respond to dispute" button on disputed transactions is not responding when clicked. We will update this status once we have more information.

2. 14 mai 2026 à 16:23 UTCmonitoring

   A fix has been deployed for the issue affecting the "Respond to dispute" button on disputed transactions. We are monitoring to confirm stability.

3. 14 mai 2026 à 16:42 UTCresolved

   Functionality has been restored and the "Respond to dispute" button is working as expected.

1. 13 mai 2026 à 14:05 UTCinvestigating

   We are currently investigating reports of Heroes being unable to access the support portal through the "Contact support" on the top right menu in Kajabi. Our team is actively working to identify the cause and resolve this as quickly as possible. As a temporary workaround, you can access our help center directly at help.kajabi.com for assistant or contact our support team via email at [email protected].

2. 13 mai 2026 à 15:35 UTCmonitoring

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

3. 13 mai 2026 à 17:21 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 à 20:39 UTCidentified

   We have identified an issue where users are experiencing errors when attempting to access the Webhooks page via Settings > Integrations & Webhooks > Webhooks. Our engineering team is actively working on a fix and we are moving as quickly as possible to restore full functionality. We will continue to provide updates as we make progress.

2. 6 mai 2026 à 20:47 UTCresolved

   This incident has been resolved.