Overview

A Downtime records that a Location stopped unexpectedly, why it stopped, and how long it was out of operation. It can also start the work needed to get the Location running again.

This article explains how a Downtime moves from start to close, what each state means for the Location, and how closed Downtimes feed your figures. To set Downtime up for your organization, see How to Get Started with Downtime in Mobaro.

At a glance
Who can do this	Starting a Downtime: anyone who can open and close the Location. Editing, closing and deleting: Super Users or a Role with Operations › Manage Downtime, plus access to the Location.
Where	Downtime list in the Backend; Operations tile in the app; RideOps
Works on	Backend (web), Mobile app, RideOps, Public API
Availability	All organizations. The Location needs Enable Operational Logging.

💡 Why this matters: Downtime is only useful if it's captured consistently and closed with an accurate duration. Done well, it turns scattered "the ride was down" moments into reliable uptime figures, reliability metrics and a maintenance trail.

How a Downtime starts

A Downtime can be started from:

the Mobaro app: Operations tile › a Location › Start Downtime — see Managing Downtime and uptime from the mobile app;
RideOps, usually from a Downtime Template — see Creating downtime templates for use in RideOps;
the Backend: Downtime › Start New Downtime;
the Public API.

Starting a Downtime closes the Location if it's open. A Location can have only one Open or Blocking Downtime at a time. To record a Downtime that happened in the past, use the Location's Uptime Summary — see Utilizing Operational Logging.

Downtime states

State	What it means
Open	The Location is out of operation and no Assignment is linked. Opening the Location again resolves the Downtime.
Blocking	An Assignment is linked. The Location can't be opened until the Assignment is resolved or the Downtime is closed in the Backend.
Resolved	The interruption is over: the Location was reopened or the Assignment resolved. The duration isn't confirmed yet.
Closed	Someone closed it in the Backend and confirmed its duration.

A Downtime is Blocking when an Assignment is linked to it. Mobaro links one automatically when Create an assignment when a new downtime is started is on (for Downtimes started in the app or RideOps) or when a RideOps Downtime Template says Create. Downtimes started in the Backend never get an Assignment automatically; tick Create Assignment in the Downtime editor to add one. For the settings, see How to Get Started with Downtime in Mobaro.

Close a Downtime

Closing confirms how long the Location was really down. Until a Downtime is closed it has no duration.

1. Find the Downtime

In the Backend, open Downtime. Filter by time range, State, Locations or Users, and select one Downtime that isn't closed.

2. Click Close Downtime

The Close Downtime dialog shows when the Downtime started and was resolved, and an Estimated Downtime: the time from start to resolved (or to now, if it isn't resolved yet). If the Location has opening hours, only time inside them counts — see How opening hours affect downtime tracking.

3. Check the Actual Downtime

Actual Downtime is pre-filled with the estimate. Change it if the estimate is wrong, add a description or photos, check the categories, then click Close Downtime.

⚠️ Heads-up: If the Downtime still has an open Assignment, Mobaro warns you. Closing the Downtime leaves the Assignment active, and the Location can be opened again unless something else critical for operation stops it.

To change the duration later, open the closed Downtime with Edit Downtime and click the pencil next to Duration. In Update downtime duration you can correct Started at and Resolved at, unlock the duration with Enable editing downtime duration to type your own, or click Use calculated downtime duration (shown when the saved duration differs from the opening-hours calculation). Then click Save changes.

How Downtime counts in reports

Dashboard widgets don't all treat unclosed Downtimes the same way:

Location MTTR MTBF counts every Downtime that started in the period. Downtimes that aren't closed have no duration, so they pull MTTR down.
Downtime by Category includes Open, Blocking, Resolved and Closed Downtimes by default. A Downtime without a duration counts its running time up to now. Use the widget's State filter to show closed Downtimes only.
Operational History Details counts closed Downtimes only.

See Downtime on Dashboards and MTTR and MTBF — Mobaro's reliability metrics.

Delete a Downtime

In the Downtime list, select the Downtime and click Delete Downtime. This needs Operations › Manage Downtime.

🛑 Critical: Deleting a Downtime can't be undone. The Downtime stops counting in your Dashboard figures and you can't restore it. If a Downtime was logged wrongly, correct it with Edit Downtime instead.

Set up permissions, Operational Logging, categories and automatic Assignments: How to Get Started with Downtime in Mobaro.
Enable Operational Logging and correct the uptime record: Utilizing Operational Logging.
Measure Downtime against real operating time: Add opening hours to a Location.
Review a Location's uptime periods: Reviewing downtime on the Locations page.
Understand the related operational-time metrics: Uptime, downtime, and lag time explained.

Best practices

Start the Downtime as soon as the Location stops, with a factual description, a category and a photo.
Close resolved Downtimes promptly and check the Actual Downtime before you confirm it, so MTTR and uptime reflect reality.
Correct wrong Downtimes with Edit Downtime rather than deleting them.

Frequently asked questions

How do I get a downtime report for a ride or for the whole park?

In the Backend, open Downtime and filter by time range and Locations to list one ride's Downtimes. For totals and trends, add the Downtime by Category or Location MTTR MTBF widget to a Dashboard. See Downtime on Dashboards.

Can I change the time of a downtime after it has been logged?

Yes, once it's closed. Open it with Edit Downtime in the Downtime list and click the pencil next to Duration to change the start, resolved time or duration. Before closing, set the right time in Actual Downtime in the Close Downtime dialog. Both need Operations › Manage Downtime.

Is there a way to close several downtimes at once?

No. In the Backend Downtime list you close Downtimes one at a time, so you can check each Actual Downtime before confirming it.

Can I track downtime against an asset?

No. A Downtime is always recorded against a Location. To see which part failed, describe it in the Downtime or in the Assignment linked to it.

Using downtime in Mobaro