Limble CMMS incident

Cloudflare Service Interruption

Critical Resolved View vendor source →

Limble CMMS experienced a critical incident on November 18, 2025 affecting Limble Fuse System and Limble CMMS Web Application and 1 more component, lasting 6h 58m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 12:23 PM UTC
Resolved
Nov 18, 2025, 07:21 PM UTC
Duration
6h 58m
Detected by Pingoru
Nov 18, 2025, 12:23 PM UTC

Affected components

Limble Fuse SystemLimble CMMS Web ApplicationLimble CMMS APILimble CMMS Marketing WebsiteLimble CMMS Authentication ServiceLimble CMMS Authentication Service BackendLimble Search

Update timeline

  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.