Limble CMMS Outage History

Limble CMMS is up right now

Pingoru has recorded 50 incidents for Limble CMMS: 22 in the last 12 months and 9 in the last 90 days.

Source: status.limblecmms.com

50incidents recorded
22last 12 months
9last 90 days
4 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Limble CMMS in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202643 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202610 of 744 (0%)
August 2026224 of 744 (3%)
September 2026436 of 720 (5%)
October 202632 of 586 (0%)

Incidents, newest first

Minor August 20, 2025 Instability in EU environment 8h 23m Limble CMMS Web Application

Started Aug 20, 2025, 03:14 PM UTC· resolved Aug 20, 2025, 11:37 PM UTC

  1. investigating Aug 20, 2025, 03:14 PM UTC

    We are currently investigating intermittent instability in the Limble CMMS EU environment.

  2. identified Aug 20, 2025, 03:54 PM UTC

    We've identified the likely root cause of the issues and are working on a fix.

  3. identified Aug 20, 2025, 06:08 PM UTC

    The environment is currently stable. The engineering team has identified the root cause and is working on a fix.

  4. monitoring Aug 20, 2025, 07:54 PM UTC

    The environment is currently stable. The engineering team is monitoring and will intervene as necessary. We are testing a proposed fix for the root cause of earlier instability.

  5. resolved Aug 20, 2025, 11:37 PM UTC

    A fix for the root cause has been deployed to production.

Read the full incident report →

Critical August 4, 2025 Limble Search is experiencing an outage 10m Limble Search

Started Aug 04, 2025, 06:02 PM UTC· resolved Aug 04, 2025, 06:12 PM UTC

  1. investigating Aug 04, 2025, 06:02 PM UTC

    We are currently investigating this issue.

  2. identified Aug 04, 2025, 06:09 PM UTC

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

  3. monitoring Aug 04, 2025, 06:11 PM UTC

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

  4. resolved Aug 04, 2025, 06:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 1, 2025 Slow loading time across the application 40m Limble Fuse System, Limble CMMS Web Application, Limble CMMS API

Started Jul 01, 2025, 05:14 PM UTC· resolved Jul 01, 2025, 05:54 PM UTC

  1. investigating Jul 01, 2025, 05:14 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 01, 2025, 05:22 PM UTC

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

  3. resolved Jul 01, 2025, 05:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 30, 2025 Issues accessing Limble applications. –

Started Jun 30, 2025, 06:30 PM UTC· resolved Jun 30, 2025, 06:30 PM UTC

  1. resolved Jun 30, 2025, 08:08 PM UTC

    Users have reported increased load times across the application. Some users are experiencing blank screens when using the application.

Read the full incident report →

Major June 12, 2025 Some customers are reporting issues re-assigning tasks and other functionality 2h 17m Limble CMMS Web Application

Started Jun 12, 2025, 07:06 PM UTC· resolved Jun 12, 2025, 09:24 PM UTC

  1. investigating Jun 12, 2025, 07:06 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 12, 2025, 07:26 PM UTC

    We are receiving reports of widespread internet outages impacting multiple services, such as Cloudflare and Google Cloud Platform. These outages are currently impacting Limble, so we are monitoring the situation closely.

  3. monitoring Jun 12, 2025, 07:56 PM UTC

    We have implemented a fix and are monitoring the situation closely.

  4. resolved Jun 12, 2025, 09:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 29, 2025 Customers are reporting issues with load times 2h 22m Limble CMMS Web Application

