Istoricul incidentelor Khoros

1. 17 august 2026 la 10:21 UTCmonitoring

   Am identificat și stabilit o problemă care afectează analiza începând cu 14 august, lucrăm la completarea datelor.

2. 18 august 2026 la 00:05 UTCmonitoring

   Datele de analiză lipsă pentru 14 august 16 au fost restaurate cu succes. Continuăm să monitorizăm următorul ciclu de prelucrare pentru a ne asigura că raportarea rămâne actuală.

3. 18 august 2026 la 11:27 UTCresolved

   Acest incident a fost rezolvat. Dacă vă confruntaţi cu probleme vă rugăm să nu ezitaţi să ajungeţi la echipa noastră de sprijin.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 13:44 UTCinvestigating

   Am identificat o problemă care afectează prelucrarea zilnică a datelor comunitare analitice și API în vrac în regiunea UE. Unii clienți pot vedea date de analiză lipsă sau întârziate din 27 iulie 2026. Lucrăm pentru a restabili datele afectate și va oferi o actualizare după validarea recuperării.

2. 30 iulie 2026 la 14:50 UTCidentified

   Problema a fost identificată și a fost inițiat un backfill pentru datele lipsă.

3. 30 iulie 2026 la 23:49 UTCidentified

   Reumplerea datelor este în curs de desfășurare și continuăm să monitorizăm recuperarea datelor privind analizele comunitare și API în regiunea UE. Vom furniza o altă actualizare odată ce firul de date a fost completat și recuperarea datelor a fost validată.

4. 31 iulie 2026 la 01:30 UTCmonitoring

   Reumplerea datelor a fost finalizată cu succes. În prezent validăm faptul că toate datele privind analizele comunitare și API lipsesc au fost restaurate integral în regiunea UE. Vom continua monitorizarea serviciului.

5. 31 iulie 2026 la 05:42 UTCresolved

   Problema care afectează analiza comunitară și prelucrarea zilnică a datelor API în regiunea UE a fost rezolvată. Reumplerea datelor a fost finalizată cu succes.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 13:25 UTCidentified

   Investigăm în prezent o problemă care afectează US Care Analytics/Search. Cauza principală a fost identificată, iar eforturile de atenuare sunt în curs de desfășurare. Vom furniza noi actualizări pe măsură ce se fac progrese.

2. 27 iulie 2026 la 14:38 UTCidentified

   Continuăm să restaurăm o componentă care sprijină Care Analytics și anumite funcții de integrare CRM. Disponibilitatea serviciilor se îmbunătăţeşte pe măsură ce restaurarea progresează. În acest timp, unii utilizatori pot experimenta erori intermitente atunci când încarcă înregistrări CRM legate sau cartografieri de câmp în panoul de integrare CRM. Datele de analiză de îngrijire pot fi, de asemenea, întârziate, indisponibile sau incomplete în timpul recuperării.

3. 27 iulie 2026 la 20:14 UTCresolved

   Problema care are impact asupra Analizelor de Îngrijire din SUA a fost rezolvată. O mică parte din datele din Care Analytics pot fi, de asemenea, întârziate, indisponibile sau incomplete în timpul recuperării.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iulie 2026 la 18:45 UTCinvestigating

   Investigăm performanţe degradate în întreaga regiune a UE care cauzează eşecuri intermitente ale fluxului către sistemul de securitate, ceea ce ar putea împiedica predarea de boturi, răspunsurile clienţilor, actualizările programului de lucru şi acţiunile temporizator/rezolvare să se finalizeze în mod fiabil.

2. 9 iulie 2026 la 19:26 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 9 iulie 2026 la 20:47 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 8 iulie 2026 la 17:45 UTCinvestigating

   Investigăm întârzieri intermitente care afectează unii clienți Khoros Care, în cazul în care noi contacte pot dura mai mult decât de obicei să apară în cozi, numărul cozilor poate afișa inexact, iar acțiunile agent, cum ar fi atribuirea de cazuri sau trimiterea de răspunsuri pot fi lente. Ingestia de mesaje nu este afectată și nu se pierd date Echipa noastră lucrează activ pentru a rezolva acest lucru și va partaja actualizările pe măsură ce acestea devin disponibile.

