Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Retention Science and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Retention Science.
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 |
---|---|
Campaign Reporting and Analytics API | Active |
Cortex Application (Main Dashboard) | Active |
Data Imports Service | Active |
Events and Tracking API | Active |
Filtering and Segmentation Service | Active |
Recommendations API | Active |
Reporting | Active |
Smart Blast / Promo Blast Sends API | Active |
SMS | Active |
Support | Active |
Template Tools | Active |
Transactional Sends API | Active |
Users API | Active |
View the latest incidents for Retention Science and check for official updates:
Description: We found a missing configuration that did not carry over from the old version of the database to the new. We added this configuration on Friday around 6pm Pacific, which has fixed the problem with our big data operations on our Subscription service database for all clients. We monitored over the weekend, and there were no further errors. This issue has been resolved. We have taken steps to make sure all of our databases have this configuration and will be monitoring any similar issue with other databases going forward.
Status: Resolved
Impact: Major | Started At: April 19, 2024, 9:20 p.m.
Description: Date Started: March 27th Date Resolved: April 11th Cause of Incident: A Migration/Upgrade to MySql v8 per Amazon AWS requirements occured on March 26th. When the migration happened there was a small bug in the code/query around NULL date values. This caused rows in our AI predictions output to go missing. Any row that had a date or timestamp or a 0 or null or date outside the normal range would cause that row to be removed entirely from the output. This was something the new version of sql was sensitive to that the old version of sql was not. How we will prevent this from happening in future: A Database migration is not a frequent occurrence, something that happens once every 4 years so so. We will do a better job in QAing by involving the Client Success team to QA a few of their largest clients to make sure no anomalies are occurring with the stages and engagement.
Status: Resolved
Impact: Critical | Started At: March 27, 2024, 6 p.m.
Description: Large amount of requests from one client caused an 11pm - 1:42am Pacific downtime (almost 3 hours) in various APIs and parts of our site. We have reduced concurrency on some services so we are less likely to see this happen again.
Status: Resolved
Impact: Critical | Started At: March 27, 2024, 6:30 a.m.
Description: Downtime for members.retentionscience.com - users were unable to access page. Incident has been resolved.
Status: Resolved
Impact: None | Started At: March 25, 2024, 10:30 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Feb. 1, 2024, 5:50 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.