Looking for an update now? Check the current status, or follow Copado Solutions for future changes.
97.1%of 34 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
96.3%
27
1
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Service Alert Update: Global Salesforce Core Service Disruption
CICDCICDCICDEssentialsEssentialsEssentialsData Deploy ServiceData Deploy ServiceData Deploy Service
monitoring
Current Status
Salesforce has deployed a fix across their infrastructure, and service is actively returning to normal across affected instances. Our team has updated our status to Monitoring as platform performance stabilizes.
Incident Progress
Service Restoration: A fleetwide rollout by Salesforce is currently in progress, and system availability is restoring.
Permanent Resolution: In parallel with the rollout, engineering teams are implementing a permanent, code-level fix to prevent recurrence.
Internal Monitoring: We are actively monitoring error rates and telemetry to verify complete stability.
Customer Guidance
Most users should now be able to access their Copado instances and Copado Community without encountering maintenance errors.
If you experience any residual latency or brief hiccups, please wait a few moments and refresh your browser session.
identified
Issue Summary:
Salesforce has officially acknowledged an ongoing global service disruption affecting their Core Services. This infrastructure-level outage is the root cause of the intermittent maintenance errors and access issues currently affecting our environments.
Current Status:
Provider Incident ID: https://status.salesforce.com/incidents/20004433
Root Cause: Global Salesforce Core Service disruption.
Next Steps & Actions:
Track Real-Time Updates: Please monitor the official Salesforce Trust Link for direct updates from Salesforce engineering.
Support Ticket Request: We kindly ask that you continue to refrain from opening Copado Support or IT tickets regarding this specific error, as our support teams do not have direct control over underlying platform restoration.
We are closely monitoring Salesforce's progress and will post another update as soon as platform functionality stabilizes.
Legacy Incident Archive
6 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Copado API authentication failed. Server response was: 401
minorSource not attested
Last archived state: resolved
View archived record details
CICDData Deploy Service
monitoring
The Salesforce degradation invalidated active Refresh Tokens, causing Copado jobs to lose access to their connected orgs. To restore functionality, please perform the following steps:
1. Re-authenticate your Copado user credentials to generate new, valid refresh tokens.
2. Retry any failed Copado jobs.
If you continue to experience any issues after re-authenticating, please reach out to our support team for assistance.
investigating
We are currently tracking Salesforce service degradation impacting org authentication and Copado deployments. We are monitoring the situation closely and will provide further updates as they become available. Check status.salesforce.com for additional details.
July 2026
GitHub Authentication Issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
investigating
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.
Metadata getting error could not clone repository repository
Source not attested
Last archived state: resolved
View archived record details
investigating
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.
Metadata getting error could not clone repository repository
Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of an issue affecting promotions involving the Metadata Format Pipeline. Our engineering team is actively investigating and will provide updates as more information becomes available. Our next update will come within the hour.
May 2026
Performance Degradation in CI/CD Pipelines
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 ...
investigating
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.
investigating
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.
Elevated Error Rates in Copado AI Services
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
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.
