Khoros kesinti geçmişi

1. 10 Eylül 2026 21:35 UTCidentified

   Instagram ve Facebook entegrasyonlarımız aracılığıyla gelen mesaj teslimatını etkileyen bir konudur. Bazı müşteriler cevap göndermede başarısızlık yaşayabilirler. Ekibimiz kök nedenini araştırıyor ve bir karar üzerinde çalışıyor. Güncellemeleri daha fazla bilgi olarak sunacağız

2. 11 Eylül 2026 06:08 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Ağustos 2026 10:21 UTCmonitoring

   14 Ağustos'tan bu yana analitikleri etkileyen ve düzelttik, verileri geri yükleme üzerinde çalışıyoruz.

2. 18 Ağustos 2026 00:05 UTCmonitoring

   14-16 Ağustos için eksik analitik veriler başarıyla restore edilmiştir. raporlamanın mevcut kalmasını sağlamak için bir sonraki işlem döngüsünü izlemeye devam ediyoruz.

3. 18 Ağustos 2026 11:27 UTCresolved

   Bu olay çözüldü. Sorunlarla karşılaşırsanız lütfen destek ekibimize ulaşmak için tereddüt etmeyin.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 30 Temmuz 2026 13:44 UTCinvestigating

   Community Analytics ve Bulk Data API verilerini AB bölgesinde etkileyen günlük işleme etkileyen bir sorunu tespit ettik. Bazı müşteriler 27 Temmuz 2026'dan beri eksik veya gecikmiş analitik verileri görebilir. Etkilenen verileri geri yüklemek için çalışıyoruz ve bir kez kurtarma onaylandı.

2. 30 Temmuz 2026 14:50 UTCidentified

   Sorun tespit edildi ve eksik veriler için geri bir dolum başlatıldı.

3. 30 Temmuz 2026 23:49 UTCidentified

   Veri geri yükleme şu anda ilerliyor ve AB bölgesindeki Community Analytics ve Bulk Data API verilerini izlemeye devam ediyoruz. Geri dolum tamamlandıktan sonra başka bir güncelleme sağlayacağız ve veri kurtarma onaylandı.

4. 31 Temmuz 2026 01:30 UTCmonitoring

   Geri yükleme işlemi başarıyla tamamlandı. Şu anda tüm eksik Community Analytics ve Bulk Data API verilerinin AB bölgesinde tamamen restore edildiğini biliyoruz. Hizmeti izlemeye devam edeceğiz.

5. 31 Temmuz 2026 05:42 UTCresolved

   Community Analytics ve Bulk Data API'yi etkileyen konu, AB bölgesinde günlük işlem çözüldü. Data backfill başarıyla tamamlandı.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 27 Temmuz 2026 13:25 UTCidentified

   Şu anda ABD Bakım Analytics / Search'i etkileyen bir sorunu araştırıyoruz. Kök nedeni tespit edildi ve tazminat çabaları devam ediyor. İlerlemenin yapıldığı gibi daha fazla güncelleme sağlayacağız.

2. 27 Temmuz 2026 14:38 UTCidentified

   Bakım Analytics ve belirli CRM entegrasyonu işlevlerini destekleyen bir bileşeni geri yüklemeye devam ediyoruz. Servis kullanılabilirliği restorasyon ilerlemeleri olarak gelişiyor. Bu süre zarfında, bazı kullanıcılar CRM kayıtlarını veya saha haritalarını CRM entegrasyonu panelinde yükleme yaparken geçici hataları deneyimleyebilir. Bakım Analytics verileri de gecikebilir, yok edilemez veya kurtarma tamamlandığında eksik olabilir.

3. 27 Temmuz 2026 20:14 UTCresolved

   ABD Bakım Analytics / Search'in etkisi çözüldü. Bakım Analytics verilerinin küçük bir kısmı da gecikebilir veya kurtarma tamamlandığında eksik olabilir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 9 Temmuz 2026 18:45 UTCinvestigating

   Avrupa Bölgesi'nde bozulan performansı araştırıyoruz, intermittent Flow-to-Care başarısızlıklarına neden oluyor, bu da bot handoffs, müşteri cevaplarını, işqueue güncelleştirmelerini ve zamanlayıcı / eylemleri güvenilir bir şekilde tamamlamayı engelleyebilir.

2. 9 Temmuz 2026 19:26 UTCmonitoring

   Bir düzeltme uygulandı ve sonuçları takip ediyoruz.

