Overview
When you close a downtime, Mobaro finalizes how much operational time it cost. Understanding the calculation — and the one rule that governs it — keeps your downtime figures accurate and your reports trustworthy. This article covers how downtime is measured, three common scenarios worked through, and how to edit closed registrations.
Users must be Super Users or have the following to measure and edit Downtime:
Operations: Manage Downtime, and Locations: View or Modify
Why this matters: A downtime is only as useful as its measured duration. Count time the Location was never expected to be running and your uptime looks worse than reality; miss in-hours time and it looks better. The rule below keeps the number honest.
How downtime is measured
Measuring downtime means finding the total lost operational hours a registration caused. This is confirmed in the web app when you close the downtime — the system suggests a duration, and you adjust it if needed. Two figures underpin it:
Nominal Operational Hours = Registered Operational Hours + Registered Downtime.
Downtime Percentage = (Registered Downtime ÷ Nominal Operational Hours) × 100.
Critical: Only register the time the Location was out of operation during hours it should have been operating. Time outside opening hours must not be counted — it's the single biggest cause of inflated downtime. Attaching opening hours to the Location automates this trimming; see How operating hours affect downtime tracking.
Worked scenarios
Short-lived downtime
Short-lived downtime
Expected operating hours: 06:00–20:00 (14 hours). Downtime: 14:00–15:00 (1 hour).
When closing, verify the suggested duration (the time between start and resolved) and adjust if needed.
Nominal Operational Hours: 13 + 1 = 14. Downtime Percentage: 1 ÷ 14 = 7.1%.
Downtime exceeding operating hours
Downtime exceeding operating hours
Expected operating hours: 06:00–20:00 (14 hours). Downtime: 14:00–22:00 (8 clock hours).
Only log the hours the Location was expected to operate but was down: 14:00–20:00 = 6 hours. The 2 hours after closing don't count.
Downtime Percentage: 6 ÷ 14 = 42%.
Downtime spanning multiple days
Downtime spanning multiple days
Downtime: starts 14:00 on day one, resolved 22:00 on day two. Count only expected operating hours on each day.
Day one: 14:00–20:00 = 6 hours. Day two: 08:00–22:00 → counted to close at 14 hours. Total: 20 hours against 28 expected = 71%.
Note: The system doesn't automatically strip out-of-hours time from a multi-day downtime, so check each day's contribution when closing. Attaching opening hours to the Location does this trimming for you.
Editing closed downtime registrations
You can correct existing and closed registrations from the web app:
Go to
Downtime.Open the
Statefilter and make sure Closed is included.Select the registration and click
Edit.Make your changes and click
Save.
Note: You can also review and correct downtime per Location on the Uptime Summary, and log a past downtime that was missed in the moment.
Frequently asked questions
Q: Why does my downtime look higher than expected?
A: Usually because out-of-hours time was counted. Only count time the Location should have been operating — attaching opening hours automates the trim.
Q: Where does the suggested duration come from?
A: The time between the downtime starting and the Location returning to operation. It's a starting point — adjust it to reflect expected operating time before confirming.
Q: Can I change a downtime after it's closed?
A: Yes. Include Closed in the state filter, then edit it. Changes flow through to reports and Dashboards.