Limble CMMS incident

Login page errors in Microsoft Edge

Major Resolved View vendor source →

Limble CMMS experienced a major incident on August 11, 2026 affecting Limble CMMS Web Application and Limble CMMS Authentication Service, lasting 22h 34m. The incident has been resolved; the full update timeline is below.

Started
Aug 11, 2026, 06:09 PM UTC
Resolved
Aug 12, 2026, 04:44 PM UTC
Duration
22h 34m
Detected by Pingoru
Aug 11, 2026, 06:09 PM UTC

Affected components

Limble CMMS Web ApplicationLimble CMMS Authentication Service

Update timeline

  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.