Limble CMMS had 21 outages in the last 2 years totaling 84h 56m of downtime — averaging 0.9 incidents per month.
There were 21 Limble CMMS outages since October 14, 2025 totaling 84h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating errors loading asset templates. These errors may be affecting other functionality in the application as well.
We've identified the issue and deployed a fix. We are still investigating to ensure that the fix is complete.
This incident has been resolved.
We are currently investigating an issue that is causing errors on the Limble Work Request Portal when using the Microsoft Edge browser, or when using Microsoft Defender.
This issue is affecting other parts of the Limble application (including login and task management) for some users. We are continuing to investigate.
We are seeing errors for some users accessing Limble through Microsoft Edge or on computers using Windows Defender. This may also be impacting users on local networks implementing network-based URL blocking. The Limble application is currently operational, and we’ve verified that the application is safe and secure. We are working with a handful of third party security reputation services that have incorrectly marked the application as unsafe to update their classification.
Limble is now loading OK in Microsoft Edge. The Limble application is currently operational, and we’ve verified that the application is safe and secure. At no time during this incident were Limble systems compromised. No customer data was accessed, exposed, altered or lost as a result of the incident. Limble was incorrectly marked as unsafe by some third-party security reputation services. We are continuing to work with those third party services to correct Limble's classification. Some users on local networks implementing network-based security may still be experiencing issues. If possible, we recommend retrieving up-to-date web site classification data from your security vendor, or specifically adding Limble to an allow list.
This incident has been resolved.
We are currently investigating an issue that is preventing emails from being sent.
We've identified the issue and are working on a fix.
New emails are being sent now. We are working through the backlog of previously triggered emails.
The backlog of emails has been sent, and new emails are flowing through the system.
We are currently investigating an issue with outgoing emails.
We have identified the cause of the email issue and are working to resolve it now.
This issue has been resolved. New emails are now being sent; we're assessing previously sent emails.
This incident has been resolved.
We are investigating an increased error rate in the Limble CMMS web application that may be affecting some users.
We are continuing to investigate this issue. Actual impact appears to be minimal, but we are working on finding and addressing the problem.
We've identified the source of the errors and have implemented a fix. We are monitoring the application performance to ensure it's resolved.
This incident has been resolved.
We are currently investigating reports of intermittent application loading errors in the Limble EU region.
We've identified the issue and have implemented a mitigation. We are currently monitoring to ensure the service is stable.
This incident has been resolved.
We are currently investigating an issue that is causing errors on the Limble login page when using the Microsoft Edge browser.
The issue may be affecting browsers on Windows other than Microsoft Edge, in cases where Microsoft Defender is running locally. We are still investigating the root cause.
We’re aware that some customers are seeing a phishing warning when attempting to access the Limble login page. We've investigated and confirmed that the Limble site is safe and secure, and our team is actively working to resolve the issue with third parties that are incorrectly marking the site as unsafe. If you run into issues when using Microsoft Edge or Google Chrome, you may use the following URL to log in to Limble: https://us-auth.limblecmms.com/
The Limble authentication page is working for some users now in Microsoft Edge. We are monitoring to ensure full resolution.
We seeing intermittent errors for some users accessing app.limblecmms.com through Microsoft Edge. We are working with the third parties that are incorrectly marking the application as unsafe.
The main Limble application URL (app.limblecmms.com) is now working for users in Microsoft Edge. We are monitoring to ensure full resolution.
The Limble application is currently operational, and we’ve verified that the application is safe and secure. We are working with a handful of third parties that have incorrectly marked the application as unsafe to update their classification. Customers who are still seeing disruption may be impacted by local network configuration that is blocking connections to Limble. Those customers may wish to update their network security settings to specifically allow connections to app.limblecmms.com and auth.limblecmms.com.
The Limble application is currently operational, and we’ve verified that the application is safe and secure. At no time during this incident were Limble systems compromised. No customer data was accessed, exposed, altered or lost as a result of the incident. Limble was incorrectly marked as unsafe by some third-party security reputation services. We've worked with those third parties to correct their classification, and all publicly available security reputation lists are currently showing Limble as safe. If you are still experiencing problems accessing Limble, you may need to update any host-based or network-based security systems to retrieve the latest classification data.
Service disruption on webapp and API for US customers
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.
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.
We are currently investigating intermittent performance issues with a tasks-related service.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue where scheduled maintenance tasks are not being created as expected for some customers.
The issue has been identified and a fix is being implemented.
A fix has been implemented, and the backlog of scheduled tasks is being processed. We are monitoring the process to ensure that all pending tasks are created successfully.
We are continuing to monitor for any further issues.
Pending tasks from overnight have been created successfully.
We are currently investigating and issue where users are unable to login to Limble Search and Limble Community sites with their Limble logins.
A fix has been deployed to all regions, restoring Limble login access to Limble Community and Limble Search.
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. Any missing tasks have been created, and new tasks are being created as expected.
We've identified an issue with PM tasks failing to be created in regions outside the US. We've implemented a fix and are monitoring the results.
This incident has been resolved. PM tasks are being created successfully.
Scheduled tasks are not being created for some customers. We are investigating the issue.
We've identified the issue and are working on mitigations.
Some previously missed tasks are being created now. We are continuing to monitor the task creation process.
Pending task creation has completed successfully. We are continuing to monitor the task creation process to ensure that it's running OK.
This incident has been resolved and scheduled tasks are being created successfully.
We are currently investigating an issue that has prevented some scheduled tasks from being created successfully.
We've isolated the incident to a transient network issue. The issue has been repaired and we are monitoring.
The issue has been resolved and scheduled tasks are being created successfully.