3. 9 Temmuz 2026 20:47 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 8 Temmuz 2026 17:45 UTCinvestigating

   Bazı Khoros Bakım müşterilerini etkileyen geçici gecikmeleri araştırıyoruz, yeni temasların kuyruklarda ortaya çıkması her zamankinden daha uzun sürebilir, kuyruk sayıları yanlışlıkla görüntülenebilir ve vakaları atama gibi ajan eylemleri yavaş olabilir. Mesaj ingestion etkilenmez ve hiçbir veri kaybolmaz - bu sorunlar görünürlüğü ve ajan iş akışını sadece etkiler. Ekibimiz bunu çözmek için aktif olarak çalışıyor ve mevcut oldukları gibi güncelleştirmeleri paylaşacaktır.

2. 8 Temmuz 2026 19:46 UTCidentified

   Mevcut sorunun nedenini tespit ettik ve etkisini azaltmak için derhal düzeltmeler uyguluyoruz. Ek kalıcı düzeltmeler, sorunu tamamen çözmek için hafta sonu boyunca uygulanacaktır. Mevcut oldukları gibi güncelleştirmeleri paylaşmaya devam edeceğiz.

3. 9 Temmuz 2026 12:11 UTCmonitoring

   Düşük trafikte bir gecede altyapı düzeltmeleri yaptık. Bu sabahtan bu yana, EU Care için performans ölçümleri normale döndü ve zirve saatler boyunca istikrarlı kaldı. Stabiliteyi doğrulamak için gün boyunca aktif olarak izliyoruz. Ek önleyici bakım, önümüzdeki hafta sonu için kapalı saatler boyunca planlanıyor.

4. 10 Temmuz 2026 02:43 UTCresolved

   Daha fazla performans sorunu gözlemledik. Bu konu şimdi çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 1 Temmuz 2026 09:15 UTCidentified

   There is an issue affecting users' ability to log in to the platform. Our engineering team has identified the cause and is actively working on a resolution to restore normal service

2. 1 Temmuz 2026 10:08 UTCmonitoring

   Our engineering team has implemented a fix for this and we are monitoring to confirm stability.

3. 1 Temmuz 2026 23:58 UTCmonitoring

   We are continuing to monitor the platform after the implemented fix. Current results remain stable, and we will keep monitoring to ensure the login functionality continues operating as expected.

4. 2 Temmuz 2026 23:44 UTCmonitoring

   We are continuing to monitor the platform following the implemented fix. Current results remain stable, and we will provide another update if any additional action is required.

5. 3 Temmuz 2026 03:26 UTCresolved

   This incident has been resolved

1. 30 Haziran 2026 11:54 UTCidentified

   We have identified an issue that are causing some of our users facing issues with sending and loading messages. Our infrastructure team is working on this with highest priority.

2. 30 Haziran 2026 12:24 UTCmonitoring

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

3. 30 Haziran 2026 21:09 UTCmonitoring

   We continue monitoring the results of the implemented fix

4. 30 Haziran 2026 23:51 UTCresolved

   This incident has been resolved. After monitoring the results of the implemented fix and receiving confirmation that the issue is no longer occurring, we have confirmed that chat loading and message sending functionality has been restored for APAC users.

1. 30 Haziran 2026 01:08 UTCinvestigating

   We are currently investigating an issue with Community to Care ingesting for the US tenants. Customers may see new Community posts and replies appear in Care with significant delays or not appear at all. Our team is actively investigating.

2. 30 Haziran 2026 02:05 UTCmonitoring

   Our team has identified the root cause of the issue and applied a fix. The service is currently recovering, and we are actively monitoring to ensure full stability.

3. 30 Haziran 2026 03:28 UTCresolved

   This incident has been resolved

1. 29 Haziran 2026 12:40 UTCinvestigating

   We are investigating an issue affecting Community-to-Care ingestion for some EU tenants. Customers may see new Community posts and replies appear in Care with significant delays or not appear at all. Our team is actively investigating.

2. 29 Haziran 2026 13:11 UTCidentified

   We have restored real-time Community-to-Care ingestion for affected EU tenants. Some content created earlier may still appear late or remain temporarily unavailable in Care while we complete recovery and validation. We are continuing to monitor the service and work through the remaining impacted items.

3. 29 Haziran 2026 14:52 UTCmonitoring

   We are monitoring the service following mitigation of the earlier ingestion issue. Some content created during the incident window may still appear in Care with delay while backfill and validation continue.

4. 29 Haziran 2026 23:52 UTCmonitoring

   We are continuing to monitor the service after the earlier mitigation. Recovery activities and validation remain in progress, and some previously affected Community content may still appear in Care with delays while the remaining backlog is processed.

5. 30 Haziran 2026 14:45 UTCresolved

   This incident has been resolved, and the old content has been successfully synchronized.

1. 23 Haziran 2026 11:54 UTCinvestigating

   We are currently investigating an issue affecting Care Message Analytics, resulting in incomplete analytics data. We will provide updates as the investigation progresses.

2. 23 Haziran 2026 20:41 UTCmonitoring

   The issue has been resolved. We continue to monitor the communities and ensure that the services have been fully re-established.

3. 24 Haziran 2026 03:04 UTCmonitoring

   We continue to monitor the communities and ensure that the services have been fully re-established.

4. 24 Haziran 2026 11:23 UTCresolved

   This incident has been resolved.

1. 15 Haziran 2026 15:28 UTCidentified

   Kök nedeni tespit ettik ve kurtarma önlemleri uyguluyoruz.

2. 15 Haziran 2026 21:40 UTCmonitoring

   Sorunu çözdük ve eksik analizi geri aldık.

3. 18 Haziran 2026 02:50 UTCmonitoring

   Tüm eksik günler için verileri yeniden doldurduk ve başka bir konu için izlemeye devam ettik.

4. 22 Haziran 2026 03:22 UTCmonitoring

   Bunu, şeylerin iyi görünmesini sağlamak için izlemeye devam ediyoruz.

5. 22 Haziran 2026 14:31 UTCmonitoring

   İzleme döneminde daha fazla sorun gözlemlemedik. Sistem beklendiği gibi çalışmaya devam ediyor ve istikrar sağlamak için izlemeye devam edeceğiz.

6. 23 Haziran 2026 04:08 UTCmonitoring

   Sürekli istikrarı doğrulamak için izlememizi sürdürüyoruz ve gerekli güncellemeler sağlayacaktır.

7. 24 Haziran 2026 14:37 UTCmonitoring

   İzleme devam eden istikrarı doğrulamaya devam ediyor ve gerekli güncellemeler vereceğiz.

8. 26 Haziran 2026 11:10 UTCmonitoring

   Devam eden istikrarı doğrulamaya devam ediyoruz ve gerekirse güncelleştirmeler sağlayacaktır.

9. 29 Haziran 2026 02:35 UTCmonitoring

   Devam eden istikrarı doğrulamaya devam ediyoruz ve gerekli güncellemeler sağlayacaktır.

10. 30 Haziran 2026 03:44 UTCmonitoring

    Bütün topluluk Analytics backfills tamamlandı ve veriler bekleniyor. Kayıt ölçümlerinde kalan bir boşluk 21 Mayıs'a geri döndük. Ekibimiz bu veriler için geri dolum üzerinde aktif olarak çalışıyor. Bu geri yüklemeyi tamamlamak için yapılan ilerlemeye dair güncellemeler sunmaya devam edeceğiz.

11. 1 Temmuz 2026 04:21 UTCmonitoring

    Kayıt metrikleri geri yükleme hala ilerliyor. Ekibimiz bu verileri tamamlamak için çalışmaya devam ediyor. Sonraki güncelleme 24 saat içinde sağlanacaktır.

12. 1 Temmuz 2026 23:58 UTCmonitoring

    Kayıt ölçümleri geri yükleme devam ediyor. Ekibimiz kalan veri boşlukları ile çalışmaya devam ediyor ve ilerlemenin yapıldığı gibi başka bir güncelleme sağlayacaktır.

13. 2 Temmuz 2026 23:34 UTCmonitoring

    Analytics Data boşlukları için kurtarma tamamlandı. Geçerlilik, etkilenen verilerin tekrar mevcut olduğunu doğruladı ve bu olay için daha fazla recurrence tespit edilmedi. Kalan herhangi bir çevreye özgü veya ayrı metrik ile ilgili takip, bu olayın dışında takip edilmeye devam edecektir. Bu düzeltmeyi önümüzdeki 24 saat boyunca izlemeye devam edeceğiz. Sabrınız için teşekkür ederiz.

