Is Piano.io down?

Piano is experiencing an issue affecting login and registration for users in the EU region. The login window may fail to open, or may be unresponsive. We have identified the cause and our team is deploying a fix. We will share an update as soon as further information is available.

Piano has identified that this issue affects login and registration across all regions, not only the EU as initially reported. Users in all regions may experience the same symptoms — the login window failing to open, or becoming unresponsive. Our team continues to deploy the fix. We will share an update as soon as further information is available. Affected components: Registration + Login - US - id.piano.io Registration + Login - Australia - id-au.piano.io Registration + Login - Asia - id-ap.piano.io Registration + Login - EU - id.piano.io

We are continuing to work on a fix for this issue.

Piano can confirm this issue in fact only affects the US and EU regions, as well as Sandbox environment. AP and AU are not affected. We apologize for any confusion caused by the earlier update. Sandbox does not have a dedicated status page component since it's not part of production infrastructure, this update is provided for visibility. Our team continues to deploy the fix. We will share an update as soon as further information is available.

Piano has implemented a fix across all affected regions and environments, including Sandbox. Login and registration functionality has been restored and is operating normally. We will continue to monitor the situation and will provide a further update should any issues arise.

This incident has been resolved.

Following recent scheduled database maintenance in the AP region, we have identified a data gap affecting the Subscription Log and Subscription Insights sections of the Publisher Dashboard. Some clients may notice that recent purchases are not yet reflected in the Subscription Log report, and some measurements in Subscription Insights may appear temporarily inconsistent. Our team is regenerating the affected data and expects this to be resolved within the next few days. We will share an update as soon as we have more information.

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

We have restored the affected data for Subscription Insights, and measurements there should now be displaying correctly. The Subscription Log report has not yet been fully recovered, and some recent purchases may still be missing from this view. Our team continues to regenerate the remaining data. We will share an update as soon as we have more information.

The data gap affecting the Subscription Log has now been fully resolved, and all recent purchases in the AP region are correctly reflected in the report. Combined with the earlier fix to Subscription Insights, both affected areas of the Publisher Dashboard have been restored to normal. This incident is now resolved. Thank you for your patience while we completed the data regeneration.

We are currently investigating an issue affecting the delivery of paywalls and experiences for publishers in Asia and Australia. Some requests are failing to complete successfully. Our engineering team is actively working to identify the root cause and restore normal service. We will share an update as soon as we have more information.

The issue has been identified and a fix is being implemented.

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

An internal infrastructure issue affecting a backend system dependency in our Tokyo data center caused authentication failures that cascaded into request failures for the Audience API. Because Composer traffic for Asia (AP) and Australia (AU) routes through this instance, both regions saw failures of Composer requests. This incident has been resolved. Our engineering team identified the cause and restored the affected system; service has returned to normal in all regions. We apologize for any inconvenience this may have caused.

We are observing data processing delays on the User profile backend caused by data improvement efforts for managing the cx prefix and the composer application ID. If you are using the cxense's external profile update API (https://api.cxense.com/profile/user/external/update) you will observe 1-2 hours of delays when reading the same profile using (https://api.cxense.com/profile/user/external/update). Our team is now reconciling the data back into a single, correct view, and this reconciliation is the source of the ongoing delay. No data has been lost, all events are being processed, currently with an approximate delay of 1–2 hours. We apologize for the inconvenience and will share an update as the backlog clear

Data processing delays continue on the User Profiles backend, with current delays of 1–2 hours. We have identified that a recent data change led to a significant increase in data volume for a subset of customers, which is the primary driver of the backlog. Our team is carefully increasing processing throughput while closely monitoring overall system stability to avoid introducing further issues. We are optimistic about stabilizing the situation soon and will share an update as soon as we have more information.

Data processing on the Piano Audience User Profiles backend has returned to near real-time and the backlog is cleared. We are setting this incident to Monitoring while our team completes residual cleanup from the earlier data change. We will share a further update once the incident is fully resolved.

The incident has been resolved after monitoring for more than 24 hours. We are seeing the processing of the data in real-time

We are observing data processing delays on the CDP caused by data improvement efforts for managing the cx prefix and the composer application ID. If you are using the cxense's external profile update API (https://api.cxense.com/profile/user/external/update) you will observe 1-2 hours of delays when reading the same profile using (https://api.cxense.com/profile/user/external/update). Our team is now reconciling the data back into a single, correct view, and this reconciliation is the source of the ongoing delay. No data has been lost, all events are being processed, currently with an approximate delay of 1–2 hours. We apologize for the inconvenience and will share an update as the backlog clear