Limble outages and incidents
Outage and incident data over the last 30 days for Limble.
There have been 1 outages or incidents for Limble in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
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 NowComponents and Services Monitored for Limble
Outlogger tracks the status of these components for Xero:
Limble Fuse
| Component | Status |
|---|---|
| Limble CMMS API | Active |
| Limble CMMS Authentication Service | Active |
| Limble CMMS Authentication Service Backend | Active |
| Limble CMMS Marketing Website | Active |
| Limble CMMS Web Application | Active |
| Limble Fuse | Active |
| Limble Fuse System | Active |
Latest Limble outages and incidents.
View the latest incidents for Limble and check for official updates:
Users unable to access the limble applications
Description: **Date**: April 26, 2024 **Status**: Resolved # Summary On April 26th, 2024, our service experienced a downtime event due to an SSL certificate failure, affecting most of our customers from approximately 2:20 AM to 3:00 AM MST. The issue stemmed from recent changes in the rules around SSL certificate auto-renewal by our SSL provider, which were not fully accounted for in our system. As a result, we have enhanced our alerting systems and updated our infrastructure configurations to prevent similar issues in the future. # Impact The downtime affected all users attempting to access our site without a cached version of the SSL certificate, resulting in about 40 minutes of service disruption. # Root Causes The primary cause of the downtime was a change in the auto-renewal rules for SSL certificates by our provider, which led to an unexpected, silent expiration. Although a fix was previously developed, it was not yet fully propagated across the entire Limble infrastructure. # Resolution and Improvements Immediate actions were taken to renew the SSL certificate and mitigate the situation. Following the incident, we fully integrated the auto-renewal fix and enhanced our monitoring and alerting capabilities to detect similar issues ahead of potential disruptions. # Description of Events: * **2:18 AM MST:** SSL certificate for [limblecmms.com](http://forlimblecmms.com/) and some of its subdomains. * **2:20 AM MST:** Service disruption detected. * **2:25 AM MST:** The on-call team was alerted to the issue. * **2:33 AM MST:** Critical alert alarm raised. * **2:44 AM MST:** Official incident declaration posted on our status page. * **3:03 AM MST:** New SSL certificate procured and implemented; service restored.
Status: Postmortem
Impact: Critical | Started At: April 26, 2024, 8:43 a.m.
Updates:
-
Time: May 3, 2024, 2:50 p.m.Status: PostmortemUpdate: **Date**: April 26, 2024 **Status**: Resolved # Summary On April 26th, 2024, our service experienced a downtime event due to an SSL certificate failure, affecting most of our customers from approximately 2:20 AM to 3:00 AM MST. The issue stemmed from recent changes in the rules around SSL certificate auto-renewal by our SSL provider, which were not fully accounted for in our system. As a result, we have enhanced our alerting systems and updated our infrastructure configurations to prevent similar issues in the future. # Impact The downtime affected all users attempting to access our site without a cached version of the SSL certificate, resulting in about 40 minutes of service disruption. # Root Causes The primary cause of the downtime was a change in the auto-renewal rules for SSL certificates by our provider, which led to an unexpected, silent expiration. Although a fix was previously developed, it was not yet fully propagated across the entire Limble infrastructure. # Resolution and Improvements Immediate actions were taken to renew the SSL certificate and mitigate the situation. Following the incident, we fully integrated the auto-renewal fix and enhanced our monitoring and alerting capabilities to detect similar issues ahead of potential disruptions. # Description of Events: * **2:18 AM MST:** SSL certificate for [limblecmms.com](http://forlimblecmms.com/) and some of its subdomains. * **2:20 AM MST:** Service disruption detected. * **2:25 AM MST:** The on-call team was alerted to the issue. * **2:33 AM MST:** Critical alert alarm raised. * **2:44 AM MST:** Official incident declaration posted on our status page. * **3:03 AM MST:** New SSL certificate procured and implemented; service restored.
-
Time: April 26, 2024, 9:35 a.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: April 26, 2024, 9:05 a.m.Status: MonitoringUpdate: We have implemented a fix to address this issue and are monitoring the results.
-
Time: April 26, 2024, 8:43 a.m.Status: InvestigatingUpdate: Currently we are aware an an issue where limble applications appear to be down. We are investigating.
We are aware of an issue that's causing some customers to not have elements / data in the app load
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: April 19, 2024, 7:34 p.m.
Updates:
-
Time: April 19, 2024, 9:06 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: April 19, 2024, 8:29 p.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: April 19, 2024, 8:29 p.m.Status: IdentifiedUpdate: We are continuing to work on a fix for this issue.
-
Time: April 19, 2024, 8:02 p.m.Status: IdentifiedUpdate: The issue has been identified and a fix is being implemented.
-
Time: April 19, 2024, 7:34 p.m.Status: InvestigatingUpdate: We are currently investigating this issue.
Some customers may be experiencing issues accessing the CMMS application
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: April 9, 2024, 4:08 p.m.
Updates:
-
Time: April 9, 2024, 5:35 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: April 9, 2024, 4:40 p.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: April 9, 2024, 4:08 p.m.Status: InvestigatingUpdate: We are currently investigating this issue.
System Unstable
Description: We are currently investigating this issue.
Status: Resolved
Impact: None | Started At: Feb. 22, 2024, midnight
Updates:
-
Time: Feb. 22, 2024, 12:27 a.m.Status: ResolvedUpdate: We are currently investigating this issue.
System Unstable
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Feb. 21, 2024, 11:55 p.m.
Updates:
-
Time: Feb. 22, 2024, 12:42 a.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: Feb. 22, 2024, 12:36 a.m.Status: MonitoringUpdate: We are continuing to monitor for any further issues.
-
Time: Feb. 22, 2024, 12:36 a.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: Feb. 22, 2024, 12:28 a.m.Status: IdentifiedUpdate: We are continuing to work on a fix for this issue.
-
Time: Feb. 22, 2024, 12:28 a.m.Status: IdentifiedUpdate: The issue has been identified and a fix is being implemented.
