Copado Outage History

Copado is up right now

Copado had 9 outages in the last 2 years totaling 47h 26m of downtime — averaging 0.4 incidents per month.

There were 9 Copado outages since November 18, 2024 totaling 47h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.copado.com

Minor July 21, 2026

GitHub Authentication Issue

Detected by Pingoru
Jul 21, 2026, 09:58 AM UTC
Resolved
Jul 21, 2026, 01:11 PM UTC
Duration
3h 12m
Affected: CICDCICDCICD
Timeline · 4 updates
  1. investigating Jul 21, 2026, 09:58 AM UTC

    We are currently investigating an issue impacting a subset of customers who are experiencing Git authentication errors when committing or promoting components. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will continue to provide updates as more information becomes available.

  2. identified Jul 21, 2026, 10:46 AM UTC

    We have identified that the Git authentication errors impacting customers are related to an ongoing GitHub service incident: https://www.githubstatus.com/ We are monitoring closely and will update this status when more information is available.

  3. monitoring Jul 21, 2026, 12:09 PM UTC

    GitHub's status has been updated to indicate that the incident is resolved. We will monitor for now and update this incident to Resolved once we have confirmed that full functionality is restored.

  4. resolved Jul 21, 2026, 01:11 PM UTC

    We have determined that there were no additional occurrences in the last hour. This incident has been resolved.

Read the full incident report →

Notice July 15, 2026

Metadata getting error could not clone repository repository

Detected by Pingoru
Jul 15, 2026, 09:25 PM UTC
Resolved
Jul 15, 2026, 11:34 PM UTC
Duration
2h 8m
Affected: CICD
Timeline · 2 updates
  1. investigating Jul 15, 2026, 09:25 PM UTC

    We have received reports from a small number of customers experiencing repository-related issues with their CICD pipelines. Due to the pattern of these reports, we are currently investigating this as a potential service degradation. While your specific Orgs and CICD operations may not be impacted, please feel free to open a case in our Success Community if you are experiencing issues.

  2. resolved Jul 15, 2026, 11:34 PM UTC

    This has been resolved.

Read the full incident report →

Minor May 11, 2026

Performance Degradation in CI/CD Pipelines

Detected by Pingoru
May 11, 2026, 03:23 PM UTC
Resolved
May 11, 2026, 08:21 PM UTC
Duration
4h 58m
Affected: CICDData Deploy Service
Timeline · 4 updates
  1. investigating May 11, 2026, 03:23 PM UTC

    We are currently investigating reports of performance degradation impacting CI/CD pipelines. During this time, some users may also experience intermittent delays or unexpected validation errors when utilizing the CICD Pipeline, which may also affect the Data Deploy Service. Our engineering teams are actively looking into the situation to identify the root cause. We will provide an update as soon as more information is available.

  2. investigating May 11, 2026, 03:44 PM UTC

    The majority of the instability being experienced is due to the "frequent rotation of Refresh Tokens" now being enforced by Salesforce, which we are in the process of further mitigating, at scale.

  3. monitoring May 11, 2026, 07:05 PM UTC

    Status update: Monitoring We have observed a complete drop in authentication errors over the last hour and currently consider this issue resolved. Our team will continue to monitor the system to ensure stability. Action required: If you experienced an error, please re-authenticate your credentials and retry your jobs. Please note that the main Credential for the Org where Copado is installed must be validated first; after that is complete, all subsequent Credential records must be validated by their respective record owners in Salesforce.

  4. resolved May 11, 2026, 08:21 PM UTC

    We have implemented the necessary backend mitigations to resolve the recent service disruptions, and system stability has been fully restored. Action required: If you experienced an error, please re-authenticate your credentials and retry your jobs. Please note that the main Credential for the Org where Copado is installed must be validated first; after that is complete, all subsequent Credential records must be validated by their respective record owners in Salesforce.

Read the full incident report →

Major May 5, 2026

Elevated Error Rates in Copado AI Services