14. 3 Temmuz 2026 03:19 UTCmonitoring

    Community Analytics'teki Kayıt metrikleri için geri yükleme devam ediyor. Daha önce tespit edilen boşluk dönemi için kayıt verileri restore edilir ve kısmi kurtarma onaylanır. İzlemeye devam edeceğiz ve geri dolum tamamen tamamlandıktan sonra bir güncelleme sağlayacağız.

15. 4 Temmuz 2026 06:58 UTCmonitoring

    Şu anda arka depolarla ilgili hiçbir sorun gözlemlenmemektedir. Bunu izlemeye devam ediyoruz.

16. 5 Temmuz 2026 12:57 UTCmonitoring

    Ekibimiz, devam eden istikrarı sağlamak için izlemeye devam ediyor ve gerekli güncellemeler yayınlayacak.

17. 7 Temmuz 2026 09:01 UTCmonitoring

    Ekibimiz devam eden istikrarı sağlamak için izlemeye devam ediyor ve geldikleri gibi güncelleştirmeleri yayınlayacak.

18. 8 Temmuz 2026 07:51 UTCmonitoring

    Ekibimiz müşterilerimiz için devam eden istikrarı sağlamak için gözetim altında kalıyor.

19. 8 Temmuz 2026 12:56 UTCresolved

    Bütün topluluk Analytics backfills şimdi tamamlandı, kalan ölçümler de dahil. Bu olayla ilgili daha fazla veri boşlukları tespit edilmedi. Sabrınız için teşekkür ederiz, ekiplerimiz kurtarma ve doğrulama çalışmalarını tamamladı.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 12 Haziran 2026 14:09 UTCinvestigating

   We are currently investigating a partner platform issue affecting Khoros Care integrations with Meta services. Customers may experience delays, errors, or intermittent failures when using connected Meta channels, including message ingestion, publishing, or synchronization. Our teams are monitoring the situation closely and will provide updates as more information becomes available.

2. 12 Haziran 2026 15:29 UTCidentified

   Meta is currently experiencing high disruptions impacting Messenger API for Instagram, Facebook and Whatsapp, which in turn is impacting Khoros message ingestion activities.

3. 12 Haziran 2026 21:17 UTCmonitoring

   The disruptions from Meta have now been resolved. We are actively monitoring on our end. Please reach out via a Support ticket if any Meta integrations are not working as expected.

4. 15 Haziran 2026 02:23 UTCresolved

   The issue related to the Meta platform disruption has been resolved, and services are now operating normally. Please note that the disruption may have caused some Meta channel connections to become disconnected. If you encounter connection errors, please re-register and re-verify the affected number/account with Meta. If the issue persists after re-registration and verification, please contact Support for further assistance.

1. 29 Mayıs 2026 15:07 UTCidentified

   We are aware of an issue with analytics for EU-hosted classic communities. We have triggered the backfill already, and we'll post updates as they are made.

2. 29 Mayıs 2026 23:58 UTCidentified

   We are continuing to work on restoring the missing analytics data for EU-hosted classic communities. The backfill process has already been initiated, and we are monitoring its progress closely. We will provide another update as soon as more information becomes available.

3. 30 Mayıs 2026 08:39 UTCidentified

   Data has been backfilled up to the 27th. We continue to backfill the remaining two days.

4. 30 Mayıs 2026 08:39 UTCidentified

   We continue to backfill data for May 28th and 29th.

5. 1 Haziran 2026 17:10 UTCidentified

   The backfilling process is progressing as expected.

6. 2 Haziran 2026 03:52 UTCidentified

   We are continuing to monitor the backfilling status. No issues have been encountered.

7. 2 Haziran 2026 23:54 UTCidentified

   Our team is currently working on the required remediation. We will share the next update as soon as additional progress is made.

8. 4 Haziran 2026 03:51 UTCidentified

   The remediation effort remains underway. We will share the next update as soon as there is more to report.

9. 4 Haziran 2026 18:46 UTCidentified

   The team continues working on the remediation.

10. 5 Haziran 2026 03:31 UTCidentified

    The remediation effort is ongoing by our teams.

11. 5 Haziran 2026 11:34 UTCmonitoring

    The issue affecting analytics collection has been resolved, and analytics data is now being collected and processed correctly. We have completed our investigation and remediation activities and will continue to monitor the platform to ensure ongoing stability.

12. 5 Haziran 2026 20:01 UTCmonitoring

    We are continuing to monitor for any further issues.

13. 6 Haziran 2026 20:14 UTCresolved

    The incident has been resolved.

