Is Piano.io down?

We are currently experiencing a delay in data generation for yesterday on Piano Analytics. Daily scheduled exports may be still pending to be sent. Hourly and dataflow exports are not affected by the problem. Our technical teams are actively working to resolve the issue. Please excuse us for any inconvenience caused.

We are continuing to investigate this issue.

A fix has been implemented and data recovery is currently underway (already completed for around 90% of customers).

We are continuing to monitor for any further issues.

The issue has been resolved and the delay in data generation has now been caught up. All scheduled exports have been sent.

**Incident explanation** * Due to inconsistencies in our delivery process, two services with incompatible versions were deployed to production during a full redelivery of all services, aimed at quickly resolving a security vulnerability * These services are part of our data ingestion pipeline, which became blocked. As all consolidation and aggregation jobs depend on this step, they could not be computed, delaying data availability. ‌ **Action performed** * Both services were rolled back to their last stable versions, which unblocked the process. ‌ **Actions to come** * Strengthen validation of this part of the pipeline during deliveries. Set up an on-call rotation for the D-1 data feed \(details to be defined\).

We are currently experiencing a production incident on Piano Analytics products. Please excuse us for any inconvenience caused.

The incident has been resolved and is no longer affecting Piano Analytics. We apologise for the inconvenience caused.

**Incident explanation:** Snowflake outage affecting multiple core Snowflake services and features. (AWS - Europe (Ireland))Many of Snowflake's services were unavailable, which affected part of the data processing chain, certain types of exports, and the analytics API.Incident Report : https://status.snowflake.com/incidents/bfh045zclk5k **Actions performed:** Monitoring the situation while awaiting the fix from Snowflake, along with several actions on our end aimed at resolving issues caused by this incident (fixing data processing delays on our end, fixing delays in certain exports, etc.).

Between approximately 18:00 UTC and 20:21 UTC on October 21, 2026, some users were unable to log in to the Piano ESP dashboard, as the login page was timing out. Some new newsletter sign-ups may also not have been recorded during this time. The issue was caused by a disruption at an external service provider. A fix has been deployed and the ESP dashboard is now operating normally. We apologize for the inconvenience.

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.

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.

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.

**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.