Detected by Pingoru
May 05, 2026, 02:58 PM UTC
Resolved
May 05, 2026, 08:07 PM UTC
Duration
5h 8m
Affected: Copado AI Services
Timeline · 5 updates
  1. investigating May 05, 2026, 02:58 PM UTC

    We are currently investigating an issue affecting Copado AI Services, where users may be experiencing consistent "Agentic LLM task failed" errors. Our engineering team has identified that this is stemming from an overloaded state with one of our upstream AI providers (Anthropic) in our primary hosting region, North America. We are treating this with the highest priority and will provide another update as soon as we have more information or a resolution.

  2. investigating May 05, 2026, 03:00 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 05, 2026, 03:59 PM UTC

    We are continuing to investigate this issue.

  4. monitoring May 05, 2026, 04:00 PM UTC

    We have successfully resolved the issue affecting Copado AI Services for our North American servers. Normal service has been fully restored, and users should no longer experience errors when utilizing AI features. We will continue to monitor the service closely to ensure optimal performance. We apologize for any inconvenience this caused and appreciate your patience while our team worked to restore service.

  5. resolved May 05, 2026, 08:07 PM UTC

    Update - Resolved Our monitoring period has concluded, and we have confirmed that Copado AI Services are fully operational and performing as expected for all North American servers. This incident is now resolved. Thank you for your patience.

Read the full incident report →

Major October 20, 2025

Third-Party Service Degradation (AWS & Salesforce)

Detected by Pingoru
Oct 20, 2025, 03:45 PM UTC
Resolved
Oct 21, 2025, 01:06 AM UTC
Duration
9h 21m
Affected: CICDCopado Robotic TestingEssentialsCopado Version ControlExplorerCopado AI ServicesData Deploy ServiceCopado Success Community
Timeline · 5 updates
  1. monitoring Oct 20, 2025, 03:45 PM UTC

    We are currently experiencing a partial outage due to an ongoing issue with Amazon Web Services (AWS), primarily affecting the US-EAST-1 region. This issue has also impacted certain Salesforce-hosted environments, including our US CRT/AI infrastructure. While AWS initially began showing signs of recovery around 5:10 AM PDT, subsequent challenges in their mitigation efforts have resulted in renewed instability. As of now, both AWS and Salesforce continue to report this as an active incident. Due to the dependencies between our systems and these third-party services, a growing number of customers are experiencing service disruptions or inaccessibility across multiple products — including CRT, AI, CI/CD, and Essentials. Our engineering team is actively engaged and continuing to monitor the situation closely. We are working with our partners at AWS and Salesforce to restore full service as quickly as possible. Next update: As soon as new information becomes available.

  2. monitoring Oct 20, 2025, 04:40 PM UTC

    We are currently seeing a broader impact across US services. Live Testing in CRT US is likely heavily impacted, and we are also receiving reports of document upload failures in AI for US-based users. Our team is actively monitoring and working with AWS and Salesforce to mitigate the issue. Next update: As soon as new information becomes available.

  3. monitoring Oct 20, 2025, 09:10 PM UTC

    We have seen improvements in the availability and performances of our services, as well as reduced errors connecting to Salesforce. This has been further confirmed by updates from AWS and Salesforce, respectively. We are continuing to monitor the situation and will post further updates, but we believe things are trending positively. Next update: As soon as new information becomes available.

  4. identified Oct 20, 2025, 11:32 PM UTC

    We have continued to monitor this situation and mostly positive improvements across our products and connectivity with Salesforce. At approximately 23:00 UTC, AWS marked their ongoing incident as resolved. Salesforce continues to consider this incident ongoing, however we are updating our status to reflect the resolution on the AWS side, and now consider this incident to only be degraded performance rather than a partial outage. Customers may still experience issues with any operations that connect to Salesforce.

  5. resolved Oct 21, 2025, 01:06 AM UTC

    Salesforce has updated their status at 00:30 UTC and marked this incident as resolved. We now also will mark this incident as resolved.

Read the full incident report →

Minor August 18, 2025

CRT Degradation affecting projects

Detected by Pingoru
Aug 18, 2025, 04:32 PM UTC
Resolved
Aug 18, 2025, 07:03 PM UTC
Duration
2h 31m
Affected: Copado Robotic TestingCopado Robotic TestingCopado Robotic Testing
Timeline · 2 updates
  1. identified Aug 18, 2025, 04:32 PM UTC

    An issue related to projects in Copado Robotic Testing has been identified affecting multiple customers in different regions. Our team is investigating the cause of the error and will provide updates as quickly as possible. We apologize for the inconvenience.

  2. resolved Aug 18, 2025, 07:03 PM UTC

    All regions are operational again. This incident has been resolved.

