- Detected by Pingoru
- Oct 16, 2026, 06:54 AM UTC
- Resolved
- Oct 16, 2026, 03:51 PM UTC
- Duration
- 8h 57m
Timeline · 1 update
-
resolved Oct 21, 2026, 06:12 AM UTC
Between approximately 06:54 and 15:51 UTC on October 16, posts sent to LinkedIn through SocialFlow failed to publish, and collection of LinkedIn post statistics was also affected. The issue was caused by a change on LinkedIn's side and has been resolved. Publishing and statistics collection have worked normally since 15:51 UTC. Posts that failed during this window were not retried automatically and will need to be rescheduled. No reauthentication of LinkedIn pages is required.
Read the full incident report →
- Detected by Pingoru
- Oct 12, 2026, 07:13 AM UTC
- Resolved
- Oct 12, 2026, 08:15 AM UTC
- Duration
- 1h 1m
Affected: SocialFlow publishingFeed Fetcher
Timeline · 3 updates
-
investigating Oct 12, 2026, 07:13 AM UTC
We are currently investigating an issue affecting automated publishing in SocialFlow. Clients may see new content from their feeds not appearing in publishing queues, and automated posts not being published to social networks, including X. The issue has been occurring since approximately October 10. Manual posting continues to work. Our engineering team is actively working to identify the root cause. We will share an update as soon as we have more information.
-
resolved Oct 12, 2026, 08:15 AM UTC
This incident has been resolved. Automated publishing in SocialFlow is working normally again, and new content from feeds is appearing in publishing queues and being posted to connected social networks. We apologize for any inconvenience caused.
-
postmortem Oct 12, 2026, 08:33 AM UTC
**Root cause:** An internal component responsible for retrieving content from client feeds stopped processing on October 10 and was not automatically restarted. This reduced the amount of content reaching the publishing system, and automated posts to connected social networks were delayed or not published. Posts scheduled directly by users were not affected. **Resolution:** The component was restarted on October 12 at 07:20 UTC, and publishing returned to normal. Content that had been queued was published shortly afterwards. **Next steps:** We are improving our monitoring and automated recovery so that this type of issue is detected and resolved faster. We apologize for the disruption.
Read the full incident report →
Notice September 21, 2026 - Detected by Pingoru
- Sep 21, 2026, 02:30 PM UTC
- Resolved
- Sep 21, 2026, 04:26 PM UTC
- Duration
- 1h 56m
Timeline · 1 update
-
resolved Sep 24, 2026, 08:33 AM UTC
Between 14:53 and 16:26 UTC on September 21, Piano experienced an issue affecting the publishing of posts to X. During this period, affected posts failed to send and, after a limited number of automatic retries, were reported back as failed rather than published, with error notifications sent to the affected accounts. Posts that failed during this window were not sent retroactively once service was restored and need to be published again. The cause was an internal configuration change made during planned monitoring work, which has been reverted. Publishing to X has been fully restored.
Read the full incident report →
Notice September 14, 2026 - Detected by Pingoru
- Sep 14, 2026, 12:38 PM UTC
- Resolved
- Sep 14, 2026, 01:08 PM UTC
- Duration
- 29m
Timeline · 2 updates
-
investigating Sep 14, 2026, 12:38 PM UTC
We are currently experiencing a production incident on Piano Analytics products. Please excuse us for any inconvenience caused.
-
resolved Sep 14, 2026, 01:08 PM UTC
An API ingress configuration issue has been detected. Rollback to previous version has been applied to solve the problem.
Read the full incident report →
Notice September 14, 2026 - Detected by Pingoru
- Sep 14, 2026, 12:38 PM UTC
- Resolved
- Sep 14, 2026, 12:58 PM UTC
- Duration
- 20m
Timeline · 2 updates
-
investigating Sep 14, 2026, 12:38 PM UTC
We are currently experiencing a production incident on Piano Analytics products. Please excuse us for any inconvenience caused.
-
resolved Sep 14, 2026, 12:58 PM UTC
Some problematic behavior relative to authorization was active on production when it should have been disabled from the start. Problematic network annotation have been desactivated for production environment.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2026, 09:28 AM UTC
- Resolved
- Sep 10, 2026, 10:14 AM UTC
- Duration
- 46m
Affected: Composer Experience Execution - USComposer Experience Execution - Europe
Timeline · 3 updates
-
monitoring Sep 10, 2026, 09:28 AM UTC
Piano has identified an issue affecting access checks in Composer for users in the US and EU regions, which began at approximately 06:49 UTC. The underlying cause has been addressed and access checks have been fully restored. Our team will continue to monitor the situation closely and will provide a further update should any issues arise.
-
monitoring Sep 10, 2026, 10:14 AM UTC
This incident has been resolved. Access checks in Composer were affected between 06:45 and 07:39 UTC in the US region, and between 07:10 and 07:34 UTC in the EU region. Alongside the access check errors, a proportion of requests to the affected services also returned errors during the same periods. All affected functionality has been fully restored and no further errors have been observed.
-
resolved Sep 10, 2026, 10:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 07:30 PM UTC
- Resolved
- Sep 09, 2026, 10:03 AM UTC
- Duration
- 14h 33m
Timeline · 1 update
-
resolved Sep 11, 2026, 11:01 AM UTC
Between 23:12 UTC on September 8 and 10:03 UTC on September 9, Piano experienced an issue affecting automated publishing from content feeds. During this period, configured RSS feeds could not be fetched, and feed-based posts were not published to Facebook or X. Articles released while the issue was active may not have been posted automatically to the affected social accounts. The underlying issue has been addressed and feed collection and publishing have been fully restored. Our team continues to work on measures to prevent a recurrence.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 07:43 AM UTC
- Resolved
- Aug 26, 2026, 08:26 PM UTC
- Duration
- 12h 42m
Affected: Composer Experience Execution - USAPI Endpoints - cxense - api.cxense.com
Timeline · 3 updates
-
investigating Aug 26, 2026, 07:43 AM UTC
We are currently investigating an issue affecting personalized content and audience segmentation for users on our US environment. Some users may see missing or outdated personalization data, including issues with audience segments and user profile data used for targeting. The issue began around 05:00 UTC. Our engineering team is actively working to identify the root cause. We will share an update as soon as we have more information.
-
monitoring Aug 26, 2026, 08:32 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 26, 2026, 08:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 03:31 PM UTC
- Resolved
- Aug 24, 2026, 06:04 PM UTC
- Duration
- 2h 32m
Affected: Composer Experience Execution - USAPI Endpoints - cxense - api.cxense.com
Timeline · 3 updates
-
investigating Aug 24, 2026, 03:31 PM UTC
We are currently investigating an issue affecting personalized content and audience segmentation for users on our US environment. Some users may see missing or outdated personalization data, including issues with audience segments and user profile data used for targeting. Our engineering team is actively working to identify the root cause. We will share an update as soon as we have more information.
-
monitoring Aug 24, 2026, 04:46 PM UTC
The API availability is improving and is expected to fully recover soon. We will update the status page once it is restored.
-
resolved Aug 24, 2026, 06:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 05:08 AM UTC
- Resolved
- Aug 24, 2026, 09:15 AM UTC
- Duration
- 4h 7m
Affected: Piano ESP Email Distribution
Timeline · 4 updates
-
investigating Aug 24, 2026, 06:44 AM UTC
We are currently investigating an issue affecting the delivery of emails and push notifications for ESP users. Our engineering team is actively working to identify the root cause. We will share an update as soon as we have more information.
-
identified Aug 24, 2026, 07:47 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Aug 24, 2026, 07:54 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 24, 2026, 09:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 15, 2026, 09:00 AM UTC
- Resolved
- Aug 15, 2026, 09:24 AM UTC
- Duration
- 23m
Affected: Piano Audience - Insight
Timeline · 3 updates
-
monitoring Aug 15, 2026, 09:00 AM UTC
Piano identified an issue affecting access to Piano Insight for some users. The certificate causing the errors has been renewed, and the fix has been verified internally. We are monitoring to confirm the issue is fully resolved and will share a further update shortly.
-
monitoring Aug 15, 2026, 09:12 AM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 15, 2026, 09:24 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 10:01 AM UTC
- Resolved
- Aug 05, 2026, 12:40 PM UTC
- Duration
- 2h 38m
Affected: Other
Timeline · 3 updates
-
investigating Aug 05, 2026, 10:01 AM UTC
We are experiencing an issue with report generation. Our team is aware and actively working to resolve it.
-
monitoring Aug 05, 2026, 10:59 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 05, 2026, 12:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 08:30 AM UTC
- Resolved
- Jul 27, 2026, 02:50 PM UTC
- Duration
- 6h 19m
Affected: Registration + Login - US - id.piano.ioRegistration + Login - Australia - id-au.piano.ioRegistration + Login - Asia - id-ap.piano.ioRegistration + Login - EU - id.piano.io
Timeline · 7 updates
-
identified Jul 27, 2026, 08:30 AM UTC
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.
-
identified Jul 27, 2026, 08:34 AM UTC
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
-
identified Jul 27, 2026, 08:35 AM UTC
We are continuing to work on a fix for this issue.
-
identified Jul 27, 2026, 08:57 AM UTC
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.
-
monitoring Jul 27, 2026, 09:20 AM UTC
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.
-
resolved Jul 27, 2026, 02:50 PM UTC
This incident has been resolved.
-
postmortem Aug 03, 2026, 01:20 PM UTC
RCA for the incident can be found at [**this link**](https://rca.piano.io/wp-content/uploads/2026/07/2026-07-27-RCA-Identity-Management-login-issues.pdf).
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 07:51 AM UTC
- Resolved
- Jul 28, 2026, 12:22 AM UTC
- Duration
- 3d 16h
Affected: Publisher Dashboard - Asia - https://dashboard-ap.piano.io
Timeline · 4 updates
-
investigating Jul 24, 2026, 07:51 AM UTC
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.
-
monitoring Jul 27, 2026, 08:04 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 27, 2026, 08:39 AM UTC
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.
-
resolved Jul 28, 2026, 12:22 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 12:31 PM UTC
- Resolved
- Jul 23, 2026, 03:50 PM UTC
- Duration
- 3h 19m
Affected: Composer Experience Execution - AsiaComposer Experience Execution - AustraliaAPI Endpoints - cxense - api.cxense.com
Timeline · 4 updates
-
investigating Jul 23, 2026, 12:31 PM UTC
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.
-
identified Jul 23, 2026, 01:00 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 23, 2026, 01:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 23, 2026, 03:50 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 08:36 PM UTC
- Resolved
- Jul 24, 2026, 08:38 PM UTC
- Duration
- 4d
Affected: Piano Audience - User Profiles Backend
Timeline · 4 updates
-
identified Jul 20, 2026, 08:36 PM UTC
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
-
identified Jul 21, 2026, 11:52 AM UTC
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.
-
monitoring Jul 22, 2026, 06:30 AM UTC
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.
-
resolved Jul 24, 2026, 08:38 PM UTC
The incident has been resolved after monitoring for more than 24 hours. We are seeing the processing of the data in real-time
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 07:46 PM UTC
- Resolved
- Jul 20, 2026, 08:40 PM UTC
- Duration
- 53m
Affected: Piano Audience Dashboard
Timeline · 1 update
-
identified Jul 20, 2026, 07:46 PM UTC
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
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 02:59 PM UTC
- Resolved
- Jun 23, 2026, 01:02 AM UTC
- Duration
- 10h 3m
Affected: Publisher Dashboard - US - https://dashboard.piano.io
Timeline · 3 updates
-
investigating Jun 22, 2026, 02:59 PM UTC
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
-
monitoring Jun 22, 2026, 05:30 PM UTC
The incident has been mitigated, along with our provider's resolution. We will continue to monitor the situation.
-
resolved Jun 23, 2026, 01:02 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 09:52 AM UTC
- Resolved
- Jun 10, 2026, 09:55 AM UTC
- Duration
- 1d
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 02:31 AM UTC
- Resolved
- May 29, 2026, 02:03 PM UTC
- Duration
- 11h 32m
Affected: Piano Data Collection - Crawler
Timeline · 6 updates
-
investigating May 29, 2026, 02:31 AM UTC
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.
-
investigating May 29, 2026, 02:31 AM UTC
We are continuing to investigate this issue.
-
identified May 29, 2026, 08:39 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 29, 2026, 09:24 AM UTC
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.
-
resolved May 29, 2026, 02:03 PM UTC
This incident has been resolved.
-
postmortem Jun 04, 2026, 09:00 AM UTC
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).
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 04:27 PM UTC
- Resolved
- May 29, 2026, 03:53 AM UTC
- Duration
- 11h 25m
Affected: API Endpoints - cxense - api.cxense.com
Timeline · 4 updates
-
identified May 28, 2026, 04:27 PM UTC
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.
-
monitoring May 28, 2026, 05:10 PM UTC
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.
-
resolved May 29, 2026, 03:53 AM UTC
This incident has been resolved.
-
postmortem Jun 15, 2026, 09:25 AM UTC
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).
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 10:19 AM UTC
- Resolved
- May 20, 2026, 12:41 PM UTC
- Duration
- 2h 22m
Affected: Publisher Dashboard - US - https://dashboard.piano.ioCheckout - US - buy.piano.ioAPI Endpoints - US - api.piano.ioRegistration + Login - US - id.piano.io
Timeline · 2 updates
-
monitoring May 20, 2026, 10:19 AM UTC
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.
-
resolved May 20, 2026, 12:41 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 08:03 AM UTC
- Resolved
- May 16, 2026, 07:16 AM UTC
- Duration
- 23h 13m
Affected: Publisher Dashboard - Asia - https://dashboard-ap.piano.io
Timeline · 2 updates
-
identified May 15, 2026, 08:03 AM UTC
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.
-
resolved May 16, 2026, 07:16 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 01:48 PM UTC
- Resolved
- May 13, 2026, 06:00 PM UTC
- Duration
- 4h 11m
Affected: Composer Experience Execution - Europe
Timeline · 4 updates
-
investigating May 13, 2026, 01:48 PM UTC
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.
-
monitoring May 13, 2026, 02:02 PM UTC
The issue has been identified and fixed; we're currently monitoring the experience executions.
-
resolved May 13, 2026, 06:00 PM UTC
This incident has been resolved.
-
postmortem May 15, 2026, 09:39 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 07:42 AM UTC
- Resolved
- May 13, 2026, 07:52 AM UTC
- Duration
- 10m
Affected: API Endpoints - EU - api-eu.piano.ioRegistration + Login - EU - id.piano.io
Timeline · 1 update
-
resolved May 13, 2026, 08:52 AM UTC
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.
Read the full incident report →
