Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for ZiftONE and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for ZiftONE.
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 |
---|---|
Advanced Reporting | Active |
Datamart Processing Queue | Active |
Integrations | Active |
Lead Distribution | Active |
Mail Deliverability | Active |
Mobile Application | Active |
REST API | Active |
Simple Processing Queue | Active |
Social Deliverability | Active |
Zift Platform | Active |
Zift Portal | Active |
View the latest incidents for ZiftONE and check for official updates:
Description: We can now confirm that a patch has been released and the incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Feb. 18, 2020, 10:11 a.m.
Description: The Zift Integration issue with Facebook that was preventing the posting of social posts and the connecting of Partner Facebook Company Pages for some users has been resolved.
Status: Resolved
Impact: Major | Started At: Jan. 21, 2020, 5:14 p.m.
Description: This incident has been resolved. The content personalizer is now fully functional again.
Status: Resolved
Impact: Major | Started At: Jan. 14, 2020, 3:48 p.m.
Description: This incident has been resolved. The content personalizer is now fully functional again.
Status: Resolved
Impact: Major | Started At: Jan. 14, 2020, 3:48 p.m.
Description: _**Summary**_ On October 18, 2019 at 12:08 EST \(17:08 GMT\), a routine update was applied to a central service. Unfortunately, that update had a downstream impact that brought most services offline. After determining the root cause, the update was rolled back to re-establish service. _**What Happened?**_ We deployed an update to our database known as a hot fix that repairs an issue in the platform quickly, but with this time-saving fix there is less evaluation of the deployment making it inherently more risky. _**What Are We Doing About This?**_ We are managing this risk by strengthening our best practices as requirements in our future hot fix release process. We are requiring the following actions for future hot fix deployments: * Prior to release, all hot fixes will require a second Engineering team lead to approve or reject the hot fix deployment based on content accuracy, quality and risk assessment. * Prior to release, all hot fixes will require a Quality Assurance representative to approve or reject the hot fix deployment based on content accuracy, quality and risk assessment. * Prior to release, specific hot fixes altering existing schema will require senior management approval.
Status: Postmortem
Impact: Critical | Started At: Oct. 18, 2019, 4:38 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.