Khoros driftsforstyrrelser

1. 17. august 2026 kl. 10.21 UTCmonitoring

   Vi har identificeret og rettet et problem, der påvirker analytics siden den 14. august, vi arbejder på at efterfylde data.

2. 18. august 2026 kl. 00.05 UTCmonitoring

   De manglende analytiske data for august 14- 16 er blevet restaureret. Vi fortsætter med at overvåge den næste behandlingscyklus for at sikre, at indberetningen forbliver aktuel.

3. 18. august 2026 kl. 11.27 UTCresolved

   Denne hændelse er blevet løst. Hvis du støder på problemer, tøv ikke med at kontakte vores support team.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juli 2026 kl. 13.44 UTCinvestigating

   Vi har identificeret et problem, der berører den daglige behandling af fællesskabsanalytics og bulk data API-data i EU-regionen. Nogle kunder kan se manglende eller forsinkede analytiske data siden juli 27, 2026. Vi arbejder på at gendanne de berørte data og vil give en opdatering, når inddrivelse er blevet valideret.

2. 30. juli 2026 kl. 14.50 UTCidentified

   Spørgsmålet er blevet identificeret, og der er indledt et tilbageslag for de manglende data.

3. 30. juli 2026 kl. 23.49 UTCidentified

   Dataindsamlingen er i øjeblikket i gang, og vi overvåger fortsat genopretningen af fællesskabsanalytikkerne og Bulk Data API-dataene i EU-regionen. Vi vil give en anden opdatering, når backfill er blevet afsluttet og data recovery er blevet valideret.

4. 31. juli 2026 kl. 01.30 UTCmonitoring

   Dataene er udfyldt med succes. Vi validerer i øjeblikket, at alle manglende fællesskabsanalytics og bulk data API-data er blevet fuldstændig genoprettet i EU-regionen. Vi vil fortsat overvåge tjenesten.

5. 31. juli 2026 kl. 05.42 UTCresolved

   Det spørgsmål, der berører Fællesskabets Analytics og Bulk Data API 's daglige behandling i EU-regionen, er løst. Den data-backfill er afsluttet med succes.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 13.25 UTCidentified

   Vi undersøger i øjeblikket et problem, der påvirker US Care Analytics / Search. Den grundlæggende årsag er blevet identificeret, og afbødning er i gang. Vi vil give yderligere opdateringer, når der er gjort fremskridt.

2. 27. juli 2026 kl. 14.38 UTCidentified

   Vi fortsætter med at genoprette en komponent, der understøtter Care Analytics og visse CRM integration funktioner. Servicetilgængeligheden forbedres, efterhånden som restaureringen skrider frem. I denne periode kan nogle brugere opleve intermitterende fejl ved indlæsning af forbundne CRM-registreringer eller felttilknytninger i CRM-integrationspanelet. Care Analytics data kan også være forsinket, utilgængelige, eller ufuldstændige, mens inddrivelse er afsluttet.

3. 27. juli 2026 kl. 20.14 UTCresolved

   Problemet med US Care Analytics / Search er løst. En lille del af Care Analytics data kan også være forsinket, utilgængelig, eller ufuldstændig, mens recovery er afsluttet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 18.45 UTCinvestigating

   Vi er ved at undersøge forringet ydeevne i hele EU-regionen forårsager intermitterende Flow- to- Care fejl, som kan forhindre bot tømmermænd, kundereaktioner, workqueue opdateringer, og timer / løse handlinger fra at fuldføre pålideligt.

2. 9. juli 2026 kl. 19.26 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 9. juli 2026 kl. 20.47 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juli 2026 kl. 17.45 UTCinvestigating

   Vi undersøger intermitterende forsinkelser, der påvirker nogle Khoros Care kunder, hvor nye kontakter kan tage længere tid end normalt at vise sig i køer, køtællinger kan vise unøjagtigt, og agent handlinger såsom tildeling af sager eller udstationering svar kan være langsom. Beskedindtagelse påvirkes ikke, og ingen data går tabt - disse problemer påvirker kun synlighed og agent arbejdsgang. Vores team arbejder aktivt på at løse dette og vil dele opdateringer, efterhånden som de bliver tilgængelige.