2. 8 iulie 2026 la 19:46 UTCidentified

   Am identificat cauza problemei actuale și aplicăm soluții imediate pentru a reduce impactul. În weekend vor fi puse în aplicare soluții permanente suplimentare pentru rezolvarea completă a problemei. Vom continua să partajăm actualizările pe măsură ce acestea devin disponibile.

3. 9 iulie 2026 la 12:11 UTCmonitoring

   Am aplicat dispozitive de infrastructură peste noapte în timpul unei ferestre cu trafic redus. Din această dimineață, indicatorii de performanță pentru îngrijirea UE au revenit la normal și au rămas stabili până în orele de vârf. Monitorizăm activ toată ziua pentru a confirma stabilitatea. Menţinerea preventivă suplimentară este programată pentru weekend-ul următor în timpul orelor de vârf.

4. 10 iulie 2026 la 02:43 UTCresolved

   Nu am mai observat alte probleme de performanţă. Această problemă este acum rezolvată.

Traducere automată din actualizarea oficială a incidentului.

1. 1 iulie 2026 la 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 iulie 2026 la 10:08 UTCmonitoring

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

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

   This incident has been resolved

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

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

3. 30 iunie 2026 la 21:09 UTCmonitoring

   We continue monitoring the results of the implemented fix

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

   This incident has been resolved

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

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

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

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

4. 24 iunie 2026 la 11:23 UTCresolved

   This incident has been resolved.

1. 15 iunie 2026 la 15:28 UTCidentified

   Am identificat cauza principală și punem în aplicare măsuri de recuperare.

2. 15 iunie 2026 la 21:40 UTCmonitoring

   Am rezolvat problema şi am completat analiza lipsă.

3. 18 iunie 2026 la 02:50 UTCmonitoring

   Am completat datele pentru toate zilele lipsă şi continuăm să monitorizăm orice altă problemă.

4. 22 iunie 2026 la 03:22 UTCmonitoring

   Continuăm să monitorizăm acest lucru pentru a ne asigura că lucrurile arată bine.

5. 22 iunie 2026 la 14:31 UTCmonitoring

   Nu am observat alte probleme în timpul perioadei de monitorizare. Sistemul continuă să funcţioneze conform aşteptărilor şi vom continua monitorizarea pentru a asigura stabilitatea.

6. 23 iunie 2026 la 04:08 UTCmonitoring

   Menţinem monitorizarea noastră pentru a confirma stabilitatea continuă şi va oferi actualizări după cum este necesar.

7. 24 iunie 2026 la 14:37 UTCmonitoring

   Monitorizarea continuă să confirme stabilitatea în curs de desfășurare și vom oferi actualizări după cum este necesar.

8. 26 iunie 2026 la 11:10 UTCmonitoring

   Vom continua monitorizarea pentru a confirma stabilitatea în curs și va oferi actualizări, dacă este necesar.

9. 29 iunie 2026 la 02:35 UTCmonitoring

   Vom continua monitorizarea pentru a confirma stabilitatea în curs și va oferi actualizări, după caz.

10. 30 iunie 2026 la 03:44 UTCmonitoring

    Întreaga Comunitate Reumplerile analitice au fost finalizate, iar datele curg conform aşteptărilor. Am identificat un decalaj rămas în indicatorii de înregistrare datând din 21 mai. Echipa noastră lucrează activ pentru aceste date. Vom continua să oferim actualizări cu privire la progresele realizate în vederea completării acestei rezerve.

11. 1 iulie 2026 la 04:21 UTCmonitoring

    Înregistrarea backfill-uri este încă în curs. Echipa noastră continuă să lucreze pentru a completa aceste date. Următoarea actualizare va fi furnizată în 24 de ore.

