Histórico de interrupções do Khoros

1. 17 Eost 2026 da 10:21 UTCmonitoring

   Identificamos e corrigimos um problema que afeta a análise desde 14 de agosto, estamos trabalhando no preenchimento dos dados.

2. 18 Eost 2026 da 00:05 UTCmonitoring

   Os dados de análise em falta para 14-16 de agosto foram restaurados com sucesso. Continuamos a acompanhar o próximo ciclo de processamento para garantir que os relatórios permaneçam em vigor.

3. 18 Eost 2026 da 11:27 UTCresolved

   Este incidente foi resolvido. se você encontrar problemas por favor não hesite em chegar à nossa equipe de suporte.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Gouere 2026 da 13:44 UTCinvestigating

   Identificámos uma questão que afecta o tratamento diário dos dados da API de análise comunitária e dados em massa na região da UE. Alguns clientes podem ver dados de análise ausentes ou atrasados desde 27 de julho de 2026. Estamos trabalhando para restaurar os dados afetados e fornecerá uma atualização uma vez que a recuperação foi validada.

2. 30 Gouere 2026 da 14:50 UTCidentified

   A questão foi identificada, e foi iniciado um backfilt para os dados em falta.

3. 30 Gouere 2026 da 23:49 UTCidentified

   O backfill de dados está actualmente em curso, e continuamos a monitorizar a recuperação dos dados da API comunitária de análise e dados em massa na região da UE. Nós forneceremos outra atualização uma vez que o backfill foi concluído e a recuperação de dados foi validada.

4. 31 Gouere 2026 da 01:30 UTCmonitoring

   O preenchimento dos dados foi concluído com sucesso. Atualmente, estamos validando que todos os dados da API da Community Analytics e Bulk Data foram totalmente restaurados na região da UE. Continuaremos a acompanhar o serviço.

5. 31 Gouere 2026 da 05:42 UTCresolved

   A questão que afecta o tratamento diário da API comunitária de análise e dados em massa na região da UE foi resolvida. O preenchimento de dados completou com sucesso.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 13:25 UTCidentified

   Atualmente estamos investigando um problema impactando o US Care Analytics/Search. A causa raiz foi identificada, e esforços de mitigação estão em andamento. Providenciaremos novas actualizações à medida que forem progredindo.

2. 27 Gouere 2026 da 14:38 UTCidentified

   Continuamos a restaurar um componente que suporta o Care Analytics e certas funções de integração CRM. A disponibilidade de serviços está melhorando à medida que a restauração avança. Durante este tempo, alguns usuários podem experimentar erros intermitentes ao carregar registros de CRM vinculados ou mapeamentos de campo no painel de integração de CRM. Os dados do Care Analytics também podem ser atrasados, indisponível ou incompletos enquanto a recuperação é concluída.

3. 27 Gouere 2026 da 20:14 UTCresolved

   O problema que impacta o US Care Analytics/Search foi resolvido. Uma pequena parte dos dados do Care Analytics também pode ser adiada, indisponível ou incompleta enquanto a recuperação é concluída.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 18:45 UTCinvestigating

   Estamos investigando o desempenho degradado em toda a região da UE, causando falhas intermitentes de fluxo a cuidado, o que pode impedir que as transferências de bots, as respostas dos clientes, as atualizações da fila de trabalho e as ações de temporizador/resolve completem de forma confiável.

2. 9 Gouere 2026 da 19:26 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 9 Gouere 2026 da 20:47 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gouere 2026 da 17:45 UTCinvestigating

   Estamos investigando atrasos intermitentes que afetam alguns clientes do Khoros Care, onde novos contatos podem levar mais tempo do que o normal para aparecer em filas, contagens de filas podem exibir imprecisamente, e ações de agentes, como atribuir casos ou postar respostas podem ser lentas. A ingestão de mensagens não é afetada e nenhum dado é perdido — essas questões impactam apenas a visibilidade e o fluxo de trabalho do agente. Nossa equipe está trabalhando ativamente para resolver isso e compartilhará atualizações conforme estiverem disponíveis.

2. 8 Gouere 2026 da 19:46 UTCidentified

   Identificámos a causa da questão actual e estamos a aplicar soluções imediatas para reduzir o impacto. Serão implementadas outras fixações permanentes durante o fim de semana para resolver plenamente o problema. Continuaremos a partilhar actualizações à medida que estiverem disponíveis.

3. 9 Gouere 2026 da 12:11 UTCmonitoring

   Nós aplicamos correções de infraestrutura durante a noite durante uma janela de baixo tráfego. Desde esta manhã, as métricas de desempenho para a EU Care voltaram ao normal e permaneceram estáveis ao longo das horas de pico. Estamos monitorando ativamente ao longo do dia para confirmar a estabilidade. Manutenção preventiva adicional está programada para o próximo fim de semana durante as horas fora do pico.

4. 10 Gouere 2026 da 02:43 UTCresolved

   Não observamos mais problemas de desempenho. Esta questão está agora resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 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 Gouere 2026 da 10:08 UTCmonitoring

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

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

   This incident has been resolved

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

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

3. 30 Mezheven 2026 da 21:09 UTCmonitoring

   We continue monitoring the results of the implemented fix

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

   This incident has been resolved

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

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

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

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

4. 24 Mezheven 2026 da 11:23 UTCresolved

   This incident has been resolved.

1. 15 Mezheven 2026 da 15:28 UTCidentified

   Identificámos a causa principal e estamos a implementar medidas de recuperação.

2. 15 Mezheven 2026 da 21:40 UTCmonitoring

   Resolvemos o problema e preenchemos as análises em falta.

