Limble Outage History

31 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Limble status100.00% uptime history

Every Recorded Limble Incident

Limble incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 22, 2026Monthly Scheduled Maintenance - November 2026We will be undergoing monthly planned maintenance during this period. Some services may experience increased latency and error rates or intermittent availability.2h 0mScheduled
Oct 18, 2026Monthly Scheduled Maintenance - October 2026The scheduled maintenance has been completed.1h 30mScheduled
Oct 8, 202621CFR Customers are seeing errors when doing certain tasks. We are currently investigatingThis incident has been resolved.18 minResolved
Oct 6, 2026Slow application loading in US environmentThis incident has been resolved.54 minResolved
Oct 1, 2026Errors loading asset templatesThis incident has been resolved.26 minResolved
Sep 20, 2026Monthly Scheduled Maintenance - September 2026The scheduled maintenance has been completed.2h 0mScheduled
Sep 15, 2026Errors accessing Limble for some usersThis incident has been resolved.23h 2mResolved
Sep 14, 2026Emails not sendingThe backlog of emails has been sent, and new emails are flowing through the system.1h 8mResolved
Sep 8, 2026Email disruptionThis incident has been resolved.9h 45mResolved
Sep 2, 2026Increased error rateThis incident has been resolved.2h 15mResolved
Aug 18, 2026Intermittent application errors in EU regionThis incident has been resolved.1h 45mResolved
Aug 16, 2026Monthly Scheduled Maintenance - August 2026The scheduled maintenance has been completed.2h 0mScheduled
Aug 11, 2026Login page errors in Microsoft EdgeThe 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…22h 34mResolved
Jul 20, 2026Service disruption in US regionService disruption on webapp and API for US customers-873 minResolved
Jul 19, 2026Monthly Scheduled Maintenance - July 2026The scheduled maintenance has been completed.2h 0mScheduled
Jul 6, 2026Emergency Maintenance for US Region - July 2026The scheduled maintenance has been completed.1h 0mScheduled
Jul 5, 2026Emergency Maintenance Non-US Regions - July 2026The scheduled maintenance has been completed.1h 0mScheduled
Jun 21, 2026Monthly Scheduled Maintenance - June 2026The scheduled maintenance has been completed.2h 0mScheduled
May 17, 2026Monthly Scheduled Maintenance PeriodThe scheduled maintenance has been completed.2h 0mScheduled
Apr 28, 2026Limble CMMS Login not workingThis incident has been resolved.41 minResolved
Apr 27, 2026Application not loading in EU regionThis incident has been resolved.1h 1mResolved
Apr 13, 2026Limble CMMS Unresponsive in CanadaThis incident has been resolved.42 minResolved
Apr 7, 2026Tasks service performance issuesThis incident has been resolved.16 minResolved
Mar 11, 2026Limble CMMS Web Application Failing to LoadThis incident has been resolved.57 minResolved
Mar 10, 2026Scheduled tasks not createdPending tasks from overnight have been created successfully.4h 10mResolved
Mar 9, 2026Users are unable to login to Limble Community and Limble SearchA fix has been deployed to all regions, restoring Limble login access to Limble Community and Limble Search.31 minResolved
Feb 24, 2026Scheduled tasks failing to create in regions outside USThis incident has been resolved. Any missing tasks have been created, and new tasks are being created as expected.1h 15mResolved
Feb 5, 2026PM creation failing in some regionsThis incident has been resolved. PM tasks are being created successfully.5 minResolved
Dec 12, 2025Scheduled tasks not being createdThis incident has been resolved and scheduled tasks are being created successfully.4h 15mResolved
Nov 18, 2025Cloudflare Service InterruptionThis incident has been resolved.6h 58mResolved
Nov 10, 2025Scheduler errorsThe issue has been resolved and scheduled tasks are being created successfully.2h 1mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Limble incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Limble Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Limble acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Limble outage in this window ran 23h 2m, against a mean recovery of 3h 21m. If you depend on Limble in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.