Is Piano.io down?

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.

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.

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

An API ingress configuration issue has been detected. Rollback to previous version has been applied to solve the problem.

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

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.

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.

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.

This incident has been resolved.