1. 28 Mayıs 2026 06:38 UTCinvestigating

   We are currently investigating an issue affecting user login for some customers. Impacted users may experience MFA failures, including invalid token errors or issues receiving SMS authentication codes. We have identified that the issue appears to be related to the authentication flow. We are further investigating and will provide further updates as soon as more information is available.

2. 28 Mayıs 2026 14:24 UTCinvestigating

   We are continuously working on a fix and actively monitoring the situation.

3. 28 Mayıs 2026 15:22 UTCmonitoring

   Our infrastructure team has applied a fix for the MFA issue and we are monitoring the results.

4. 28 Mayıs 2026 19:18 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 28 Mayıs 2026 23:54 UTCmonitoring

   The issue affecting some user login flows has been resolved. We have completed monitoring and are not seeing further impact at this time. Thank you for your patience.

6. 29 Mayıs 2026 03:19 UTCresolved

   This incident has been resolved.

1. 27 Mayıs 2026 04:17 UTCinvestigating

   We are investigating reports of missing analytics data for AMER-hosted communities. Analytics data has been unavailable since May 21, 2026. Our Infrastructure team is actively looking into the root cause and we will provide updates as more information becomes available.

2. 27 Mayıs 2026 11:01 UTCinvestigating

   The Infrastructure team is working on backfilling the analytics data for AMER-hosted communities.

3. 27 Mayıs 2026 23:48 UTCidentified

   Our team is continuing to investigate the missing Community Analytics data affecting AMER-hosted communities. Work is ongoing to backfill the impacted analytics data, and we will provide another update as soon as more information is available.

4. 28 Mayıs 2026 06:19 UTCidentified

   Backfill work for AMER Community analytics data is ongoing. Analytics data for May 26th is now available. Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

5. 28 Mayıs 2026 14:25 UTCidentified

   We are continuously working on a fix and actively monitoring the situation.

6. 28 Mayıs 2026 19:18 UTCidentified

   Backfill work for AMER Community analytics data is ongoing. Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

7. 29 Mayıs 2026 03:28 UTCidentified

   We have completed backfilling data for May 21, 22, and 27. Work is currently ongoing to populate the remaining affected dates. We will continue to provide updates as progress is made.

8. 29 Mayıs 2026 20:59 UTCidentified

   Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.

9. 30 Mayıs 2026 07:52 UTCmonitoring

   All affected dates have been successfully backfilled. Please reach out to us if you are still experiencing any issues or require further assistance.

10. 1 Haziran 2026 04:17 UTCresolved

    This incident has been resolved.

1. 25 Mayıs 2026 01:06 UTCinvestigating

   We are currently investigating an issue affecting Community Analytics data for APAC-hosted communities from May 19 onwards.

2. 25 Mayıs 2026 01:59 UTCidentified

   The issue has been identified, and our team is working on fixing it.

3. 25 Mayıs 2026 09:13 UTCidentified

   The fix for the issue is under review.

4. 26 Mayıs 2026 00:23 UTCidentified

   Our team continues working on the fix for the Community Analytics data issue affecting some communities. The fix is still under review, and backfill work is in progress. We will provide another update as soon as we have more progress to share.

5. 26 Mayıs 2026 08:17 UTCidentified

   Our team continues to make progress on the Community Analytics data issue affecting some communities. The fix has completed review and backfill work is actively ongoing. We appreciate your patience and will provide updates once we have more to share.

6. 26 Mayıs 2026 23:16 UTCidentified

   Our team continues to work on the Community Analytics data issue affecting some hosted communities. Progress is ongoing, and we will provide another update as soon as we have more information to share.

7. 27 Mayıs 2026 04:01 UTCmonitoring

   The backfill has been completed for all affected dates and the analytics data pipeline is now running healthy. All APAC Community Analytics data that was missing since May 19 has been fully restored. We are now monitoring the pipeline to confirm continued stability before closing this incident.

8. 27 Mayıs 2026 10:59 UTCmonitoring

   We continue monitoring pipeline stability.

9. 27 Mayıs 2026 23:50 UTCmonitoring

   We are continuing to monitor the Community Analytics pipeline for APAC-hosted communities after the completion of the backfill. The analytics data pipeline remains stable at this time, and we will provide another update if there are any changes.

10. 28 Mayıs 2026 02:29 UTCresolved

    The incident with APAC hosted communities is resolved.

1. 20 Mayıs 2026 21:31 UTCinvestigating

   We are aware of an issue causing replies to Google My Business (GMB) reviews to fail. We are actively investigating this and will provide updates as they become available.

