[钢琴观众] SSL 证书出错影响透视访问
Issues轻微事件
受影响的组件
Piano Audience - Insight
- monitoring
钢琴找出了影响一些用户获取钢琴洞察力的问题. 导致出错的证书被更新,并进行了内部验证. 我们正在监测,以确认这一问题已完全解决,不久将进一步通报最新情况.
- monitoring
我们正在继续监测任何其他问题.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
57 Pianoio incidents · 2025年8月 — official updates, affected components, duration and resolution details.
钢琴找出了影响一些用户获取钢琴洞察力的问题. 导致出错的证书被更新,并进行了内部验证. 我们正在监测,以确认这一问题已完全解决,不久将进一步通报最新情况.
我们正在继续监测任何其他问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在经历一个报告生成问题。 我们的团队意识到并积极努力解决这个问题.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
自动翻译自官方事件更新。
钢琴正在经历一个影响欧盟区域用户登录和注册的问题。 登录窗口可能无法打开, 也可能没有响应 。 我们已经确定了原因,我们的团队正在部署一个固定方案。 我们将在获得进一步资料后立即分享最新情况.
钢琴已经确认,这一问题影响到所有区域的登录和登记,而不仅仅是最初报告的欧盟。 所有区域的用户都可能遇到同样的症状——登录窗口无法打开,或者变得没有反应. 我们的团队继续部署修复方案。 我们将在获得进一步资料后立即分享最新情况。 受影响的组件: 注册+登录 - US - id.piano.io 登记+登录 - 澳大利亚 - id-au.piano.io 注册+登录 - 亚洲 - id-ap.piano.io 登记+登录 - 欧盟 - id.piano.io
我们正在继续努力解决这个问题。
钢琴可以证实这个问题实际上只会影响美国和欧盟地区以及沙盒环境. AP和非盟不受影响。 我们对先前的更新所造成的任何混乱表示歉意。 Sandbox没有专门的状态页面组件,因为它不是生产基础设施的一部分,这个更新是为能见度提供的. 我们的团队继续部署修复方案。 我们将在获得进一步资料后立即分享最新情况.
钢琴已经在所有受影响的区域和环境,包括沙盒实施了一个固定方案。 登入和注册功能已经恢复并正常运行. 我们将继续监测局势,并在出现任何问题时提供进一步的最新情况.
这一事件已经得到解决.
事件的RCA可参见[**此链接**](https://rca.piano.io/wp-content/uploads/2026/07/2026-07-27-RCA-IDentity-Management-login-issues.pdf).
自动翻译自官方事件更新。
在AP区域最近安排的数据库维护之后,我们发现有一个数据缺口,影响到出版商Dashboard的订阅日志和订阅透视部分。 一些客户可能注意到最近的采购尚未在订阅日志报告中反映出来,而订阅洞察中的一些测量数据可能看起来暂时不一致. 我们的小组正在重新生成受影响的数据,并期望在今后几天内解决这个问题。 一旦掌握更多信息,我们将立即分享最新情况.
一项措施已经执行,我们正在监测结果.
我们已经恢复了用于订阅透视的受影响数据,现在应该正确显示那里的测量数据。 订阅日志报告尚未完全收回,这一观点中可能仍然缺少一些最近的购买。 我们的团队继续重新生成剩余的数据. 一旦掌握更多信息,我们将立即分享最新情况.
影响订阅日志的数据差距现已完全解决,AP区域最近的所有采购都在报告中得到正确反映。 加上早先的订阅"洞察"的修补,"出版机Dashboard"两个受影响的区域都已经恢复正常. 这一事件现在已经得到解决。 谢谢你的耐心 在我们完成数据再生时.
自动翻译自官方事件更新。
我们正在调查一个影响在亚洲和澳大利亚为出版商提供付费墙和经验的问题。 一些请求未能成功完成。 我们的工程队正在积极工作,找出根源,恢复正常服务。 一旦掌握更多信息,我们将立即分享最新情况.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
影响我们东京数据中心后端系统依赖性的一个内部基础设施问题造成了认证失败,从而导致对Auditence API的请求失败。 由于亚洲(AP)和澳大利亚(AU)路线的作曲家流量通过这一实例,这两个区域都遇到了作曲家请求的失败. 这一事件已经得到解决。 我们的工程小组查明了原因并恢复了受影响的系统;所有区域的服务都恢复正常。 我们对此可能造成的不便表示歉意.
自动翻译自官方事件更新。
我们正在观察由于管理cx前缀和作曲应用程序ID的数据改进工作造成的用户配置后端数据处理延迟。 如果您使用cxense的外部配置更新API(https://api.cxense.com/profile/user/external/update),您在使用同一配置读取时会看到1-2小时的延迟(https://api.cxense.com/profile/user/external/update). 我们的团队正在将数据调回一个单一的正确视图,这种调和是持续拖延的根源. 没有丢失任何数据,所有事件都在处理之中,目前大约延迟1至2小时。 我们对此不便表示歉意,并将通报最新进展,因为积压情况已查明
数据处理延迟在用户配置文件后端继续进行,目前延迟1至2小时。 我们已查明,最近的数据变化导致少数客户的数据量大幅增加,这是积压的主要驱动因素。 我们的团队正在仔细地增加处理的吞吐量,同时密切监测整个系统的稳定,以避免提出更多的问题。 我们对尽快稳定局势感到乐观,一旦我们掌握了更多信息,我们将提供最新情况.
Piano Audence用户简介后端的数据处理已恢复近实时,并清理了积压. 我们正在将这一事件归为 " 监测 " ,而我们的小组则完成先前数据变化的剩余清理工作。 一旦事件完全解决,我们将分享进一步的最新情况.
该事件经过超过24小时的监测后已经得到解决. 我们看到实时处理数据
自动翻译自官方事件更新。
我们正在观察由于管理cx前缀和作曲应用程序ID的数据改进工作而导致的用户配置后缀数据处理延迟。 如果您使用cxense的外部配置更新API(https://api.cxense.com/profile/user/external/update),您在使用同一配置读取时会看到1-2小时的延迟(https://api.cxense.com/profile/user/external/update). 我们的团队正在将数据调回一个单一的正确视图,这种调和是持续拖延的根源. 没有丢失任何数据,所有事件都在处理之中,目前大约延迟1至2小时。 我们对此不便表示歉意,并将通报最新进展,因为积压情况已查明
我们正在继续努力解决这个问题。
自动翻译自官方事件更新。
We are currently experiencing a minor service disruption affecting user logins to the Piano dashboards, caused by an ongoing outage on Cloudflare's side. Our team is actively monitoring the situation. We apologize for any inconvenience this may cause and appreciate your patience. Further updates will be provided as soon as more information becomes available. For reference: https://www.cloudflarestatus.com/incidents/v3yl7jqmqj51
The incident has been mitigated, along with our provider's resolution. We will continue to monitor the situation.
This incident has been resolved.
Since approximately 11:00 PM (UTC) on June 8, 2026, there have been intermittent delays loading files into Snowflake. The average load duration is currently about 10 minutes, compared to the usual under 2 minutes. The issue has been identified and a ticket has been opened with Snowflake.
The incident has been resolved and is no longer affecting Piano Analytics. We apologise for the inconvenience caused.
**Incident explanation:** The latency was caused by an issue on our cloud data platform provider's side. An internal infrastructure configuration change introduced resource contention that affected workloads with high ingestion concurrency, leading to elevated response times and intermittent timeouts when loading files. The change has been reverted by the provider, and ingestion performance has fully returned to its normal baseline. **Actions performed:** Opened and tracked an incident with our data platform provider and provided detailed monitoring evidence to support their investigation. Deployed mitigations on our streaming ingestion stack (increased service scaling and improved handling of stalled ingestion calls) to limit customer impact during the incident. Temporarily tuned ingestion timeout and retry settings to keep file loading as stable as possible while the root cause was being addressed. Continuously monitored ingestion latency and error rates until performance returned to normal. Confirmed full recovery, then reverted the temporary configuration to restore standard behaviour and avoid masking any future issues. **Actions to come:** Continued close monitoring of ingestion latency over the coming days to confirm lasting stability. Keep the temporary mitigation patterns configurable in the code so they can be re-applied quickly should a similar provider-side degradation occur.
We are currently experiencing an issue with the Content Crawler, which is failing to crawl content. Our team is actively investigating the root cause. We will provide further updates as more information becomes available.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and all Content pipeline services have been restored. Some processing delays may persist while the crawling backlog clears. We will continue to monitor and confirm full resolution.
This incident has been resolved.
RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/06/2026-05-29-RCA-Content-Crawler-Service-Disruption-1.pdf).
We identified an issue in our systems starting around 10:20 UTC that is currently degrading CXSense platform responsiveness over the /public/user/id endpoint. As a result, some users may experience failed requests, while others may experience longer response times and timeouts. Our engineering team is actively investigating and working on mitigation efforts. We will continue to provide updates as more information becomes available.
A fix has been implemented and we are currently monitoring the results. At this time, API performance has returned to normal operation levels and the platform is behaving as expected again. We will continue monitoring closely to ensure stability.
This incident has been resolved.
RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/06/2026-05-28-RCA-Audience-API-Failures-happening-in-Europe-environment.pdf).
On 20 May 2026, starting at approximately 09:58 UTC, we identified an issue affecting Piano Activation in the US environment, impacting the Dashboard, Piano ID authentication, and checkout flows. A fix has been applied and the platform is now operating normally. We are continuing to monitor the situation and further details will follow. We apologise for any inconvenience caused.
The incident has been resolved. All services are operating normally. Between approximately 09:58 and 10:11 UTC, users in the US region may have experienced issues accessing the Piano Dashboard, signing in via Piano ID, or completing checkout flows. This was caused by a routine configuration update to our US environment that introduced a conflict and disrupted traffic routing to the affected services. Our team identified the issue, rolled back the change, and confirmed full recovery shortly after. To prevent this from happening again, we are reviewing our release process and will validate the change in a controlled manner before re-applying it. We apologize for the inconvenience and thank you for your patience.
We are currently experiencing degraded performance across the Publisher Dashboard in the AP environment, with data taking up to 3 hours longer than usual to reflect recent changes. This may affect any section of the Dashboard — including user search, reporting, and other data views. Our engineering team has identified the underlying cause and is actively working on a resolution. We will provide updates as the situation progresses.
This incident has been resolved.
We are currently investigating issues affecting the execution of experiences in our European region for segmentation that relies on custom field rules. Impacted users may notice that experiences are not triggering as expected, not reaching the desired outcome. Our engineering team is actively investigating the issue.
The issue has been identified and fixed; we're currently monitoring the experience executions.
This incident has been resolved.
An infrastructure update to the EU environment introduced an incompatibility that prevented Composer from retrieving Custom Fields. The issue was limited to the EU region and did not affect other environments. The update introduced a behavioural change in the network routing layer where a configuration setting that had previously been relied upon was no longer honoured under the new setup. This incompatibility was not detected during pre-production testing, as the test environments did not fully replicate the conditions needed to surface the issue. The root cause was identified and the configuration gap was addressed promptly. Piano is taking steps to improve parity between pre-production and production environments and to strengthen the validation process ahead of future infrastructure changes to prevent similar issues.
Between 07:42 and 07:52 AM UTC, Piano experienced elevated error rates affecting the Publisher API and ID API in the EU environment. The incident occurred during an ingress upgrade from a deprecated version to the current supported version, which caused a routing configuration incompatibility. The issue lasted approximately 10 minutes and has been fully resolved. Publisher Dashboard, Checkout, and access controls in Composer operated normally throughout the incident and were not affected.
We are currently experiencing a production incident on Piano Analytics products. Please excuse us for any inconvenience caused.
The issue has been resolved and all Piano Analytics tools and interfaces are fully available. We are currently catching up the delay in real-time data retrieval.
Composer is experiencing a service incident affecting C1X segmentation in both EU and US regions. Impact includes high error rates, degraded segment lookup, and degraded widget performance. The issue started at approximately 22:00 UTC on May 7 and continues with periods of instability. Our team is actively investigating the issue.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
We are currently experiencing an issue with Composer in our sandbox environment; the Composer module and experiences fail to load. Our team has identified the root cause and is actively working to resolve the issue. We will provide updates as more information becomes available.
The team has deployed a fix, and the issue has been resolved. Experiences are executing, and the Composer module is working normally. We will continue monitoring the remediation.
We are continuing to monitor for any further issues.
This incident has been resolved.
Between 06:48 and 07:05 UTC, Piano ID API experienced elevated error rates in the US cluster. Requests requiring user authentication, token verification, and user profile retrieval were affected. Other Piano services including Composer and VX subscription management were not impacted. Service has been fully restored and all systems are operating normally. We apologize for any disruption caused during this incident.
This incident has been resolved.
We have found an issue with our priority rules for API interaction on server/edge in Composer. The dev team is currently investigating. Clients may find their list order being changed or unsorted without any user interaction. We will continue updating this incident once we identify the root cause.
Our team has restored the priority rules to their pre-incident state while we continue to investigate the root cause. We advise customers to avoid making changes to priority rules until the investigation is complete. We will provide further updates as more information becomes available.
The issue has been identified and mitigated; we will continue monitoring the remediation.
This incident has been resolved.
RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/04/2025-05-06-RCA-Experience-Priority-Data-Incident.pdf).