Störungsverlauf von Khoros

1. 17. August 2026 um 10:21 UTCmonitoring

   Wir haben seit dem 14. August ein Problem mit Analytics identifiziert und behoben, wir arbeiten daran, die Daten zu hinterlegen.

2. 18. August 2026 um 00:05 UTCmonitoring

   Die fehlenden Analysedaten für den 14. und 16. August wurden erfolgreich wiederhergestellt. Wir überwachen weiterhin den nächsten Verarbeitungszyklus, um sicherzustellen, dass die Berichterstattung aktuell bleibt.

3. 18. August 2026 um 11:27 UTCresolved

   Dieser Vorfall wurde behoben. Wenn sie probleme haben, zögern sie nicht, sich an unser support-team zu wenden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juli 2026 um 13:44 UTCinvestigating

   Wir haben ein Problem identifiziert, das die tägliche Verarbeitung von Community Analytics- und Bulk Data-API-Daten in der EU-Region betrifft. Einige Kunden sehen möglicherweise fehlende oder verzögerte Analysedaten seit dem 27. Juli 2026. Wir arbeiten daran, die betroffenen Daten wiederherzustellen und werden ein Update bereitstellen, sobald die Wiederherstellung validiert wurde.

2. 30. Juli 2026 um 14:50 UTCidentified

   Das Problem wurde identifiziert und eine Auffüllung der fehlenden Daten eingeleitet.

3. 30. Juli 2026 um 23:49 UTCidentified

   Die Daten-Backfill ist derzeit im Gange, und wir überwachen weiterhin die Wiederherstellung von Community Analytics und Bulk Data API-Daten in der EU-Region. Wir werden ein weiteres Update bereitstellen, sobald das Backfill abgeschlossen und die Datenwiederherstellung validiert wurde.

4. 31. Juli 2026 um 01:30 UTCmonitoring

   Die Datenauffüllung wurde erfolgreich abgeschlossen. Wir bestätigen derzeit, dass alle fehlenden Community Analytics- und Bulk Data API-Daten in der EU-Region vollständig wiederhergestellt wurden. Wir werden den Service weiterhin überwachen.

5. 31. Juli 2026 um 05:42 UTCresolved

   Das Problem, das die tägliche Verarbeitung von Community Analytics und Bulk Data API in der EU-Region betrifft, wurde behoben. Die Datenauffüllung ist erfolgreich abgeschlossen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. Juli 2026 um 13:25 UTCidentified

   Wir untersuchen derzeit ein Problem, das sich auf US Care Analytics / Search auswirkt. Die Ursache wurde identifiziert, und die Bemühungen zur Minderung sind im Gange. Wir werden weitere Updates bereitstellen, wenn Fortschritte gemacht werden.

2. 27. Juli 2026 um 14:38 UTCidentified

   Wir werden weiterhin eine Komponente wiederherstellen, die Care Analytics und bestimmte CRM-Integrationsfunktionen unterstützt. Die Serviceverfügbarkeit verbessert sich mit fortschreitender Wiederherstellung. Während dieser Zeit können bei einigen Benutzern intermittierende Fehler beim Laden von verknüpften CRM-Datensätzen oder Feldzuordnungen im CRM-Integrationsfeld auftreten. Care Analytics-Daten können auch verzögert, nicht verfügbar oder unvollständig sein, während die Wiederherstellung abgeschlossen ist.

3. 27. Juli 2026 um 20:14 UTCresolved

   Das Problem mit Auswirkungen auf US Care Analytics / Search wurde behoben. Ein kleiner Teil der Care Analytics-Daten kann auch verzögert, nicht verfügbar oder unvollständig sein, während die Wiederherstellung abgeschlossen ist.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juli 2026 um 18:45 UTCinvestigating

   Wir untersuchen eine beeinträchtigte Leistung in der gesamten EU-Region, die zu intermittierenden Flow-to-Care-Ausfällen führt, die verhindern können, dass Bot-Übergaben, Kundenantworten, Workqueue-Updates und Timer-/Resolve-Aktionen zuverlässig abgeschlossen werden.

2. 9. Juli 2026 um 19:26 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 9. Juli 2026 um 20:47 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Juli 2026 um 17:45 UTCinvestigating

   Wir untersuchen intermittierende Verzögerungen bei einigen Khoros Care-Kunden, bei denen neue Kontakte länger als üblich in Warteschlangen erscheinen können, die Anzahl der Warteschlangen ungenau angezeigt werden kann und Agentenaktionen wie das Zuweisen von Fällen oder das Posten von Antworten langsam sein können. Die Nachrichtenaufnahme ist nicht betroffen und es gehen keine Daten verloren – diese Probleme betreffen nur die Sichtbarkeit und den Agenten-Workflow. Unser Team arbeitet aktiv daran, dies zu beheben und wird Updates teilen, sobald sie verfügbar sind.

