Plainly Outage History

Started Oct 02, 2026, 10:46 AM UTC· resolved Oct 02, 2026, 12:54 PM UTC

1. identified Oct 02, 2026, 10:46 AM UTC

   We're seeing errors connecting to our integrations provider. Setting up integrations and integration-triggered actions may fail for now. Video rendering, projects, templates and the API are not affected. We've found the cause: a certificate configuration change on the provider's side. We're working with them on a fix. We'll post an update within the next few hours or as soon as we know more.

2. monitoring Oct 02, 2026, 11:16 AM UTC

   We've deployed a temporary fix and integrations are working again. We're monitoring to make sure everything stays stable, and we're still working with our integrations provider on a permanent fix on their side.

3. resolved Oct 02, 2026, 12:54 PM UTC

   We are marking the incident as resolved. Systems are fully operational, and we will continue working with the service provider on a permanent fix on their side.

Read the full incident report →

Started Apr 22, 2026, 06:44 PM UTC· resolved Apr 23, 2026, 01:19 PM UTC

1. investigating Apr 22, 2026, 06:44 PM UTC

   Web app is currently unreachable due to a communication failure between our GCP cluster and our authentication provider. We are actively investigating and will provide an update shortly.

2. investigating Apr 22, 2026, 06:57 PM UTC

   The issue has been identified as a temporary problem on Google Cloud Platform affecting communication between our cluster and authentication provider. Service has been restored and we are continuing to monitor for stability.

3. monitoring Apr 22, 2026, 07:01 PM UTC

   After further investigation, we have confirmed that API users were not affected at any point during this incident. Impact was limited to web app access only. We continue to monitor.

4. resolved Apr 23, 2026, 01:19 PM UTC

   Issue resolved.

Read the full incident report →

Started Mar 19, 2026, 09:49 AM UTC· resolved Mar 20, 2026, 03:16 PM UTC

1. investigating Mar 19, 2026, 09:49 AM UTC

   We are currently investigating an issue where integrations are not functioning correctly. Multiple customers have reported problems with triggering renders and delivery workflows.

2. monitoring Mar 19, 2026, 10:43 AM UTC

   A fix has been deployed, and integrations are now recovering. We are monitoring the system to ensure stability.

3. resolved Mar 20, 2026, 03:16 PM UTC

   The issue is fully resolved.

Read the full incident report →

Started Feb 11, 2026, 04:36 PM UTC· resolved Feb 12, 2026, 03:46 PM UTC

1. investigating Feb 11, 2026, 04:36 PM UTC

   We are currently experiencing delays in retries for render webhook calls that do not return a successful response. While retries normally occur every 15 minutes, the retry interval is not guaranteed at this time. During this incident, the retry interval may be extended to up to 3 hours. We are actively working to restore the standard retry schedule.

2. identified Feb 11, 2026, 05:46 PM UTC

   We have identified the issue. We will move webhook retries to an exponential backoff strategy to ensure more reliable retry behavior.

3. identified Feb 12, 2026, 01:43 PM UTC

   The fix has been implemented and tested in the staging environment. It will be deployed to production later today as part of a new release.

4. resolved Feb 12, 2026, 03:46 PM UTC

   The issue has been resolved. Webhook retries are now functioning normally and use exponential backoff delays.

Read the full incident report →

Started Dec 05, 2025, 08:29 AM UTC· resolved Dec 08, 2025, 09:47 AM UTC

1. investigating Dec 05, 2025, 08:29 AM UTC

   We are currently investigating an issue affecting all integrations that use a file upload step. Workflows that upload a video file as part of an integration are currently not proceeding to the file download and upload steps. Other functionality remains operational. We are working to identify the root cause and will provide an update as soon as possible. Affected integrations include: Vimeo, YouTube, Google Drive, OneDrive, Dropbox, all S3-compatible storages, Signed URL uploads, etc.

2. monitoring Dec 05, 2025, 01:29 PM UTC

   The issue affecting integrations that use a file upload has been resolved. All workflows should now proceed normally. We are continuing to monitor system performance and will apply additional configurations to improve stability and prevent similar disruptions.

3. monitoring Dec 06, 2025, 07:05 AM UTC

   We are still observing occasional sporadic degradations and will continue to monitor the system closely over the weekend while additional stability improvements are applied.

4. resolved Dec 08, 2025, 09:47 AM UTC

   We have not observed any issues in the last 24 hours and all integrations are operating normally. The incident is now considered resolved, and no further impact is expected. Thank you for your patience.

Read the full incident report →

Started Nov 06, 2025, 09:24 AM UTC· resolved Nov 12, 2025, 08:54 AM UTC

1. investigating Nov 06, 2025, 09:24 AM UTC

   We’re currently investigating an issue with integrations not working as expected. Our team is in contact with the integration service provider to understand more and will share updates as soon as we have additional information.

2. identified Nov 06, 2025, 01:02 PM UTC

   The integration service provider has identified the issue causing integrations to fail. We’re waiting for their next update and will continue to monitor the situation closely.

3. identified Nov 07, 2025, 07:23 AM UTC

   The integration service provider has identified the root cause of the issue, but the fix is taking longer than initially expected to be applied. We’re staying in close contact with them and will continue to provide updates as progress is made.