2. 8. juli 2026 kl. 19.46 UTCidentified

   Vi har identificeret årsagen til det aktuelle problem og anvender øjeblikkelige løsninger for at reducere virkningen. Yderligere permanente rettelser vil blive gennemført i løbet af weekenden for fuldt ud at løse problemet. Vi vil fortsætte med at dele opdateringer, når de bliver tilgængelige.

3. 9. juli 2026 kl. 12.11 UTCmonitoring

   Vi har anvendt infrastrukturløsninger natten over i et lavtrafikvindue. Siden i morges er præstationsmålinger for EU Care blevet normale og har været stabile i myldretiden. Vi overvåger aktivt hele dagen for at bekræfte stabiliteten. Yderligere forebyggende vedligeholdelse er planlagt til den kommende weekend i off- peak timer.

4. 10. juli 2026 kl. 02.43 UTCresolved

   Vi har ikke observeret yderligere præstationsspørgsmål. Dette spørgsmål er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 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 kl. 10.08 UTCmonitoring

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

3. 1. juli 2026 kl. 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 kl. 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 kl. 03.26 UTCresolved

   This incident has been resolved

1. 30. juni 2026 kl. 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 kl. 12.24 UTCmonitoring

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

3. 30. juni 2026 kl. 21.09 UTCmonitoring

   We continue monitoring the results of the implemented fix

4. 30. juni 2026 kl. 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 kl. 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 kl. 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 kl. 03.28 UTCresolved

   This incident has been resolved

1. 29. juni 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 14.45 UTCresolved

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

1. 23. juni 2026 kl. 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 kl. 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 kl. 03.04 UTCmonitoring

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

4. 24. juni 2026 kl. 11.23 UTCresolved

   This incident has been resolved.

1. 15. juni 2026 kl. 15.28 UTCidentified

   Vi har identificeret den grundlæggende årsag og gennemfører genopretningsforanstaltninger.

2. 15. juni 2026 kl. 21.40 UTCmonitoring

   Vi har løst problemet og udfyldt de manglende analytikere.

3. 18. juni 2026 kl. 02.50 UTCmonitoring

   Vi har udfyldt data for alle de manglende dage og fortsætter med at overvåge for yderligere spørgsmål.

4. 22. juni 2026 kl. 03.22 UTCmonitoring

   Vi fortsætter med at overvåge dette for at sikre, at tingene ser godt ud.

5. 22. juni 2026 kl. 14.31 UTCmonitoring

   Vi har ikke observeret yderligere spørgsmål i overvågningsperioden. Systemet fungerer fortsat som forventet, og vi vil fortsat overvåge for at sikre stabilitet.

6. 23. juni 2026 kl. 04.08 UTCmonitoring

   Vi fortsætter vores overvågning for at bekræfte den fortsatte stabilitet og vil om nødvendigt opdatere.

7. 24. juni 2026 kl. 14.37 UTCmonitoring

   Overvågningen fortsætter med at bekræfte den fortsatte stabilitet, og vi vil fremlægge opdateringer efter behov.

8. 26. juni 2026 kl. 11.10 UTCmonitoring

   Vi fortsætter overvågningen for at bekræfte den fortsatte stabilitet og vil om nødvendigt give opdateringer.

9. 29. juni 2026 kl. 02.35 UTCmonitoring

   Vi fortsætter overvågningen for at bekræfte den fortsatte stabilitet og vil om nødvendigt opdatere.

10. 30. juni 2026 kl. 03.44 UTCmonitoring

    Hele Fællesskabet Analytics backfills er blevet afsluttet, og data strømmer som forventet. Vi har identificeret et resterende hul i registreringen målinger går tilbage til maj 21. Vores team arbejder aktivt på at fylde disse data. Vi vil fortsætte med at opdatere de fremskridt, der er gjort i retning af at færdiggøre denne efterfyldning.

11. 1. juli 2026 kl. 04.21 UTCmonitoring

    Registreringsmålingerne er stadig i gang. Vores team fortsætter med at arbejde på at færdiggøre disse data. Den næste opdatering vil blive leveret i 24 timer.

12. 1. juli 2026 kl. 23.58 UTCmonitoring

    Registreringsmålets-backfill er stadig i gang. Vores team fortsætter med at arbejde gennem de resterende data hul og vil give en anden opdatering, når fremskridt er gjort.

