Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Totango and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Totango.
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 |
---|---|
Assets | Active |
Campaigns | Active |
Data Collection Gateway | Active |
Data Processing Pipelines | Active |
Email to Touchpoints | Active |
Marketing Website | Active |
Mobile Application | Active |
Salesforce Connector | Active |
Tasks and SuccessPlays | Active |
Totango Web Application | Active |
View the latest incidents for Totango and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: May 14, 2023, 5:06 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: May 14, 2023, 5:06 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 9, 2023, 6:36 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 9, 2023, 6:36 p.m.
Description: # **Event Description** Success Plays unexpectedly fired in the US region on April 19, 14:15 UTC, due to the use of an old Redis cluster. # **Findings & Timeline** _**Reported: April 19, 14:15 UTC The Totango system monitoring detected the issue.**_ _**Identified: April 19, 15:20 UTC The root cause was identified as a DNS change from the new Redis cluster to the old one.**_ _The application team immediately stopped all SuccessPlay triggering. The SuccessPlay engine at that time already triggered a few thousands tasks and events \(as part of the task creation emails which were sent to users\)._ _The application team then created a cleanup plan, which included deleting duplicated tasks and events and reverting attribute changes._ _**Resolved:** Apr 21, 19:58 UTC_ _Duplicated task deletion is completed_ _**April 21, 20:51 UTC**_ _**Cleanup plan execution was completed in full, including events deletion and reverting attribute changes.**_ **Root Cause:** _An old Redis cluster was being used actively instead of the new one due to a DNS change, causing SuccessPlays to fire unexpectedly._ _Corrective Action_ * _Deprecate and isolate old components when a replacement is created - Completed_ * _Implement a monitoring system to alert on any manual changes performed - In Progress \(ETA: June 30th\)_ * _Enforce a single config file for all application DNSs - Planned \(ETA: August 2023\)_ * _Create a dedicated runbook to tackle similar cases in the future - In Progress \(ETA: May 5th\)_ * _Implement anomaly detection flows to identify changes in automation triggering behavior, pause it, and alert about it - In Progress \(ETA: June 1st\)_
Status: Postmortem
Impact: Major | Started At: April 19, 2023, 3:20 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.