2. 20 Mayıs 2026 23:05 UTCidentified

   We have identified the issue causing Google My Business (GMB) reviews to fail, and our Engineering team are currently working on a fix.

3. 21 Mayıs 2026 04:43 UTCmonitoring

   A fix has been deployed to address the issue causing Google My Business review replies to fail in Khoros Care. We are actively monitoring the environment to ensure replies are processing as expected. If you continue to experience issues, please reach out to Khoros Support.

4. 21 Mayıs 2026 12:58 UTCidentified

   After continued monitoring, we found that the issue affecting Google My Business replies in Khoros Care is still ongoing, due to data consumed during the incident. We have identified the issue affecting some Google My Business replies and are actively working to restore reply publishing for impacted cases. We will share another update as soon as more information is available.

5. 22 Mayıs 2026 03:09 UTCidentified

   Our Engineering team is actively working on restoring reply publishing for impacted reviews. We will continue to provide updates as progress is made and share additional information as soon as it becomes available.

6. 22 Mayıs 2026 10:23 UTCidentified

   Work on restoring reply publishing for impacted reviews is ongoing. We will continue to provide updates as progress is made and share additional information as soon as it becomes available.

7. 22 Mayıs 2026 20:00 UTCmonitoring

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

8. 24 Mayıs 2026 22:17 UTCresolved

   We are closing this incident as the fix has been implemented and the environment has been monitored successfully. The issue affecting Google My Business review replies in Khoros Care has been addressed, and reply publishing for impacted reviews has been restored. Our Engineering team completed the required remediation work and monitored the results to confirm that replies are processing as expected. If you continue to experience any issues with Google My Business replies, please contact Khoros Support for further assistance.

1. 20 Mayıs 2026 14:59 UTCinvestigating

   We are investigating reports that some customers using Khoros Care are seeing Facebook Messenger / Facebook DM author names display as long numeric IDs instead of customer names. Agents can generally continue to read and respond to affected conversations, but identifying customers by name in Care may be impacted. We are actively investigating and will provide another update as soon as we have more information.

2. 20 Mayıs 2026 21:36 UTCidentified

   We have identified the issue causing some customers to see Facebook Messenger / Facebook DM author names display as long numeric IDs instead of customer names. We are working on a fix for this issue and will update as soon as this is deployed.

3. 21 Mayıs 2026 04:31 UTCidentified

   We have deployed a fix that addresses the root cause of this issue. Facebook Messenger and Facebook DM sender names are now displaying correctly for new incoming messages. For messages received during the incident window, our team is actively working to determine the best path to restore the correct sender names. We are committed to keeping you informed as this progresses and will share an update shortly. Agents can continue to read and respond to all conversations in the meantime

4. 22 Mayıs 2026 01:12 UTCmonitoring

   We have deployed a fix that addresses the root cause of this issue. Facebook Messenger and Facebook DM sender names are now displaying correctly for new incoming messages. For messages received during the incident window, our team has completed restoration efforts and sender names should now appear correctly. We will continue monitoring the system to ensure stability. Agents can continue to read and respond to all conversations as normal. Thank you for your patience while we worked through this issue.

5. 22 Mayıs 2026 10:34 UTCmonitoring

   We will continue monitoring the system to ensure stability.

6. 24 Mayıs 2026 22:20 UTCresolved

   The fix has been implemented, and the system has been monitored for stability. The issue causing Facebook Messenger and Facebook DM author names to display as numeric IDs in Khoros Care has been addressed. New incoming messages are now displaying sender names correctly, and restoration efforts for messages received during the incident window have been completed. If you continue to see Facebook author names displayed incorrectly, please contact Khoros Support for further assistance.

1. 18 Mayıs 2026 09:50 UTCinvestigating

   We have found that there were issues with Community Analytics data not coming up from May 12 for APAC-hosted communities. The team is investigating.

2. 18 Mayıs 2026 10:00 UTCidentified

   The issue has been identified, and the backfill has been triggered accordingly. Backfill is in progress, and we will keep you posted on its status.

3. 18 Mayıs 2026 21:09 UTCmonitoring

   The backfill has been completed. We continue to investigate the root cause.

4. 20 Mayıs 2026 02:17 UTCresolved

   The issue affecting Community Analytics data for APAC-hosted communities from May 12 onward has been resolved. The backfill has completed successfully, and data is now available as expected.