Couchdrop Outage History

Couchdrop is up right now

Pingoru has recorded 14 incidents for Couchdrop: 2 in the last 12 months and 1 in the last 90 days.

Source: couchdropstatus.statuspage.io

14incidents recorded
2last 12 months
1last 90 days
42 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Couchdrop in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026142 of 744 (6%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 744 (0%)
November 202600 of 26 (0%)

Incidents, newest first

Notice October 22, 2026 Security Advisory: Critical PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619) - Not Affected – API, Movebot Admin, Couchdrop Web Admin, Orchestration System and 4 more

Started Oct 22, 2026, 06:35 PM UTC· resolved Oct 22, 2026, 06:35 PM UTC

  1. resolved Oct 22, 2026, 06:35 PM UTC

    Security Advisory: Critical PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619) Status: Not Affected On 21 October 2026, the PHP Security Team disclosed two critical vulnerabilities affecting the PHP runtime, identified as CVE-2026-109618 and CVE-2026-109619, collectively referred to as PHP2Shell. Both vulnerabilities carry a CVSS v4.0 severity score of 9.2 (Critical) and could allow unauthenticated attackers to execute arbitrary code on vulnerable servers. Impact on Couchdrop and Movebot We can confirm that neither Couchdrop nor Movebot is affected by these vulnerabilities. Neither platform uses PHP in any of its application components or underlying platform infrastructure. Consequently, these vulnerabilities do not present an exposure to either platform. Couchdrop: Not affected. Movebot: Not affected. Customer Data: No identified exposure resulting from these vulnerabilities. Service Availability: No impact. Customer Action Required: None. We continue to monitor emerging security threats and vulnerabilities as part of our ongoing security management processes.

Read the full incident report →

Minor May 18, 2026 Invalid upload failure notifications 1d 17h Couchdrop Web Admin, Upload/Download Portal, SFTP, FTP/FTPS

Started May 18, 2026, 06:31 AM UTC· resolved May 20, 2026, 12:06 AM UTC

  1. investigating May 18, 2026, 06:31 AM UTC

    We are currently investigating an issue causing incorrect Data Loss Prevention (DLP) alert notifications for some uploads. At this stage, uploads are continuing to process successfully, however some customers may receive erroneous “upload denied” notifications. Our engineering team has identified the issue and a fix is currently being deployed. We apologise for the confusion and will provide a further update shortly.

  2. monitoring May 18, 2026, 06:31 AM UTC

    A fix has been deployed and we are monitoring the situation

  3. resolved May 20, 2026, 12:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 18, 2025 Issue connecting to onedrive and sharepoint 1d 1h Upload/Download Portal, SFTP, Migrations/Transfers, FTP/FTPS

Started Oct 18, 2025, 06:43 PM UTC· resolved Oct 19, 2025, 07:51 PM UTC

  1. investigating Oct 18, 2025, 06:43 PM UTC

    We have identified an issue connecting to Sharepoint and Onedrive.

  2. monitoring Oct 18, 2025, 06:45 PM UTC

    A fix has been implemented and we are updating our clusters.

  3. resolved Oct 19, 2025, 07:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 12, 2024 Jobs finishing before transferring data 22m

Started Dec 12, 2024, 08:17 PM UTC· resolved Dec 12, 2024, 08:39 PM UTC

  1. investigating Dec 12, 2024, 08:17 PM UTC

    We have identified an issue with jobs finishing immediately and not transferring data. We have deployed a fix and we will remediate all the jobs affected for the last 24hrs

  2. identified Dec 12, 2024, 08:17 PM UTC

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

  3. identified Dec 12, 2024, 08:39 PM UTC

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

  4. resolved Dec 12, 2024, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →