Historial de interrupciones de Khoros

1. August 17, 2026 at 10:21 AM UTCmonitoring

   Hemos identificado y arreglado un problema que afecta a la analítica desde el 14 de agosto, estamos trabajando en el respaldo de los datos.

2. August 18, 2026 at 12:05 AM UTCmonitoring

   Los datos de análisis desaparecidos del 14 al 16 de agosto han sido restaurados con éxito. Seguimos monitoreando el próximo ciclo de procesamiento para asegurar que la presentación de informes siga siendo actual.

3. August 18, 2026 at 11:27 AM UTCresolved

   Este incidente ha sido resuelto. si encuentras problemas por favor no dudes en contactar con nuestro equipo de soporte.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 30, 2026 at 1:44 PM UTCinvestigating

   Hemos identificado un problema que afecta el procesamiento diario de los datos de API de datos de análisis comunitario y a granel en la región de la UE. Algunos clientes pueden ver datos de análisis perdidos o retrasados desde el 27 de julio de 2026. Trabajamos para restaurar los datos afectados y proporcionaremos una actualización una vez validada la recuperación.

2. July 30, 2026 at 2:50 PM UTCidentified

   Se ha identificado la cuestión y se ha iniciado un backfill para los datos faltantes.

3. July 30, 2026 at 11:49 PM UTCidentified

   El backfill de datos está actualmente en marcha, y seguimos monitoreando la recuperación de los datos de la API de datos Community Analytics y Bulk en la región de la UE. Proporcionaremos otra actualización una vez que se haya completado el backfill y se haya validado la recuperación de datos.

4. July 31, 2026 at 1:30 AM UTCmonitoring

   El backfill de datos se ha completado con éxito. Actualmente estamos validando que todos los datos que faltan Community Analytics y Bulk Data API se han restaurado completamente en la región de la UE. Seguiremos vigilando el servicio.

5. July 31, 2026 at 5:42 AM UTCresolved

   Se ha resuelto el problema que afecta al procesamiento diario de la API de datos de la comunidad y de gran alcance en la región de la UE. El backfill de datos se ha completado con éxito.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 1:25 PM UTCidentified

   Actualmente estamos investigando un problema que afecta a US Care Analytics/Search. Se ha identificado la causa raíz y se están realizando esfuerzos de mitigación. Proporcionaremos nuevas actualizaciones a medida que se avance.

2. July 27, 2026 at 2:38 PM UTCidentified

   Continuamos restaurando un componente que apoya las funciones de integración de Care Analytics y ciertas funciones de CRM. La disponibilidad de servicios está mejorando a medida que avanza la restauración. Durante este tiempo, algunos usuarios pueden experimentar errores intermitentes al cargar registros de CRM conectados o mapas de campo en el panel de integración CRM. Los datos de Care Analytics también pueden retrasarse, no estar disponibles o estar incompletos mientras se complete la recuperación.

3. July 27, 2026 at 8:14 PM UTCresolved

   Se ha resuelto el problema que afecta a US Care Analytics/Search. Una pequeña parte de los datos de Care Analytics también puede retrasarse, no estar disponible o incompleta mientras se completa la recuperación.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 6:45 PM UTCinvestigating

   Estamos investigando el rendimiento degradado en toda la región de la UE, causando fallos intermitentes de flujo a carta, lo que puede impedir que se completen de forma fiable las entregas de bot, las respuestas de los clientes, las actualizaciones de las carpetas de trabajo y las medidas de temporización y resolución.

2. July 9, 2026 at 7:26 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 9, 2026 at 8:47 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 8, 2026 at 5:45 PM UTCinvestigating

   Estamos investigando retrasos intermitentes que afectan a algunos clientes de Khoros Care, donde los nuevos contactos pueden tardar más de lo habitual en aparecer en colas, los recuentos de cola pueden mostrar inexactamente, y acciones de agentes como la asignación de casos o la publicación de respuestas pueden ser lentas. La ingestión de mensajes no se ve afectada y no se pierden datos: estos problemas afectan la visibilidad y el flujo de trabajo de los agentes solamente. Nuestro equipo está trabajando activamente para resolver esto y compartirá actualizaciones a medida que estén disponibles.

2. July 8, 2026 at 7:46 PM UTCidentified

   Hemos identificado la causa del problema actual y estamos aplicando correcciones inmediatas para reducir el impacto. Durante el fin de semana se aplicarán correcciones permanentes adicionales para resolver plenamente el problema. Seguiremos compartiendo actualizaciones a medida que estén disponibles.

3. July 9, 2026 at 12:11 PM UTCmonitoring

   Hemos aplicado correcciones de infraestructura durante toda la noche durante una ventana de bajo tráfico. Desde esta mañana, las métricas de rendimiento para la atención de la UE han regresado a la normalidad y han permanecido estables a través de horas pico. Estamos monitoreando activamente durante todo el día para confirmar la estabilidad. El mantenimiento preventivo adicional está programado para el próximo fin de semana durante horas libres.