Read the full incident report →

Major June 12, 2025

Global AWS and Google Cloud Outage

Detected by Pingoru
Jun 12, 2025, 06:53 PM UTC
Resolved
Jun 12, 2025, 08:55 PM UTC
Duration
2h 2m
Affected: CICDCICDCICDCopado Robotic TestingCopado Robotic TestingCopado Robotic TestingEssentialsEssentialsEssentialsCopado Version ControlCopado Version ControlCopado Version ControlExplorerExplorerExplorerCopado AI ServicesCopado AI ServicesCopado AI ServicesData Deploy ServiceData Deploy ServiceData Deploy ServiceCopado Success Community
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:53 PM UTC

    We have detected a global service disruption as of 13:28 CST, which is impacting, but is not limited to, both Google Cloud and Amazon Web Services worldwide. This disruption is impacting Copado, Salesforce, and many other products and services. During this time you may experience issues such as inability to login, authenticate, and interact with Copado/Salesforce. We will continue to update our status as more information becomes available.

  2. investigating Jun 12, 2025, 07:24 PM UTC

    We are seeing a partial recovery in internal Copado Job executions. All the systems have been updated to Degraded Performance.

  3. monitoring Jun 12, 2025, 08:08 PM UTC

    We have observed a full recovery across Copado Robotic Testing, Copado Explorer, Essentials, and Copado AI services. We are still seeing partial degradation affecting CICD jobs. Our team is actively monitoring the situation to ensure full restoration of all services.

  4. resolved Jun 12, 2025, 08:55 PM UTC

    Google Cloud's mitigation efforts have led to all services showing significant recovery. We will continue to monitor to ensure we don't see signs of the disruption recurring, but at this time, all known impact has subsided. All services are operational.

Read the full incident report →

Notice March 3, 2025

Get Metadata and Snapshot Issue

Detected by Pingoru
Mar 03, 2025, 10:35 PM UTC
Resolved
Mar 04, 2025, 04:40 PM UTC
Duration
18h 4m
Affected: CICDCICDCICD
Timeline · 4 updates
  1. identified Mar 03, 2025, 10:35 PM UTC

    It appears that Salesforce has introduced a change to the Partner WSDL in patch 9.9 which is unexpectedly returning JSON for the certain objects in the describe call. This is affecting customers on this version in their ability to get metadata, and to create snapshots. We have temporarily implemented a method to ignore this object in the Salesforce Partner WSDL and have informed Salesforce of the issue. Our engineering and infrastructure teams are engaged and we will share updates here as our investigation continues.

  2. identified Mar 04, 2025, 01:34 PM UTC

    Our engineering team has reviewed this issue further, and confirmed that customers on Salesforce patch 9.10 are also affected, due to another object not included in the library. They have prepared a hotfix which addresses all cases. This hotfix is being tested now and will be released shortly.

  3. monitoring Mar 04, 2025, 03:06 PM UTC

    The hotfix has been released. We will monitor the impact for a short period and update this incident to Resolved.

  4. resolved Mar 04, 2025, 04:40 PM UTC

    After the hotfix, our monitoring shows no new instances of this error occurring- this incident is being marked Resolved.

Read the full incident report →

Notice November 18, 2024

APAC Job Delays

Detected by Pingoru
Nov 18, 2024, 04:00 AM UTC
Resolved
Nov 18, 2024, 04:00 AM UTC
Duration
—
Affected: CICDCopado Version ControlData Deploy Service
Timeline · 1 update
  1. resolved Nov 27, 2024, 11:06 PM UTC

    On 11/18/2024, at 4:00 AM UTC, customers on our APAC backend experienced interruptions resulting job delays and errors during their use of Copado. Our engineering team investigated and identified issues related to the latest backend release. The team implemented the necessary changes on 11/18/2024 at 8:20 AM UTC, and service resumed to normal. We apologize for any inconvenience.

Read the full incident report →