Started Apr 29, 2025, 08:10 PM UTC· resolved Apr 29, 2025, 10:33 PM UTC

  1. investigating Apr 29, 2025, 08:10 PM UTC

    We are currently investigating this issue.

  2. identified Apr 29, 2025, 08:15 PM UTC

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

  3. monitoring Apr 29, 2025, 08:16 PM UTC

    A partial fix has been deployed. We are continuing to investigate issues with creating assets and managing vendors.

  4. monitoring Apr 29, 2025, 08:41 PM UTC

    A partial fix has been deployed. We are continuing to investigate issues with creating assets, reassigning tasks, and managing vendors.

  5. monitoring Apr 29, 2025, 09:45 PM UTC

    We are continuing to investigate and monitor issues with the following: - Creating and managing assets - Managing Vendors - Purchase order management - Some graph widgets are failing to load

  6. monitoring Apr 29, 2025, 10:17 PM UTC

    All functionality has been restored. We are continuing to monitor.

  7. resolved Apr 29, 2025, 10:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 28, 2025 Some customers reporting intermittent issues using the Limble application 24m Limble CMMS Web Application

Started Apr 28, 2025, 06:20 PM UTC· resolved Apr 28, 2025, 06:45 PM UTC

  1. investigating Apr 28, 2025, 06:20 PM UTC

    Some customers are intermittently experiencing slowness, errors, or pages failing to load on the Limble application

  2. resolved Apr 28, 2025, 09:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 18, 2025 Loading Issues in Limble 2h 26m Limble CMMS Web Application

Started Apr 18, 2025, 03:15 PM UTC· resolved Apr 18, 2025, 05:41 PM UTC

  1. investigating Apr 18, 2025, 03:53 PM UTC

    We are investigating reports of loading issues across the app, slow connections and white screens.

  2. investigating Apr 18, 2025, 03:58 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 18, 2025, 04:01 PM UTC

    The issue has been identified and a fix is being applied

  4. monitoring Apr 18, 2025, 04:14 PM UTC

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

  5. resolved Apr 18, 2025, 05:41 PM UTC

    This incident has been resolved

Read the full incident report →

Minor March 13, 2025 Some users are reporting issues with Logging on 38m Limble CMMS Web Application

Started Mar 13, 2025, 10:52 PM UTC· resolved Mar 13, 2025, 11:30 PM UTC

  1. investigating Mar 13, 2025, 10:52 PM UTC

    We are currently investigating this issue.

  2. identified Mar 13, 2025, 11:07 PM UTC

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

  3. monitoring Mar 13, 2025, 11:10 PM UTC

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

  4. resolved Mar 14, 2025, 04:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2025 Intermittent issues with new PMs and Cycle Counts launching at scheduled times 3h 29m Limble CMMS Web Application, Limble CMMS API

Started Mar 12, 2025, 12:30 PM UTC· resolved Mar 12, 2025, 04:00 PM UTC

  1. investigating Mar 12, 2025, 11:31 PM UTC

    Some customers are experiencing issues with new PMs and Cycle Counts launching at their scheduled times.

  2. identified Mar 12, 2025, 11:33 PM UTC

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

  3. monitoring Mar 12, 2025, 11:34 PM UTC

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

  4. resolved Mar 12, 2025, 11:35 PM UTC

    The incident has been resolved. A post-mortem will follow.

  5. postmortem Mar 21, 2025, 04:46 PM UTC

    **Date:** March 12, 2025 **Status:** Resolved **Impacted Region\(s\) or Services:** Limble CMMS Web Application **Note:** All times are in Mountain Daylight Time \(MDT\) ## Summary On March 12 at approximately 5 AM we identified that our backend service responsible for generating scheduled tasks had failed to initialize. Further investigation found that the scheduler had been offline since the previous evening at 5:30 PM due to a container image unexpectedly expiring. After initiating our incident response plan, engineers discovered the cause to be an expired container image. Manual steps were taken to update the container image and restart the scheduled task. Further steps were taken to implement detailed monitoring to alert if another imagine expires in the future. ## Impact Scheduled PMs and Cycle Counts experienced a temporary delay of approximately 14 hours, from 5:30 PM on March 11th to 9:00 AM on March 12th, the service was successfully restored, and all scheduled tasks resumed normal operation. ## Root Cause The scheduler container image failed to propagate during a deployment. Consequently, the scheduler attempted to run with an expired image, which resulted in a service startup failure. ## Resolution and Improvements Engineers were quickly able to identify the root cause and its relation to the missing container image. A rollback of the deployment was initiated, which resolved the issue. To prevent future occurrences, the following improvements have been implemented: * **Enhanced Monitoring:** We have deployed detailed monitoring systems specifically designed to detect and alert us to any future container image expirations, ensuring proactive intervention. ## Timeline of Events * 3/12/2025 at 4:59 AM: Customer reports that scheduled items did not send as expected * 7:30 AM: Incident is declared and engineering team is alerted * 8:15 AM: Container image was updated * 8:45 AM: Process was manually re-run * 9:15 AM: All processes re-ran successfully ## **Key Points** * No loss of customer data