2. 8. Juli 2026 um 19:46 UTCidentified

   Wir haben die Ursache des aktuellen Problems identifiziert und wenden sofortige Korrekturen an, um die Auswirkungen zu reduzieren. Zusätzliche permanente Fixes werden am Wochenende implementiert, um das Problem vollständig zu lösen. Wir werden weiterhin Updates teilen, sobald sie verfügbar sind.

3. 9. Juli 2026 um 12:11 UTCmonitoring

   Wir haben Infrastruktur-Fixes über Nacht während eines niedrigen Verkehrsfensters angewendet. Seit heute Morgen haben sich die Leistungskennzahlen für EU Care wieder normalisiert und blieben während der Hauptverkehrszeiten stabil. Wir überwachen den ganzen Tag aktiv, um die Stabilität zu bestätigen. Zusätzliche vorbeugende Wartung ist für das kommende Wochenende während der Nebenzeiten geplant.

4. 10. Juli 2026 um 02:43 UTCresolved

   Wir haben keine weiteren Leistungsprobleme beobachtet. Dieses Problem ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juli 2026 um 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. Juli 2026 um 10:08 UTCmonitoring

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

3. 1. Juli 2026 um 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. Juli 2026 um 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. Juli 2026 um 03:26 UTCresolved

   This incident has been resolved

1. 30. Juni 2026 um 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. Juni 2026 um 12:24 UTCmonitoring

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

3. 30. Juni 2026 um 21:09 UTCmonitoring

   We continue monitoring the results of the implemented fix

4. 30. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 03:28 UTCresolved

   This incident has been resolved

1. 29. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 14:45 UTCresolved

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

1. 23. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 03:04 UTCmonitoring

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

4. 24. Juni 2026 um 11:23 UTCresolved

   This incident has been resolved.

1. 15. Juni 2026 um 15:28 UTCidentified

   Wir haben die Ursache identifiziert und setzen Sanierungsmaßnahmen um.

2. 15. Juni 2026 um 21:40 UTCmonitoring

   Wir haben das Problem gelöst und die fehlenden Analysen hinterlegt.

3. 18. Juni 2026 um 02:50 UTCmonitoring

   Wir haben die Daten für alle fehlenden Tage hinterlegt und überwachen weiterhin alle weiteren Probleme.

4. 22. Juni 2026 um 03:22 UTCmonitoring

   Wir überwachen dies weiterhin, um sicherzustellen, dass die Dinge gut aussehen.

5. 22. Juni 2026 um 14:31 UTCmonitoring

   Wir haben während des Überwachungszeitraums keine weiteren Probleme festgestellt. Das System funktioniert weiterhin wie erwartet, und wir werden die Stabilität weiterhin überwachen.

6. 23. Juni 2026 um 04:08 UTCmonitoring

   Wir behalten unsere Überwachung bei, um die anhaltende Stabilität zu bestätigen, und werden bei Bedarf Updates bereitstellen.

7. 24. Juni 2026 um 14:37 UTCmonitoring

   Die Überwachung bestätigt weiterhin die anhaltende Stabilität und wir werden bei Bedarf Updates bereitstellen.

8. 26. Juni 2026 um 11:10 UTCmonitoring

   Wir überwachen weiterhin die anhaltende Stabilität und werden bei Bedarf Updates bereitstellen.

9. 29. Juni 2026 um 02:35 UTCmonitoring

   Wir überwachen weiterhin die anhaltende Stabilität und werden bei Bedarf Updates bereitstellen.

10. 30. Juni 2026 um 03:44 UTCmonitoring

    Ganze Gemeinschaft Analytics-Backfills wurden abgeschlossen und die Daten fließen wie erwartet. Wir haben eine verbleibende Lücke in den Registrierungsmetriken aus dem 21. Mai identifiziert. Unser Team arbeitet aktiv an der Auffüllung dieser Daten. Wir werden weiterhin Updates über die Fortschritte bei der Fertigstellung dieser Backfill zur Verfügung stellen.

11. 1. Juli 2026 um 04:21 UTCmonitoring

    Die Registrierungsmetriken Backfill ist noch im Gange. Unser Team arbeitet weiter daran, diese Daten zu vervollständigen. Das nächste Update wird in 24 Stunden zur Verfügung gestellt.

12. 1. Juli 2026 um 23:58 UTCmonitoring

    Die Registrierungsmetriken Backfill bleibt im Gange. Unser Team arbeitet weiterhin an der verbleibenden Datenlücke und wird ein weiteres Update bereitstellen, sobald Fortschritte gemacht werden.

13. 2. Juli 2026 um 23:34 UTCmonitoring

    Die Wiederherstellung der Analytics Data-Lücken ist abgeschlossen. Die Validierung hat bestätigt, dass die betroffenen Daten wieder verfügbar sind, und es wurde keine weitere Wiederholung für diesen Vorfall festgestellt. Alle verbleibenden umgebungsspezifischen oder separaten metrischen Folgemaßnahmen werden weiterhin außerhalb dieses Vorfalls verfolgt. Wir werden diesen Fix für die nächsten 24 Stunden weiter überwachen. Vielen Dank für Ihre Geduld.

