Limble CMMS Outage History

Started Oct 08, 2026, 03:25 PM UTC· resolved Oct 08, 2026, 03:43 PM UTC

1. investigating Oct 08, 2026, 03:25 PM UTC

   We are currently investigating this issue.

2. identified Oct 08, 2026, 03:31 PM UTC

   The issue has been identified, and a fix is being implemented.

3. monitoring Oct 08, 2026, 03:39 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Oct 08, 2026, 03:39 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 08, 2026, 03:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2026, 04:32 PM UTC· resolved Oct 06, 2026, 05:27 PM UTC

1. investigating Oct 06, 2026, 04:32 PM UTC

   We are currently investigating this issue.

2. monitoring Oct 06, 2026, 04:57 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 06, 2026, 05:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 11:09 PM UTC· resolved Oct 01, 2026, 11:36 PM UTC

1. investigating Oct 01, 2026, 11:09 PM UTC

   We are investigating errors loading asset templates. These errors may be affecting other functionality in the application as well.

2. identified Oct 01, 2026, 11:15 PM UTC

   We've identified the issue and deployed a fix. We are still investigating to ensure that the fix is complete.

3. resolved Oct 01, 2026, 11:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 04:31 PM UTC· resolved Sep 16, 2026, 03:34 PM UTC

1. investigating Sep 15, 2026, 04:31 PM UTC

   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.

2. investigating Sep 15, 2026, 04:59 PM UTC

   This issue is affecting other parts of the Limble application (including login and task management) for some users. We are continuing to investigate.

3. identified Sep 15, 2026, 05:42 PM UTC

   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.

4. monitoring Sep 15, 2026, 06:30 PM UTC

   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.

5. resolved Sep 16, 2026, 03:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 01:03 PM UTC· resolved Sep 14, 2026, 02:12 PM UTC

1. investigating Sep 14, 2026, 01:03 PM UTC

   We are currently investigating an issue that is preventing emails from being sent.

2. identified Sep 14, 2026, 01:14 PM UTC

   We've identified the issue and are working on a fix.

3. identified Sep 14, 2026, 01:36 PM UTC

   New emails are being sent now. We are working through the backlog of previously triggered emails.

4. resolved Sep 14, 2026, 02:12 PM UTC

   The backlog of emails has been sent, and new emails are flowing through the system.

Read the full incident report →

Started Sep 08, 2026, 12:43 PM UTC· resolved Sep 08, 2026, 10:29 PM UTC

1. investigating Sep 08, 2026, 12:43 PM UTC

   We are currently investigating an issue with outgoing emails.

2. investigating Sep 08, 2026, 03:50 PM UTC

   We have identified the cause of the email issue and are working to resolve it now.

3. investigating Sep 08, 2026, 06:58 PM UTC

   This issue has been resolved. New emails are now being sent; we're assessing previously sent emails.

4. resolved Sep 08, 2026, 10:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 04:11 PM UTC· resolved Sep 02, 2026, 06:27 PM UTC

1. investigating Sep 02, 2026, 04:11 PM UTC

   We are investigating an increased error rate in the Limble CMMS web application that may be affecting some users.

2. investigating Sep 02, 2026, 04:47 PM UTC

   We are continuing to investigate this issue. Actual impact appears to be minimal, but we are working on finding and addressing the problem.

3. monitoring Sep 02, 2026, 05:07 PM UTC

   We've identified the source of the errors and have implemented a fix. We are monitoring the application performance to ensure it's resolved.

4. resolved Sep 02, 2026, 06:27 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 04:17 PM UTC· resolved Aug 18, 2026, 06:03 PM UTC

1. investigating Aug 18, 2026, 04:17 PM UTC

   We are currently investigating reports of intermittent application loading errors in the Limble EU region.

2. monitoring Aug 18, 2026, 04:38 PM UTC

   We've identified the issue and have implemented a mitigation. We are currently monitoring to ensure the service is stable.

3. resolved Aug 18, 2026, 06:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 11, 2026, 06:09 PM UTC· resolved Aug 12, 2026, 04:44 PM UTC

1. investigating Aug 11, 2026, 06:09 PM UTC

   We are currently investigating an issue that is causing errors on the Limble login page when using the Microsoft Edge browser.

2. investigating Aug 11, 2026, 06:46 PM UTC

   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.

3. identified Aug 11, 2026, 06:56 PM UTC

   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/

4. monitoring Aug 11, 2026, 07:36 PM UTC

   The Limble authentication page is working for some users now in Microsoft Edge. We are monitoring to ensure full resolution.

5. identified Aug 11, 2026, 08:02 PM UTC

   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.

6. monitoring Aug 11, 2026, 08:41 PM UTC

   The main Limble application URL (app.limblecmms.com) is now working for users in Microsoft Edge. We are monitoring to ensure full resolution.

7. monitoring Aug 12, 2026, 12:44 AM UTC

   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.

8. resolved Aug 12, 2026, 04:44 PM UTC

   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.

Read the full incident report →