Read the full incident report →

Critical December 10, 2024 Service Outage 22m Limble CMMS Web Application

Started Dec 10, 2024, 09:34 PM UTC· resolved Dec 10, 2024, 09:57 PM UTC

  1. investigating Dec 10, 2024, 09:34 PM UTC

    We are currently investigating this issue.

  2. identified Dec 10, 2024, 09:39 PM UTC

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

  3. identified Dec 10, 2024, 09:54 PM UTC

    We have resolved the issue, and will continue monitoring.

  4. resolved Dec 10, 2024, 09:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 12, 2024 Issues with creating Tasks, Parts, Assets 1h 47m Limble CMMS Web Application, Limble CMMS API

Started Nov 12, 2024, 08:11 PM UTC· resolved Nov 12, 2024, 09:59 PM UTC

  1. investigating Nov 12, 2024, 08:11 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 12, 2024, 08:13 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 12, 2024, 09:10 PM UTC

    We have identified the issue and have taken steps toward a fix.

  4. monitoring Nov 12, 2024, 09:31 PM UTC

    A fix has been implemented and we are monitoring results

  5. resolved Nov 12, 2024, 09:59 PM UTC

    This incident is now resolved.

  6. postmortem Nov 14, 2024, 08:12 PM UTC

    **Date:** November 12, 2024 **Status:** Resolved ## Summary On November 12, 2024, the application experienced a rolling service disruption that intermittently impacted our customers when attempting to create new items in our application, such as tasks, assets, and parts. The incident was caused by a database migration deployed into production, which overloaded our databases and caused delays in propagating requests. Immediate action was taken to terminate the migration and restore service to customers. to prevent a recurrence, new deploy procedures and monitors are being implemented. ## Impact For a period of approximately 3 hours, customers intermittently encountered delays or failures when attempting to create items, such as tasks, assets, and parts in our application. In some cases, the action appeared to fail, but the items were successfully created, appearing in the application after some delay. ## Root Cause The incident was caused by a database migration which overloaded our production database. Overloading of the database directly led to a increase in ‘replication lag’. When this metric exceeded 1 second, our applications’ workflows began failing or timing out. ## Resolution and Improvements Once discovered the offending database migration was immediately terminated, restoring service to all customers. Next, that migration was corrected by our Engineers, thoroughly tested using improved protocols, and re-executed without a recurrence of service disruption. Additionally, the following improvements will be implemented: * Monitoring and Alerting Improvements * Stricter requirements in testing of all migrations using a near production sandbox database * High-risk migrations will be executed during planned maintenance windows ### Timeline of Events * 11:29 AM MST: Database migration initiated. * 12:03 PM MST: Customers begin reporting disruptions. * 12:30 PM MST: Investigation and communication initiated. * 12:57 PM MST: Incident is declared. * 2:15 PM MST: Root cause identified and solution identified. * 2:22 PM MST: Solution implemented and verified in production. * 2:37 PM MST: Incident resolved following further monitoring. ### Key Points * No loss of our customers' historical data. * Not all customers were impacted at the same time. This was a rolling disruption.

Read the full incident report →