Higher Logic had 22 outages in the last 2 years totaling 114h 6m of downtime — averaging 0.9 incidents per month.
There were 22 Higher Logic outages since September 4, 2024 totaling 114h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating issues related to mailings, this includes fonts, formatting and rendering).
This incident has been resolved.
We are currently investigating issues with the Rest API.
The issue has been identified, the fix has been deployed, and we've completed our post-deployment validation.
THIS PERTAINS TO WORKSPACE ONLY OC Workspace is currently down, and no service is available at this time. Our team is actively investigating the issue and working to restore service as quickly as possible. We understand this is disruptive and apologize for the inconvenience. We will share another update as soon as more information is available. Thank you for your patience.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of messages being sent however they are showing not delivered to all members of the group.
The issue has been identified and a fix implemented. For customers who submitted a ticket, our support team will be in touch regarding next steps.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Some Community (OC) emails are delayed, processing is active and the backlog is steadily decreasing. Once queues normalize, we will re-drive any affected messages. Informz (IZ) mailings that rely on UPI integrations may continue to error until the service is fully restored.
All outstanding issues have been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue and will provide an update as soon as additional information is available.
The server error has been corrected and the issue has been resolved. Any messages showing they went to 0 contacts will need to be copied and resent.
**Root Cause:** We did a major version upgrade to our Mailer servers during our Q1 Quarterly Maintenance cycle. During the final steps of this process, we missed a key step in our documented procedure. This left the mailer services running on a temporary license which expired on 03/7/2025. **Corrective Actions:** We are doing additional training and adding a peer review step into the process.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some sites were showing a server error when trying to access
**What Happened** On Saturday nights, we run a full reindex operation on each database before the Full backups run against our databases. During the reindex operation, our application servers started having issues connecting to the databases. **Root Cause** A recent change in the application stack caused a significantly higher rate of log entries to a system Log table. Due to the increased size of this table, the reindex process locked that table for a significant amount of time. In turn, this caused issues for all OC application servers connecting to the databases. **Corrective Actions** * A code change has been released to production to fix the uncontrolled growth of the log table. * Enhance monitors that will alert when unexpected growth conditions happen on key system Log tables.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and this issue is resolved. Thank you for your patience.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.