14. 3. Juli 2026 um 03:19 UTCmonitoring

    Das Backfill für Registrierungsmetriken in Community Analytics ist noch im Gange. Registrierungsdaten für die zuvor identifizierte Lückenperiode werden wiederhergestellt und eine teilweise Wiederherstellung wird bestätigt. Wir werden die Überwachung fortsetzen und ein Update bereitstellen, sobald die Auffüllung vollständig abgeschlossen ist.

15. 4. Juli 2026 um 06:58 UTCmonitoring

    Es werden derzeit keine Probleme mit den Backfills beobachtet. Wir werden dies weiterhin beobachten.

16. 5. Juli 2026 um 12:57 UTCmonitoring

    Unser Team bleibt bei der Überwachung, um weiterhin Stabilität zu gewährleisten, und wird bei Bedarf Updates veröffentlichen.

17. 7. Juli 2026 um 09:01 UTCmonitoring

    Unser Team bleibt bei der Überwachung, um weiterhin Stabilität zu gewährleisten, und wird Updates veröffentlichen, sobald sie auftauchen.

18. 8. Juli 2026 um 07:51 UTCmonitoring

    Unser Team bleibt bei der Überwachung engagiert, um eine anhaltende Stabilität für unsere Kunden zu gewährleisten.

19. 8. Juli 2026 um 12:56 UTCresolved

    Ganze Gemeinschaft Analytics-Backfills wurden nun abgeschlossen, einschließlich der verbleibenden Metriken. Es wurden keine weiteren Datenlücken im Zusammenhang mit diesem Vorfall festgestellt. Vielen Dank für Ihre Geduld, während unsere Teams die Wiederherstellungs- und Validierungsarbeit abgeschlossen haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 08:39 UTCidentified

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

4. 30. Mai 2026 um 08:39 UTCidentified

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

5. 1. Juni 2026 um 17:10 UTCidentified

   The backfilling process is progressing as expected.

6. 2. Juni 2026 um 03:52 UTCidentified

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

7. 2. Juni 2026 um 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. Juni 2026 um 03:51 UTCidentified

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

9. 4. Juni 2026 um 18:46 UTCidentified

   The team continues working on the remediation.

10. 5. Juni 2026 um 03:31 UTCidentified

    The remediation effort is ongoing by our teams.

11. 5. Juni 2026 um 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. Juni 2026 um 20:01 UTCmonitoring

    We are continuing to monitor for any further issues.

13. 6. Juni 2026 um 20:14 UTCresolved

    The incident has been resolved.

1. 28. Mai 2026 um 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. Mai 2026 um 14:24 UTCinvestigating

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

3. 28. Mai 2026 um 15:22 UTCmonitoring

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

4. 28. Mai 2026 um 19:18 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 28. Mai 2026 um 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. Mai 2026 um 03:19 UTCresolved

   This incident has been resolved.

1. 27. Mai 2026 um 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. Mai 2026 um 11:01 UTCinvestigating

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

3. 27. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 14:25 UTCidentified

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

6. 28. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Juni 2026 um 04:17 UTCresolved

    This incident has been resolved.

1. 25. Mai 2026 um 01:06 UTCinvestigating

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

2. 25. Mai 2026 um 01:59 UTCidentified

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

3. 25. Mai 2026 um 09:13 UTCidentified

   The fix for the issue is under review.

4. 26. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 10:59 UTCmonitoring

   We continue monitoring pipeline stability.

9. 27. Mai 2026 um 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. Mai 2026 um 02:29 UTCresolved

    The incident with APAC hosted communities is resolved.

1. 20. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 20:00 UTCmonitoring

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

8. 24. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 10:34 UTCmonitoring

   We will continue monitoring the system to ensure stability.

6. 24. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 21:09 UTCmonitoring

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

4. 20. Mai 2026 um 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.

1. 13. Mai 2026 um 16:00 UTCinvestigating

   We are currently investigating ingestion issues with some Care instances. The radius is unclear, so the customers are advised to create support tickets in case they notice degradation.

2. 14. Mai 2026 um 02:51 UTCmonitoring

   Our infrastructure team has applied a fix for the issue affecting ingestion. Services are recovering, and we are currently monitoring the environment to ensure stability. Customers should continue to report any ongoing degradation through support tickets.

3. 14. Mai 2026 um 21:21 UTCinvestigating

   We have observed some continued delays in post ingestion after our original fix, and we are investigating the cause.

4. 14. Mai 2026 um 22:39 UTCmonitoring

   We have identified the issue and implemented a secondary fix that has restored post ingestion. We are now working on a permanent fix for this.

5. 15. Mai 2026 um 04:58 UTCresolved

   The incident has been resolved.