8月14日 EMEA 区域分析数据缺失
Issues轻微事件
受影响的组件
AnalyticsEU Hosted Communities
- monitoring
自8月14日以来,我们已经确定并确定了一个影响分析的问题,我们正在努力回填数据.
- monitoring
8月14日至16日缺失的分析数据已成功恢复. 我们正在继续监测下一个处理周期,以确保报告仍然及时.
- resolved
这一事件已经得到解决。 如果你遇到问题 请毫不犹豫地联系我们的支援队.
自动翻译自官方事件更新。
61 Khoros incidents · 2025年11月 — official updates, affected components, duration and resolution details.
自8月14日以来,我们已经确定并确定了一个影响分析的问题,我们正在努力回填数据.
8月14日至16日缺失的分析数据已成功恢复. 我们正在继续监测下一个处理周期,以确保报告仍然及时.
这一事件已经得到解决。 如果你遇到问题 请毫不犹豫地联系我们的支援队.
自动翻译自官方事件更新。
我们确定了一个影响欧盟区域共同体分析数据和散装数据API数据日常处理的问题。 一些顾客可能看到2026年7月27日以来缺失或延迟了分析数据. 我们正在努力恢复受影响的数据,并将在恢复得到证实后提供最新情况.
这一问题已经确定,并已开始对缺失的数据进行回填.
数据回填正在进行中,我们正在继续监测欧盟区域共同体分析数据和散装数据API数据的恢复情况。 一旦回填完成并验证数据回收情况,我们将再次提供最新情况.
数据回填已成功完成 。 我们目前正在核实,欧盟区域已完全恢复了所有缺失的共同体分析数据和散装数据API数据。 我们将继续监测这项服务.
影响欧盟地区共同体分析和散装数据API日常处理的问题已经解决. 数据回填已成功完成 .
自动翻译自官方事件更新。
我们目前正在调查一个影响美国医疗分析/搜索的问题。 其根源已经确定,缓解努力正在进行。 我们将随着进展提供进一步的最新资料.
我们正在继续恢复一个支持“护理分析”和某些客户关系管理整合职能的部分。 随着恢复工作的进行,服务供应正在改善。 在此期间,一些用户在CRM集成面板上加载链接的CRM记录或场地映射时可能会有间歇出错. 在康复期间,护理分析数据也可能被延迟、无法获得或不完整.
影响美国医疗分析/搜索的问题已经解决。 在康复期间,护理分析数据的一小部分也可能被延迟、无法获得或不完整.
自动翻译自官方事件更新。
我们正在调查整个欧盟区域的退化表现,造成间歇性的流动-护理故障,这可能会妨碍瓶子的取出、客户的反应、工作流程更新和定时器/解决行动可靠地完成.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查影响一些Khoros Care客户的间歇性延误,在这些客户中,新联系人可能需要比通常更长的时间才能出现在队列中,队列计数可能显示不准确,诸如分配案件或张贴答复等代理行为可能缓慢。 信息摄取不受影响,也没有丢失数据——这些问题只影响能见度和代理工作流程. 我们的团队正在积极努力解决这一问题,并将在获得最新情况后分享.
我们已查明造成目前问题的原因,并正在立即采取补救措施来减少影响。 周末将执行更多的永久措施来充分解决这一问题。 我们将继续在获得最新情况后予以分享.
我们在一个低流量窗口里用过一夜时间就修复了基础设施。 自今天上午以来,欧盟关爱的绩效衡量标准已恢复正常,并在高峰时段保持稳定。 我们每天积极监测,以确认稳定。 计划下个周末在非高峰时间进行额外的预防性维修.
我们没有看到进一步的业绩问题。 这个问题现已得到解决.
自动翻译自官方事件更新。
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
Our engineering team has implemented a fix for this and we are monitoring to confirm stability.
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.
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.
This incident has been resolved
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.
A fix has been implemented and we are monitoring the results.
We continue monitoring the results of the implemented fix
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.
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.
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.
This incident has been resolved
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.
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.
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.
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.
This incident has been resolved, and the old content has been successfully synchronized.
We are currently investigating an issue affecting Care Message Analytics, resulting in incomplete analytics data. We will provide updates as the investigation progresses.
The issue has been resolved. We continue to monitor the communities and ensure that the services have been fully re-established.
We continue to monitor the communities and ensure that the services have been fully re-established.
This incident has been resolved.
我们查明了根源,并正在执行恢复措施.
我们已经解决这个问题,并填补了缺失的分析.
我们已经回填了所有缺失日的数据,并继续监测任何进一步的问题.
我们继续对此进行监测,以确保情况良好.
我们在监测期间没有看到任何其他问题。 该系统继续按预期运作,我们将继续监测以确保稳定.
我们正在维持我们的监测,以确认目前的稳定,并将根据需要提供最新情况.
监测继续证实目前稳定,我们将视需要提供最新情况.
我们继续进行监测,以确认目前的稳定,并在需要时提供最新情况.
我们继续进行监测,以确认目前的稳定,并将根据需要提供最新情况.
全社区 分析回填已经完成,数据正按预期流动。 我们已查明在登记指标方面尚有差距,可追溯到5月21日。 我们的团队正在积极为这些数据进行回填。 我们将继续提供最新资料,说明在完成这一回填方面取得的进展.
登记指标的回填仍在进行中。 我们的小组继续努力完成这一数据。 下一次更新将在24小时内提供.
登记指标的回填工作仍在进行中。 我们的小组正在继续填补剩余的数据空白,并将随着进展提供又一最新情况.
分析数据差距的恢复工作已经完成。 鉴定确认,再次获得受影响数据,未发现此事件再发生. 在这一事件之外,将继续跟踪任何与环境有关或与衡量标准有关的其余后续行动。 我们将在今后24小时内继续监测这项措施。 谢谢你的耐心.
社区分析中登记指标的回填工作仍在进行中。 正在恢复以前确定的间隔期的登记数据并证实部分恢复。 我们将继续进行监测,并在填满后提供最新情况.
目前未发现回填问题。 我们正在继续监测这一情况.
我们的小组继续参与监测,以确保持续稳定,并将视需要公布最新情况.
我们的小组继续参与监测工作,以确保持续稳定,并将随时公布最新情况.
我们的小组继续参与监测工作,以确保我们的客户持续稳定.
全社区 分析回填工作现已完成,包括其余的衡量标准。 没有发现与这一事件有关的进一步数据缺口。 谢谢你的耐心 在我们的团队完成恢复和验证工作时.
自动翻译自官方事件更新。
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.
Meta is currently experiencing high disruptions impacting Messenger API for Instagram, Facebook and Whatsapp, which in turn is impacting Khoros message ingestion activities.
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.
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.
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.
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.
Data has been backfilled up to the 27th. We continue to backfill the remaining two days.
We continue to backfill data for May 28th and 29th.
The backfilling process is progressing as expected.
We are continuing to monitor the backfilling status. No issues have been encountered.
Our team is currently working on the required remediation. We will share the next update as soon as additional progress is made.
The remediation effort remains underway. We will share the next update as soon as there is more to report.
The team continues working on the remediation.
The remediation effort is ongoing by our teams.
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.
We are continuing to monitor for any further issues.
The incident has been resolved.
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.
We are continuously working on a fix and actively monitoring the situation.
Our infrastructure team has applied a fix for the MFA issue and we are monitoring the results.
We are continuing to monitor for any further issues.
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.
This incident has been resolved.
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.
The Infrastructure team is working on backfilling the analytics data for AMER-hosted communities.
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.
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.
We are continuously working on a fix and actively monitoring the situation.
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.
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.
Our Infrastructure team continues to work on restoring data for the remaining affected dates. We will provide further updates as progress is made.
All affected dates have been successfully backfilled. Please reach out to us if you are still experiencing any issues or require further assistance.
This incident has been resolved.
We are currently investigating an issue affecting Community Analytics data for APAC-hosted communities from May 19 onwards.
The issue has been identified, and our team is working on fixing it.
The fix for the issue is under review.
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.
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.
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.
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.
We continue monitoring pipeline stability.
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.
The incident with APAC hosted communities is resolved.
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.
We have identified the issue causing Google My Business (GMB) reviews to fail, and our Engineering team are currently working on a fix.
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.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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
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.
We will continue monitoring the system to ensure stability.
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.
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.
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.
The backfill has been completed. We continue to investigate the root cause.
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.
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.
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.
We have observed some continued delays in post ingestion after our original fix, and we are investigating the cause.
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.
The incident has been resolved.