4. July 10, 2026 at 2:43 AM UTCresolved

   No hemos observado más problemas de desempeño. Esta cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 1, 2026 at 9:15 AM 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. July 1, 2026 at 10:08 AM UTCmonitoring

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

3. July 1, 2026 at 11:58 PM 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. July 2, 2026 at 11:44 PM 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. July 3, 2026 at 3:26 AM UTCresolved

   This incident has been resolved

1. June 30, 2026 at 11:54 AM 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. June 30, 2026 at 12:24 PM UTCmonitoring

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

3. June 30, 2026 at 9:09 PM UTCmonitoring

   We continue monitoring the results of the implemented fix

4. June 30, 2026 at 11:51 PM 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. June 30, 2026 at 1:08 AM 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. June 30, 2026 at 2:05 AM 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. June 30, 2026 at 3:28 AM UTCresolved

   This incident has been resolved

1. June 29, 2026 at 12:40 PM 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. June 29, 2026 at 1:11 PM 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. June 29, 2026 at 2:52 PM 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. June 29, 2026 at 11:52 PM 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. June 30, 2026 at 2:45 PM UTCresolved

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

1. June 23, 2026 at 11:54 AM 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. June 23, 2026 at 8:41 PM UTCmonitoring

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

3. June 24, 2026 at 3:04 AM UTCmonitoring

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

4. June 24, 2026 at 11:23 AM UTCresolved

   This incident has been resolved.

1. June 15, 2026 at 3:28 PM UTCidentified

   Hemos identificado la causa raíz y estamos aplicando medidas de recuperación.

2. June 15, 2026 at 9:40 PM UTCmonitoring

   Hemos resuelto el problema y respaldamos el análisis que falta.

3. June 18, 2026 at 2:50 AM UTCmonitoring

   Hemos respaldado los datos durante todos los días desaparecidos y seguimos monitoreando para cualquier otra cuestión.

4. June 22, 2026 at 3:22 AM UTCmonitoring

   Seguimos monitoreando esto para asegurar que las cosas se vean bien.

5. June 22, 2026 at 2:31 PM UTCmonitoring

   No hemos observado ninguna otra cuestión durante el período de vigilancia. El sistema sigue funcionando según lo previsto, y seguiremos vigilando para garantizar la estabilidad.

6. June 23, 2026 at 4:08 AM UTCmonitoring

   Mantenemos nuestro monitoreo para confirmar la estabilidad continua y proporcionaremos actualizaciones según sea necesario.

7. June 24, 2026 at 2:37 PM UTCmonitoring

   La vigilancia sigue confirmando la estabilidad en curso y proporcionaremos actualizaciones según sea necesario.

8. June 26, 2026 at 11:10 AM UTCmonitoring

   Seguimos monitoreando para confirmar la estabilidad en curso y proporcionaremos actualizaciones si es necesario.

9. June 29, 2026 at 2:35 AM UTCmonitoring

   Seguimos monitoreando para confirmar la estabilidad en curso y proporcionaremos actualizaciones según sea necesario.

10. June 30, 2026 at 3:44 AM UTCmonitoring

    Toda la comunidad Se han completado los retrocesos analíticos y los datos fluyen según se espera. Hemos identificado una brecha restante en las métricas de registro que datan del 21 de mayo. Nuestro equipo está trabajando activamente en el backfill para estos datos. Seguiremos proporcionando información actualizada sobre los progresos realizados para completar este backfill.

11. July 1, 2026 at 4:21 AM UTCmonitoring

    El backfill de métricas de registro sigue en curso. Nuestro equipo continúa trabajando para completar estos datos. La próxima actualización se proporcionará en 24 horas.

12. July 1, 2026 at 11:58 PM UTCmonitoring

    El backfill de métricas de registro sigue en curso. Nuestro equipo continúa trabajando a través de la brecha de datos restante y proporcionará otra actualización a medida que se avance.

13. July 2, 2026 at 11:34 PM UTCmonitoring

    Se ha completado la recuperación de los datos analíticos. La validación ha confirmado que los datos afectados están disponibles de nuevo, y no se ha identificado más recurrencia para este incidente. Cualquier seguimiento relacionado con el medio ambiente o la métrica restante seguirá siendo rastreado fuera de este incidente. Seguiremos monitoreando esta solución durante las próximas 24 horas. Gracias por su paciencia.

14. July 3, 2026 at 3:19 AM UTCmonitoring

    El backfill for Registration metrics in Community Analytics sigue en curso. Se están restableciendo los datos de registro para el período de diferencia identificado anteriormente y se confirma la recuperación parcial. Seguiremos monitorizando y proporcionaremos una actualización una vez que el backfill esté completo.

15. July 4, 2026 at 6:58 AM UTCmonitoring

    Actualmente no se observan problemas con los backfills. Continuamos monitoreando esto.