Started Jul 20, 2026, 09:00 AM UTC· resolved Jul 20, 2026, 09:00 AM UTC

1. resolved Jul 20, 2026, 11:33 PM UTC

   Service disruption on webapp and API for US customers

Read the full incident report →

Started Apr 28, 2026, 05:41 PM UTC· resolved Apr 28, 2026, 06:22 PM UTC

1. investigating Apr 28, 2026, 05:41 PM UTC

   We are currently investigating this issue.

2. monitoring Apr 28, 2026, 06:02 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 28, 2026, 06:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 11:55 AM UTC· resolved Apr 27, 2026, 12:57 PM UTC

1. investigating Apr 27, 2026, 11:55 AM UTC

   We are currently investigating this issue.

2. monitoring Apr 27, 2026, 11:58 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 27, 2026, 12:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 10:25 PM UTC· resolved Apr 13, 2026, 11:08 PM UTC

1. investigating Apr 13, 2026, 10:25 PM UTC

   We are currently investigating this issue.

2. investigating Apr 13, 2026, 10:26 PM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 13, 2026, 10:56 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 13, 2026, 11:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 03:52 PM UTC· resolved Apr 07, 2026, 04:09 PM UTC

1. investigating Apr 07, 2026, 03:52 PM UTC

   We are currently investigating intermittent performance issues with a tasks-related service.

2. monitoring Apr 07, 2026, 04:02 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 07, 2026, 04:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 01:10 PM UTC· resolved Mar 11, 2026, 02:08 PM UTC

1. investigating Mar 11, 2026, 01:10 PM UTC

   We are currently investigating this issue.

2. monitoring Mar 11, 2026, 01:18 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Mar 11, 2026, 01:18 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Mar 11, 2026, 02:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 10, 2026, 12:19 PM UTC· resolved Mar 10, 2026, 04:29 PM UTC

1. investigating Mar 10, 2026, 12:19 PM UTC

   We are currently investigating an issue where scheduled maintenance tasks are not being created as expected for some customers.

2. identified Mar 10, 2026, 12:55 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Mar 10, 2026, 01:07 PM UTC

   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.

4. monitoring Mar 10, 2026, 01:08 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Mar 10, 2026, 04:29 PM UTC

   Pending tasks from overnight have been created successfully.

Read the full incident report →

Started Mar 09, 2026, 07:45 PM UTC· resolved Mar 09, 2026, 08:16 PM UTC

1. investigating Mar 09, 2026, 07:45 PM UTC

   We are currently investigating and issue where users are unable to login to Limble Search and Limble Community sites with their Limble logins.

2. resolved Mar 09, 2026, 08:16 PM UTC

   A fix has been deployed to all regions, restoring Limble login access to Limble Community and Limble Search.

Read the full incident report →

Started Feb 24, 2026, 03:57 PM UTC· resolved Feb 24, 2026, 05:12 PM UTC

1. investigating Feb 24, 2026, 03:57 PM UTC

   We are currently investigating this issue.

2. identified Feb 24, 2026, 04:00 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Feb 24, 2026, 05:03 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 24, 2026, 05:12 PM UTC

   This incident has been resolved. Any missing tasks have been created, and new tasks are being created as expected.

Read the full incident report →

Started Feb 05, 2026, 09:09 PM UTC· resolved Feb 05, 2026, 09:14 PM UTC

1. identified Feb 05, 2026, 09:09 PM UTC

   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.

2. resolved Feb 05, 2026, 09:14 PM UTC

   This incident has been resolved. PM tasks are being created successfully.

Read the full incident report →

Started Dec 12, 2025, 12:10 PM UTC· resolved Dec 12, 2025, 04:26 PM UTC

1. investigating Dec 12, 2025, 12:10 PM UTC

   Scheduled tasks are not being created for some customers. We are investigating the issue.

2. identified Dec 12, 2025, 01:11 PM UTC

   We've identified the issue and are working on mitigations.

3. monitoring Dec 12, 2025, 01:58 PM UTC

   Some previously missed tasks are being created now. We are continuing to monitor the task creation process.

4. monitoring Dec 12, 2025, 02:23 PM UTC

   Pending task creation has completed successfully. We are continuing to monitor the task creation process to ensure that it's running OK.

5. resolved Dec 12, 2025, 04:26 PM UTC

   This incident has been resolved and scheduled tasks are being created successfully.

Read the full incident report →

Started Nov 18, 2025, 12:23 PM UTC· resolved Nov 18, 2025, 07:21 PM UTC

1. investigating Nov 18, 2025, 12:23 PM UTC

   We are currently investigating this issue.

2. investigating Nov 18, 2025, 12:26 PM UTC

   It seems that Limble services are currently being affected by an issue with Cloudflare. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://news.ycombinator.com/item?id=45963949

3. monitoring Nov 18, 2025, 12:34 PM UTC

   Cloudflare is beginning to see service restored, which extends to Limble services. From their status page: "We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts."