13. 2. juli 2026 kl. 23.34 UTCmonitoring

    Genopretningen af analytikernes datahuller er afsluttet. Validering har bekræftet, at de berørte data er tilgængelige igen, og der er ikke identificeret yderligere gentagelser for denne hændelse. Eventuelle resterende miljøspecifikke eller separate meterrelaterede opfølgning vil fortsat blive sporet uden for denne hændelse. Vi vil fortsætte med at overvåge dette fix for de næste 24 timer. Tak for din tålmodighed.

14. 3. juli 2026 kl. 03.19 UTCmonitoring

    Der er stadig problemer med efterfyldningen af registreringsmålinger i EF-analytikkerne. Registreringsdata for den tidligere identificerede gap periode er ved at blive genoprettet, og delvis genopretning bekræftes. Vi vil fortsætte med at overvåge og levere en opdatering, når backfill er helt færdig.

15. 4. juli 2026 kl. 06.58 UTCmonitoring

    Ingen problemer er observeret i øjeblikket med backfills. Vi fortsætter med at overvåge dette.

16. 5. juli 2026 kl. 12.57 UTCmonitoring

    Vores team er fortsat engageret i overvågning for at sikre fortsat stabilitet og vil sende opdateringer efter behov.

17. 7. juli 2026 kl. 09.01 UTCmonitoring

    Vores team er fortsat engageret i overvågning for at sikre fortsat stabilitet og vil sende opdateringer, når de kommer op.

18. 8. juli 2026 kl. 07.51 UTCmonitoring

    Vores team er fortsat engageret i overvågning for at sikre fortsat stabilitet for vores kunder.

19. 8. juli 2026 kl. 12.56 UTCresolved

    Hele Fællesskabet Analytics-backfills er nu afsluttet, herunder de resterende målinger. Der er ikke identificeret yderligere datahuller i forbindelse med denne hændelse. Tak for din tålmodighed, mens vores hold afsluttet inddrivelse og validering arbejde.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. juni 2026 kl. 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 kl. 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 kl. 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 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 08.39 UTCidentified

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

4. 30. maj 2026 kl. 08.39 UTCidentified

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

5. 1. juni 2026 kl. 17.10 UTCidentified

   The backfilling process is progressing as expected.

6. 2. juni 2026 kl. 03.52 UTCidentified

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

7. 2. juni 2026 kl. 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 kl. 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 kl. 18.46 UTCidentified

   The team continues working on the remediation.

10. 5. juni 2026 kl. 03.31 UTCidentified

    The remediation effort is ongoing by our teams.

11. 5. juni 2026 kl. 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 kl. 20.01 UTCmonitoring

    We are continuing to monitor for any further issues.

13. 6. juni 2026 kl. 20.14 UTCresolved

    The incident has been resolved.

1. 28. maj 2026 kl. 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. maj 2026 kl. 14.24 UTCinvestigating

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

3. 28. maj 2026 kl. 15.22 UTCmonitoring

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

4. 28. maj 2026 kl. 19.18 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 28. maj 2026 kl. 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. maj 2026 kl. 03.19 UTCresolved

   This incident has been resolved.

1. 27. maj 2026 kl. 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. maj 2026 kl. 11.01 UTCinvestigating

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

3. 27. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 14.25 UTCidentified

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

6. 28. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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 kl. 04.17 UTCresolved

    This incident has been resolved.

1. 25. maj 2026 kl. 01.06 UTCinvestigating

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

2. 25. maj 2026 kl. 01.59 UTCidentified

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

3. 25. maj 2026 kl. 09.13 UTCidentified

   The fix for the issue is under review.

4. 26. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 10.59 UTCmonitoring

   We continue monitoring pipeline stability.

9. 27. maj 2026 kl. 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. maj 2026 kl. 02.29 UTCresolved

    The incident with APAC hosted communities is resolved.

1. 20. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 20.00 UTCmonitoring

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

8. 24. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 10.34 UTCmonitoring

   We will continue monitoring the system to ensure stability.

6. 24. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 21.09 UTCmonitoring

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

4. 20. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 21.21 UTCinvestigating

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

4. 14. maj 2026 kl. 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. maj 2026 kl. 04.58 UTCresolved

   The incident has been resolved.