4. identified Nov 07, 2025, 07:53 AM UTC

   Our integration service provider shared the following update: “We are experiencing an infrastructure-related outage that has extended beyond our initial recovery estimate. Our full DevOps team is actively working on manual recovery procedures, with management oversight to ensure this issue receives absolute priority.” We’ll continue to share updates as we receive them. As a gesture of goodwill, we’re happy to refund any rendering usage during the incident. Please contact our support team if you were affected.

5. identified Nov 07, 2025, 10:54 AM UTC

   Latest update from the integration service provider: "We’ve fixed the root cause affecting our Ceph cluster, and the cluster is now being restored. The issue turned out to be a bug in ceph cluster, where the Python sub-interpreter used by the mgr modules wasn’t loading plugins correctly. In the meantime, our team has fixed the manager side and is working on restoring the broken OSDs. We expect this to take the next 2-3 hours."

6. identified Nov 07, 2025, 03:35 PM UTC

   Another update from the integration service provider: "We’re still working on the broken OSDs — it’s taking longer than expected to get them all back online."

7. identified Nov 09, 2025, 08:39 AM UTC

   The integration service provider’s infrastructure outage is still ongoing, and unfortunately, we haven’t received a recent update from their team. We’ve reached out multiple times and are awaiting further information on recovery progress. We understand how disruptive this is and sincerely apologize for the extended downtime. We’ll continue to share updates as soon as we receive new information.

8. identified Nov 10, 2025, 09:46 AM UTC

   The integration service provider has prepared a new cluster and started moving affected customers to the new cluster. We’re hopeful the work will be completed by the end of the day and will share updates as soon as integration services are back online.

9. identified Nov 11, 2025, 08:44 AM UTC

   We just received information from our integration service provider that new AWS infrastructure is ready, and tenant restoration will begin today in phases. We’ve been assured that the service will be fully restored today, and we’ll share updates as progress continues.

10. monitoring Nov 11, 2025, 06:29 PM UTC

    The issue has been resolved, and we’re now moving into the monitoring phase. We urge all customers to check their integrations and ensure connected accounts are working properly, as integrations may fail if any accounts are disconnected. A detailed post-incident report will be shared once the incident is fully closed.

11. resolved Nov 12, 2025, 08:54 AM UTC

    The integration service has been fully restored, and after an extended monitoring period, we’re closing this incident. We sincerely apologize for the disruption this caused and thank all affected customers for their patience and understanding throughout the outage. Going forward, we’ll implement several improvements to strengthen reliability and transparency: - Improve user notifications in case of integration service failures. Currently, these alerts did not trigger because the system responsible for notifications was also impacted. - Add a notification when an integration cannot be triggered after a successful rendering. - Provide some integrations as built-in features (e.g., signed URL uploads, form-based render triggering, and others) to reduce dependency on third-party services. - Adopt a more proactive update policy for third-party software to stay on the latest stable versions.

Read the full incident report →

Started Jul 23, 2025, 07:31 AM UTC· resolved Jul 24, 2025, 01:27 PM UTC

1. investigating Jul 23, 2025, 07:31 AM UTC

   We’re currently experiencing issues with our integrations caused by an error in rendered video file processing. Our team is actively working with the integration service provider to identify and resolve the root cause. We’ll share updates as soon as we have more information.

2. investigating Jul 23, 2025, 08:03 AM UTC

   Upon further investigation, we’ve identified that the video processing error may have affected some users and integrations intermittently over the past few days, not just during the current incident window. We are expanding our diagnostics and continuing to work closely with the integration provider to ensure a complete resolution.

3. identified Jul 23, 2025, 10:23 AM UTC

   The integration service provider has identified the root cause of the issue. While the permanent fix is still pending deployment, we’ve implemented temporary measures that have improved overall system stability in the meantime. We’re continuing to monitor performance closely and will share another update once the fix is fully rolled out.

4. monitoring Jul 23, 2025, 12:28 PM UTC

   The integration service provider has deployed the fix, and the issue has now been resolved. All affected integrations are functioning normally. We will continue to monitor the system to ensure ongoing stability.

5. monitoring Jul 23, 2025, 12:54 PM UTC

   Although a fix was deployed by the integration service provider, it has proven to be insufficient. We are still seeing degraded system performance, and some integrations continue to be affected. We’re actively collaborating with the provider on a more robust solution and will share further updates as progress is made.

6. monitoring Jul 23, 2025, 03:00 PM UTC

   System performance is gradually stabilizing, and error rates have begun to decrease. We continue to monitor the situation closely in collaboration with the integration service provider to ensure full recovery and long-term stability.

7. monitoring Jul 24, 2025, 10:01 AM UTC

   While the immediate issue has been resolved, the incident remains open as we work on strengthening our monitoring systems. We're actively improving detection and alerting for integration-related errors to ensure we can respond faster in the future. System performance remains stable, and we’ll provide another update once these improvements are fully implemented.

8. resolved Jul 24, 2025, 01:27 PM UTC

   The issue impacting integrations has been fully resolved. All systems are operating normally and integrations are working as expected. To improve our response and transparency in the future, we are taking the following actions: - Improving monitoring to detect integration errors earlier. - Implementing user notifications to alert when their integrations encounter issues. We’ll continue to monitor the system to ensure ongoing stability. Thank you for your patience during this incident.

Read the full incident report →