Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Copado Solutions and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Copado Solutions.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
APAC | Active |
CICD | Active |
Copado AI Services | Active |
Copado Robotic Testing | Active |
Copado Version Control | Active |
Data Deploy Service | Active |
Essentials | Active |
Explorer | Active |
EMEA | Active |
CICD | Active |
Copado AI Services | Active |
Copado Robotic Testing | Active |
Copado Version Control | Active |
Data Deploy Service | Active |
Essentials | Active |
Explorer | Active |
North America | Active |
CICD | Active |
Copado AI Services | Active |
CopadoGPT | Active |
Copado Robotic Testing | Active |
Copado Success Community | Active |
Copado Version Control | Active |
Data Deploy Service | Active |
Essentials | Active |
Explorer | Active |
View the latest incidents for Copado Solutions and check for official updates:
Description: Due to conflicts stemmed from Salesforce API changes ( upgrade from v42.0 to v43.0 API's ), we introduced an regression error that might have impacted the GIT commit operations with nested components. The impacted commits are the ones generated between monday 13 at 7:55am UTC until today, tuesday 14 at 4:05pm UTC , and in some specific conditions they may have missing nested metadata items on the feature branch, although everything seems normal in Copado UI. We encourage you to visually confirm that what's on GIT is what it was expected for each commit, or simply recommit to ensure consistency. We deeply regret any inconvenience we might have caused.
Status: Resolved
Impact: None | Started At: Aug. 14, 2018, 5:01 p.m.
Description: All systems appear to be returning its full capacity
Status: Resolved
Impact: Minor | Started At: June 28, 2018, 3:32 p.m.
Description: Engineering team found that there was an older git version on the Heroku image caused by a silently failing git-heroku-build-pack. We had to rollback to Heroku image until we find a permanent solution to the build pack issue.
Status: Resolved
Impact: Minor | Started At: May 31, 2018, 2:19 p.m.
Description: The incident seems to be resolved.
Status: Resolved
Impact: Minor | Started At: April 4, 2018, 3:14 p.m.
Description: Service seems to be resolved, we will keep monitoring longer-than-usual API calls.
Status: Resolved
Impact: Minor | Started At: Jan. 23, 2018, 8:37 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.