3. 18 Mezheven 2026 da 02:50 UTCmonitoring

   Nós preenchemos os dados para todos os dias que faltam e continuamos a monitorar qualquer problema adicional.

4. 22 Mezheven 2026 da 03:22 UTCmonitoring

   Continuamos a acompanhar esta situação para garantir que as coisas estão a correr bem.

5. 22 Mezheven 2026 da 14:31 UTCmonitoring

   Não observámos quaisquer outras questões durante o período de monitorização. O sistema continua a funcionar como esperado, e continuaremos a monitorizar para garantir a estabilidade.

6. 23 Mezheven 2026 da 04:08 UTCmonitoring

   Estamos mantendo nosso monitoramento para confirmar a estabilidade contínua e forneceremos atualizações conforme necessário.

7. 24 Mezheven 2026 da 14:37 UTCmonitoring

   O monitoramento continua a confirmar a estabilidade contínua e forneceremos atualizações conforme necessário.

8. 26 Mezheven 2026 da 11:10 UTCmonitoring

   Continuamos monitorando para confirmar a estabilidade contínua e forneceremos atualizações se necessário.

9. 29 Mezheven 2026 da 02:35 UTCmonitoring

   Continuamos a monitorizar para confirmar a estabilidade contínua e forneceremos actualizações conforme necessário.

10. 30 Mezheven 2026 da 03:44 UTCmonitoring

    Toda a Comunidade Os backfills do Analytics foram completados, e os dados estão fluindo como esperado. Identificamos uma lacuna remanescente nas métricas de Registro que datam de 21 de maio. Nossa equipe está trabalhando ativamente no backfill para esses dados. Continuaremos a fornecer actualizações sobre os progressos realizados no sentido de completar este atraso.

11. 1 Gouere 2026 da 04:21 UTCmonitoring

    O preenchimento das métricas de registro ainda está em andamento. Nossa equipe continua trabalhando para completar esses dados. A próxima atualização será fornecida em 24 horas.

12. 1 Gouere 2026 da 23:58 UTCmonitoring

    O preenchimento das métricas de registro permanece em andamento. Nossa equipe continua trabalhando através da lacuna de dados remanescentes e fornecerá outra atualização à medida que o progresso é feito.

13. 2 Gouere 2026 da 23:34 UTCmonitoring

    A recuperação das lacunas de dados do Analytics foi concluída. A validação confirmou que os dados afetados estão novamente disponíveis, e nenhuma nova recorrência foi identificada para este incidente. Qualquer acompanhamento métrico específico para o ambiente ou separado continuará a ser rastreado fora deste incidente. Continuaremos a monitorizar esta solução nas próximas 24 horas. Obrigado pela vossa paciência.

14. 3 Gouere 2026 da 03:19 UTCmonitoring

    O backfill para métricas de registro em Community Analytics continua em andamento. Os dados de registo relativos ao período de abertura previamente identificado estão a ser restaurados e a recuperação parcial é confirmada. Continuaremos monitorando e forneceremos uma atualização assim que o preenchimento estiver completo.

15. 4 Gouere 2026 da 06:58 UTCmonitoring

    Nenhum problema é observado atualmente com os backfills. Continuamos a acompanhar esta situação.

16. 5 Gouere 2026 da 12:57 UTCmonitoring

    Nossa equipe continua envolvida no monitoramento para garantir a estabilidade contínua e publicará atualizações conforme necessário.

17. 7 Gouere 2026 da 09:01 UTCmonitoring

    Nossa equipe continua engajada em monitoramento para garantir estabilidade contínua e publicará atualizações à medida que surgirem.

18. 8 Gouere 2026 da 07:51 UTCmonitoring

    Nossa equipe continua engajada em monitoramento para garantir estabilidade contínua para nossos clientes.

19. 8 Gouere 2026 da 12:56 UTCresolved

    Toda a Comunidade Os backfills de análise já foram concluídos, incluindo as métricas restantes. Não foram identificadas mais lacunas de dados relacionadas com este incidente. Obrigado por sua paciência, enquanto nossas equipes completaram o trabalho de recuperação e validação.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 08:39 UTCidentified

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

4. 30 Mae 2026 da 08:39 UTCidentified

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

5. 1 Mezheven 2026 da 17:10 UTCidentified

   The backfilling process is progressing as expected.

6. 2 Mezheven 2026 da 03:52 UTCidentified

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

7. 2 Mezheven 2026 da 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 Mezheven 2026 da 03:51 UTCidentified

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

9. 4 Mezheven 2026 da 18:46 UTCidentified

   The team continues working on the remediation.

10. 5 Mezheven 2026 da 03:31 UTCidentified

    The remediation effort is ongoing by our teams.

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

    We are continuing to monitor for any further issues.

13. 6 Mezheven 2026 da 20:14 UTCresolved

    The incident has been resolved.

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

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

3. 28 Mae 2026 da 15:22 UTCmonitoring

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

4. 28 Mae 2026 da 19:18 UTCmonitoring

   We are continuing to monitor for any further issues.

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

   This incident has been resolved.

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

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

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

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

6. 28 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mezheven 2026 da 04:17 UTCresolved

    This incident has been resolved.

1. 25 Mae 2026 da 01:06 UTCinvestigating

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

2. 25 Mae 2026 da 01:59 UTCidentified

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

3. 25 Mae 2026 da 09:13 UTCidentified

   The fix for the issue is under review.

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

   We continue monitoring pipeline stability.

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

    The incident with APAC hosted communities is resolved.

1. 20 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 20:00 UTCmonitoring

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

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

   We will continue monitoring the system to ensure stability.

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

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

4. 20 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 21:21 UTCinvestigating

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

4. 14 Mae 2026 da 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 Mae 2026 da 04:58 UTCresolved

   The incident has been resolved.