Overview
A Downtime gets its duration when someone closes it in the Mobaro Backend. That duration decides how much operating time the Downtime cost, and it feeds your downtime percentages and MTTR.
This article explains the rule for what to count, how the duration becomes a downtime percentage, three worked scenarios, and how to correct a closed Downtime. For every operational-time metric, see Uptime, downtime, and lag time explained.
At a glance |
|
Who can do this | Super Users, or a Role with Operations › Manage Downtime, plus access to the Location |
Where | Downtime › Close Downtime or Edit Downtime |
Works on | Backend (web) |
Availability | All organizations. The Location needs Enable Operational Logging. |
💡 Why this matters: A Downtime is only as useful as its duration. Count time the Location was never meant to be running and uptime looks worse than it was; miss time it should have been open and it looks better.
What to count
When you click Close Downtime, the dialog shows an Estimated Downtime: the time from when the Downtime started to when it was resolved, or to now if it isn't resolved. If the Location has opening hours, only the time inside them counts. The estimate is pre-filled as the Actual Downtime, and what you save becomes the Downtime's duration.
🛑 Critical: Only count 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 biggest cause of inflated downtime. Without opening hours on the Location, the estimate is the full elapsed time and you must trim it yourself. See Add opening hours to a Location and How opening hours affect downtime tracking.
How the percentage is calculated
Two figures turn the duration into a percentage:
Nominal Operational Hours = Registered Operational Hours (uptime) + Registered Downtime.
Downtime Percentage = (Registered Downtime ÷ Nominal Operational Hours) × 100.
This is how the Operations tile in the Mobaro app works out the day's percentages. The Location Operational History and Operational History Details Dashboard widgets also add lag time — the time a Location stayed closed after a Downtime — to the total, and count only closed Downtimes. So the app and a Dashboard can show different percentages for the same day. See Uptime, downtime, and lag time explained.
Worked scenarios
The scenarios use expected operating hours of 06:00–20:00 (14 hours) unless stated otherwise.
Short-lived downtime
Downtime: 14:00–15:00. The Estimated Downtime is 1 hour, the time from start to resolved. Uptime is 13 hours, so the Downtime Percentage is 1 ÷ 14 = 7.1%.
Downtime past closing time
Downtime: 14:00–22:00, 8 clock hours. Only 14:00–20:00 counts, because the Location wasn't meant to run after 20:00: Actual Downtime is 6 hours. With 8 hours of uptime, the Downtime Percentage is 6 ÷ 14 = 43%.
Downtime over several days
Downtime: from 14:00 on day one until 22:00 on day two. Count each day's operating hours separately. Day one runs 06:00–20:00, so 6 hours count (14:00–20:00). Day two runs 08:00–22:00, so all 14 hours count. Actual Downtime is 20 hours. With 8 hours of uptime on day one, the Downtime Percentage is 20 ÷ 28 = 71%.
With opening hours on the Location, Mobaro suggests these figures in the Close Downtime dialog, checking each day separately. Without them, the estimate includes the nights and you must enter the Actual Downtime yourself.
Correct a closed Downtime
1. Show closed Downtimes
In the Backend, open Downtime. The list shows Open, Blocking and Resolved Downtimes by default, so open the State filter and include Closed.
2. Open the Downtime
Select the Downtime and click Edit Downtime.
3. Update the duration
Click the pencil next to Duration. In Update downtime duration, correct Started at or Resolved at, or tick Enable editing downtime duration to type your own Downtime Duration. Then click Save changes.
⚠️ Heads-up: If the saved duration doesn't match the opening-hours calculation, the dialog shows a mismatch notice with the calculated value. That can be intentional, for example after a manual correction. Click Use calculated downtime duration only if you want the calculated value. Changing a Location's opening hours doesn't update Downtimes that are already closed.
To add a Downtime nobody logged at the time, use the Location's Uptime Summary — see Reviewing and correcting uptime in the Uptime Summary.
Best practices
Attach opening hours to every Location that uses Downtime, so the estimate is trimmed for you.
Check the Actual Downtime against what really happened before you close each Downtime.
Close resolved Downtimes promptly; Dashboards only count closed ones in the history widgets.
When comparing percentages, compare the same surface: the app and the Dashboard widgets use different totals.
Frequently asked questions
Why does the Dashboard show zero downtime when there was a downtime?
Usually because the Downtime isn't closed yet; the history widgets count closed Downtimes only. If it was closed with 0 minutes, the Downtime usually fell entirely outside the Location's opening hours. Correct it in Update downtime duration. See How opening hours affect downtime tracking.
Where do I set or change the downtime duration?
When closing, in Actual Downtime in the Close Downtime dialog. Afterwards, select the Downtime, click Edit Downtime, then the pencil next to Duration. Both need Operations › Manage Downtime or Super User.
Why do the percentages change when I change the date range, even though the downtimes stay the same?
Because the percentage is a share of the recorded time in the range — uptime plus downtime, plus lag time on Dashboards — not of opening hours. A longer range adds uptime, so the same downtime is a smaller share. See Uptime, downtime, and lag time explained.
Can I edit several downtimes at once?
No. In the Downtime list you close and edit Downtimes one at a time, so you can check each duration. See Using downtime in Mobaro.
Can I leave a downtime open for several days while the ride is closed?
Yes. With opening hours on the Location, the Estimated Downtime counts only each day's opening hours, so nights and closed days aren't suggested. Check the value before you confirm it. See How opening hours affect downtime tracking.