12. 1 iulie 2026 la 23:58 UTCmonitoring

    Înregistrarea se completează în continuare. Echipa noastră continuă să lucreze prin diferența de date rămasă și va oferi o altă actualizare pe măsură ce se înregistrează progrese.

13. 2 iulie 2026 la 23:34 UTCmonitoring

    Recuperarea lacunelor din datele analitice a fost finalizată. Validarea a confirmat faptul că datele afectate sunt disponibile din nou și că nu s-a identificat nicio recurență suplimentară pentru acest incident. Orice urmărire specifică mediului sau separată legată de metric va continua să fie urmărită în afara acestui incident. Vom continua monitorizarea acestui fix pentru următoarele 24 de ore. Mulţumesc pentru răbdare.

14. 3 iulie 2026 la 03:19 UTCmonitoring

    Reumplerea indicatorilor de înregistrare în analiza comunitară rămâne în curs de desfășurare. Datele de înregistrare pentru perioada de decalaj identificată anterior sunt restabilite și se confirmă recuperarea parțială. Vom continua monitorizarea și va oferi o actualizare odată ce backfill este complet.

15. 4 iulie 2026 la 06:58 UTCmonitoring

    În prezent, nu sunt observate probleme legate de umplere. Continuăm să monitorizăm acest lucru.

16. 5 iulie 2026 la 12:57 UTCmonitoring

    Echipa noastră rămâne angajată în monitorizare pentru a asigura stabilitatea continuă și va posta actualizări după cum este necesar.

17. 7 iulie 2026 la 09:01 UTCmonitoring

    Echipa noastră rămâne angajată în monitorizare pentru a asigura stabilitatea continuă și va posta actualizări pe măsură ce apar.

18. 8 iulie 2026 la 07:51 UTCmonitoring

    Echipa noastră rămâne angajată în monitorizare pentru a asigura stabilitatea continuă a clienților noștri.

19. 8 iulie 2026 la 12:56 UTCresolved

    Întreaga Comunitate Reumplerile de analiză au fost acum finalizate, inclusiv indicatorii rămași. Nu au fost identificate lacune suplimentare de date legate de acest incident. Vă mulțumim pentru răbdare în timp ce echipele noastre au finalizat munca de recuperare și validare.

Traducere automată din actualizarea oficială a incidentului.

1. 12 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 la 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 la 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 la 08:39 UTCidentified

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

4. 30 mai 2026 la 08:39 UTCidentified

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

5. 1 iunie 2026 la 17:10 UTCidentified

   The backfilling process is progressing as expected.

6. 2 iunie 2026 la 03:52 UTCidentified

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

7. 2 iunie 2026 la 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 iunie 2026 la 03:51 UTCidentified

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

9. 4 iunie 2026 la 18:46 UTCidentified

   The team continues working on the remediation.

10. 5 iunie 2026 la 03:31 UTCidentified

    The remediation effort is ongoing by our teams.

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

    We are continuing to monitor for any further issues.

13. 6 iunie 2026 la 20:14 UTCresolved

    The incident has been resolved.

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

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

3. 28 mai 2026 la 15:22 UTCmonitoring

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

4. 28 mai 2026 la 19:18 UTCmonitoring

   We are continuing to monitor for any further issues.

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

   This incident has been resolved.

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

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

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

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

6. 28 mai 2026 la 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 la 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 la 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 la 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 iunie 2026 la 04:17 UTCresolved

    This incident has been resolved.

1. 25 mai 2026 la 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 la 01:59 UTCidentified

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

3. 25 mai 2026 la 09:13 UTCidentified

   The fix for the issue is under review.

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

   We continue monitoring pipeline stability.

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

    The incident with APAC hosted communities is resolved.

1. 20 mai 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 20:00 UTCmonitoring

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

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

   We will continue monitoring the system to ensure stability.

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

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

4. 20 mai 2026 la 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 la 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 la 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 la 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 la 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 la 04:58 UTCresolved

   The incident has been resolved.