All Systems Operational

Limble CMMS Web Application Operational
90 days ago
99.95 % uptime
Today
Limble CMMS API Operational
90 days ago
100.0 % uptime
Today
Limble CMMS Marketing Website Operational
90 days ago
100.0 % uptime
Today
Limble CMMS Authentication Service Operational
90 days ago
100.0 % uptime
Today
Limble CMMS Authentication Service Backend Operational
90 days ago
99.99 % uptime
Today
Limble Fuse Operational
90 days ago
100.0 % uptime
Today
Limble Fuse System Operational
90 days ago
100.0 % uptime
Today
Limble Search Operational
90 days ago
99.99 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Limble Web Application Average Response Time
Fetching
Limble API Average Response Time
Fetching
Limble Fuse System Latency
Fetching
Limble Fuse Webhook Latency
Fetching
Mar 10, 2026

No incidents reported today.

Mar 9, 2026
Resolved - A fix has been deployed to all regions, restoring Limble login access to Limble Community and Limble Search.
Mar 9, 14:16 MDT
Investigating - We are currently investigating and issue where users are unable to login to Limble Search and Limble Community sites with their Limble logins.
Mar 9, 13:45 MDT
Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

No incidents reported.

Mar 4, 2026

No incidents reported.

Mar 3, 2026

No incidents reported.

Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

Feb 26, 2026

No incidents reported.

Feb 25, 2026

No incidents reported.

Feb 24, 2026
Resolved - This incident has been resolved. Any missing tasks have been created, and new tasks are being created as expected.
Feb 24, 10:12 MST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 24, 10:03 MST
Identified - The issue has been identified and a fix is being implemented.
Feb 24, 09:00 MST
Investigating - We are currently investigating this issue.
Feb 24, 08:57 MST