4. monitoring Nov 18, 2025, 12:34 PM UTC

   Cloudflare is beginning to see service restored, which extends to Limble services. From their status page: "We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts."

5. monitoring Nov 18, 2025, 12:58 PM UTC

   Cloudflare services are not yet fully restored, but some relief has been confirmed.

6. monitoring Nov 18, 2025, 01:22 PM UTC

   Cloudflare is continuing to work on the outage, and some Limble Customers are still affected. We are continuing to monitor the situation.

7. monitoring Nov 18, 2025, 02:28 PM UTC

   We've identified and implemented a fix that should restore all Limble Services. We will continue to monitor.

8. monitoring Nov 18, 2025, 04:16 PM UTC

   We are continuing to monitor for any further issues.

9. resolved Nov 18, 2025, 07:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 10, 2025, 05:06 PM UTC· resolved Nov 10, 2025, 07:07 PM UTC

1. investigating Nov 10, 2025, 05:06 PM UTC

   We are currently investigating an issue that has prevented some scheduled tasks from being created successfully.

2. monitoring Nov 10, 2025, 05:49 PM UTC

   We've isolated the incident to a transient network issue. The issue has been repaired and we are monitoring.

3. resolved Nov 10, 2025, 07:07 PM UTC

   The issue has been resolved and scheduled tasks are being created successfully.

Read the full incident report →

Started Oct 14, 2025, 01:20 PM UTC· resolved Oct 14, 2025, 02:18 PM UTC

1. investigating Oct 14, 2025, 01:20 PM UTC

   We are currently investigating an issue with the application failing to load.

2. monitoring Oct 14, 2025, 02:08 PM UTC

   We've fixed the issue and are currently monitoring to ensure stability.

3. resolved Oct 14, 2025, 02:18 PM UTC

   This incident has been resolved.

4. postmortem Oct 16, 2025, 12:41 PM UTC

   **Date:** October 14, 2025 **Status:** Resolved **Impacted Region\(s\) or Services:** Limble CMMS Web and Mobile Application \(US Region\) **Note:** All times are in Universal Coordinated Time \(UTC\) ## **Summary** On October 14 at approximately 12:48 AM, customers began experiencing issues accessing Limble. While users could log in successfully, application features failed to load, displaying spinning indicators followed by error messages. Our engineering team immediately initiated our incident response plan and identified that our database connection management service had failed. The issue was resolved at 13:51 AM after engineers successfully restarted the affected service components. ## **Customer Impact** For approximately 1 hour, customers were unable to access or use Limble functionality in the desktop or mobile applications. Users could reach the login page but could not load any data or perform actions within the application. The service was successfully restarted, immediately restoring full functionality to all users. **No customer data was lost during this incident.** ## **Root Cause** A sudden spike in database connection requests caused our database connection pooling service to stop accepting new connections. This service acts as a gateway between the application and our database, and when it failed, users were unable to retrieve or update any information. Our engineering team quickly isolated the issue and determined that a manual restart of the connection service was required. ## **Improvements** We take service reliability seriously and have identified several improvements to prevent similar incidents: * **Automated Health Monitoring:** Have implemented additional automated health checks on this specific service to detect failures immediately and enable automatic recovery * **Automatic Restart Capability:** Will implement self-healing capabilities to this database connection service so it can automatically restart when issues are detected, consistent with our other infrastructure components * **Enhanced Observability:** Will implement improved logging and diagnostic capabilities for this service to enable faster troubleshooting ## **Timeline of Events** * **10/14/2025 at 12:48 PM UTC:** Issue detected * **1:55 PM UTC:** Incident response team assembled * **2:05 PM UTC:** Customers notified via in-app messaging * **2:15 PM UTC:** Root cause identified * **2:25 PM UTC:** Service restart initiated * **2:51 PM UTC:** **Full service** restored and confirmed operational * **3:08 PM UTC:** Status page updated * **3:19 PM UTC:** Incident officially resolved; monitoring continued

Read the full incident report →

Started Oct 01, 2025, 04:26 PM UTC· resolved Oct 01, 2025, 07:45 PM UTC

1. investigating Oct 01, 2025, 04:26 PM UTC

   We are currently investigating reports of performance degradation on the Limble API.

2. monitoring Oct 01, 2025, 05:27 PM UTC

   We've implemented some mitigations and are monitoring performance.

3. resolved Oct 01, 2025, 07:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 28, 2025, 02:05 PM UTC· resolved Aug 28, 2025, 05:00 PM UTC

1. investigating Aug 28, 2025, 02:05 PM UTC

   We are currently investigating an issue that prevented scheduled tasks from being created for a subset of customers.

2. identified Aug 28, 2025, 02:41 PM UTC

   We've identified the probable root cause and are working on a fix.

3. monitoring Aug 28, 2025, 03:38 PM UTC

   We've implemented a temporary workaround and are verifying that it has fixed the issue.

4. resolved Aug 28, 2025, 05:00 PM UTC

   Failures have been resolved and pending scheduled tasks have been created.

Read the full incident report →