16. July 5, 2026 at 12:57 PM UTCmonitoring

    Nuestro equipo sigue trabajando en la vigilancia para garantizar la estabilidad continua y publicará actualizaciones según sea necesario.

17. July 7, 2026 at 9:01 AM UTCmonitoring

    Nuestro equipo sigue comprometido en la vigilancia para garantizar la estabilidad continua y publicará actualizaciones a medida que aparezcan.

18. July 8, 2026 at 7:51 AM UTCmonitoring

    Nuestro equipo sigue comprometido en la vigilancia para garantizar la estabilidad continua de nuestros clientes.

19. July 8, 2026 at 12:56 PM UTCresolved

    Toda la comunidad Se han completado los retrocesos analíticos, incluyendo las métricas restantes. No se han identificado más lagunas de datos relacionadas con este incidente. Gracias por su paciencia mientras nuestros equipos completaron el trabajo de recuperación y validación.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 12, 2026 at 2:09 PM 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. June 12, 2026 at 3:29 PM 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. June 12, 2026 at 9:17 PM 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. June 15, 2026 at 2:23 AM 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. May 29, 2026 at 3:07 PM 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. May 29, 2026 at 11:58 PM 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. May 30, 2026 at 8:39 AM UTCidentified

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

4. May 30, 2026 at 8:39 AM UTCidentified

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

5. June 1, 2026 at 5:10 PM UTCidentified

   The backfilling process is progressing as expected.

6. June 2, 2026 at 3:52 AM UTCidentified

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

7. June 2, 2026 at 11:54 PM UTCidentified

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

8. June 4, 2026 at 3:51 AM UTCidentified

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

9. June 4, 2026 at 6:46 PM UTCidentified

   The team continues working on the remediation.

10. June 5, 2026 at 3:31 AM UTCidentified

    The remediation effort is ongoing by our teams.

11. June 5, 2026 at 11:34 AM 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. June 5, 2026 at 8:01 PM UTCmonitoring

    We are continuing to monitor for any further issues.

13. June 6, 2026 at 8:14 PM UTCresolved

    The incident has been resolved.

1. May 28, 2026 at 6:38 AM 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. May 28, 2026 at 2:24 PM UTCinvestigating

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

3. May 28, 2026 at 3:22 PM UTCmonitoring

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

4. May 28, 2026 at 7:18 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. May 28, 2026 at 11:54 PM 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. May 29, 2026 at 3:19 AM UTCresolved

   This incident has been resolved.

1. May 27, 2026 at 4:17 AM 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. May 27, 2026 at 11:01 AM UTCinvestigating

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

3. May 27, 2026 at 11:48 PM 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. May 28, 2026 at 6:19 AM 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. May 28, 2026 at 2:25 PM UTCidentified

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

6. May 28, 2026 at 7:18 PM 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. May 29, 2026 at 3:28 AM 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. May 29, 2026 at 8:59 PM 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. May 30, 2026 at 7:52 AM 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. June 1, 2026 at 4:17 AM UTCresolved

    This incident has been resolved.

1. May 25, 2026 at 1:06 AM UTCinvestigating

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

2. May 25, 2026 at 1:59 AM UTCidentified

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

3. May 25, 2026 at 9:13 AM UTCidentified

   The fix for the issue is under review.

4. May 26, 2026 at 12:23 AM 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. May 26, 2026 at 8:17 AM 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. May 26, 2026 at 11:16 PM 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. May 27, 2026 at 4:01 AM 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. May 27, 2026 at 10:59 AM UTCmonitoring

   We continue monitoring pipeline stability.

9. May 27, 2026 at 11:50 PM 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. May 28, 2026 at 2:29 AM UTCresolved

    The incident with APAC hosted communities is resolved.

1. May 20, 2026 at 9:31 PM 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. May 20, 2026 at 11:05 PM 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. May 21, 2026 at 4:43 AM 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. May 21, 2026 at 12:58 PM 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. May 22, 2026 at 3:09 AM 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. May 22, 2026 at 10:23 AM 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. May 22, 2026 at 8:00 PM UTCmonitoring

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

8. May 24, 2026 at 10:17 PM 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. May 20, 2026 at 2:59 PM 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. May 20, 2026 at 9:36 PM 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. May 21, 2026 at 4:31 AM 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. May 22, 2026 at 1:12 AM 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. May 22, 2026 at 10:34 AM UTCmonitoring

   We will continue monitoring the system to ensure stability.

6. May 24, 2026 at 10:20 PM 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. May 18, 2026 at 9:50 AM 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. May 18, 2026 at 10:00 AM 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. May 18, 2026 at 9:09 PM UTCmonitoring

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

4. May 20, 2026 at 2:17 AM 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. May 13, 2026 at 4:00 PM 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. May 14, 2026 at 2:51 AM 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. May 14, 2026 at 9:21 PM UTCinvestigating

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

4. May 14, 2026 at 10:39 PM 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. May 15, 2026 at 4:58 AM UTCresolved

   The incident has been resolved.