All Systems Operational

About This Site

Welcome to the Copado status page.
Transparency is one of our key values.

Uptime over the past 90 days. View historical uptime.
North America Operational
CICD Operational
Copado Robotic Testing Operational
Essentials Operational
Copado Version Control Operational
Explorer Operational
Copado AI Services Operational
Data Deploy Service Operational
Copado Success Community Operational
EMEA Operational
CICD Operational
Copado Robotic Testing Operational
Essentials Operational
Copado Version Control Operational
Explorer Operational
Copado AI Services Operational
Data Deploy Service Operational
APAC Operational
CICD Operational
Copado Robotic Testing Operational
Essentials Operational
Copado Version Control Operational
Explorer Operational
Copado AI Services Operational
Data Deploy Service Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 17, 2026

No incidents reported today.

Sep 16, 2026

Service Alert Update: Global Salesforce Core Service Disruption
Resolved - This incident has been resolved.
Sep 16, 18:03 UTC
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.
Sep 16, 12:19 UTC
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.
Sep 16, 08:47 UTC

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

Planned Downtime - US Customers
Completed - The scheduled maintenance has been completed.
Sep 10, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 10, 01:00 UTC
Scheduled - During this planned downtime, we will perform maintenance, enhancements and needed improvements to keep Copado secure, robust and reliable. We recognize the important role that Copado plays in your success, and we aim to minimize disruption by planning and scheduling this downtime in advance.

Please note that Copado performs planned downtime operations regionally. This planned downtime will affect customers on Copado backends, including dedicated backends, located in North America.

If you have any scheduled jobs during this window, please reschedule them or try them after the maintenance window is complete.
May 26, 11:00 UTC

Sep 9, 2026

Planned Downtime - EMEA Customers
Completed - The scheduled maintenance has been completed.
Sep 9, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 9, 01:00 UTC
Scheduled - During this planned downtime, we will perform maintenance, enhancements and needed improvements to keep Copado secure, robust and reliable. We recognize the important role that Copado plays in your success, and we aim to minimize disruption by planning and scheduling this downtime in advance.

Please note that Copado performs planned downtime operations regionally. This planned downtime will affect customers on Copado backends, including dedicated backends, located in the EMEA region.

If you have any scheduled jobs during this window, please reschedule them or try them after the maintenance window is complete.
May 26, 10:59 UTC

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

Planned Downtime - APAC Customers
Completed - The scheduled maintenance has been completed.
Sep 3, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 3, 15:00 UTC
Scheduled - During this planned downtime, we will perform maintenance, enhancements and needed improvements to keep Copado secure, robust and reliable. We recognize the important role that Copado plays in your success, and we aim to minimize disruption by planning and scheduling this downtime in advance.

Please note that Copado performs planned downtime operations regionally. This planned downtime will affect customers on Copado backends, including dedicated backends, located in the APAC region.

If you have any scheduled jobs during this window, please reschedule them or try them after the maintenance window is complete.
May 26, 10:57 UTC
Incident History Powered by Atlassian Statuspage