A ride "breaking down" on parkqueuetimes.com means the park's own feed reported it closed during opening hours for ten minutes or more. Uptime is the share of the park's operating minutes a ride was actually running, averaged over the last 60 operating days. Every park's reliability page shows both, ranked worst first, with the hour of day closures cluster in. Below: how those numbers are made, why rides go down, and how to use the live board so a closure costs you a coffee rather than an afternoon.
What uptime and downtime mean here
Every park has a reliability page, for example Alton Towers, Thorpe Park and Magic Kingdom. The definition at the bottom of each is identical and worth quoting directly: "Uptime is the share of the park's own operating minutes a ride was running, recorded every few minutes and averaged over 60 days."
Two things in that sentence matter. It is measured against the park's published hours, not a 24-hour day, so a ride closing early on a 5pm day counts against it and the hours after the park shuts do not. And it is recorded at the same cadence as the live board, so a stop that falls between two readings can be missed; if anything, uptime is slightly generous.
The page sorts rides into four bands, excellent (95% and up), good (85 to 94%), patchy (70 to 84%) and poor (under 70%), and gives the park an overall verdict on the same scale.
Downtime is the other side of the coin: the "ride hours lost" figure adds up every closed minute across every ride as a share of the park's total ride hours. A park that lost 20% had, on average, one ride in five shut at any moment.
How a breakdown is counted
The page's own words: "A closure counts as one breakdown when it lasts ten minutes or more; shorter stops still count towards time lost, because a two-minute reset is not a fault."
A coaster that stops for three minutes while an operator clears a dropped hat is not a breakdown. Those minutes come off its uptime, but only a closure of ten minutes or longer adds to the count.
The page also merges touching closure windows into one, because a ride shut all day arrives from the feed sliced into the sampling interval, and counting each slice would report one bad day as a hundred breakdowns. This is why Vortex at Thorpe Park shows 0.6% uptime with only 7 breakdowns: it has been shut for almost the whole window, 21 days and 7 hours lost, as a handful of very long closures. The page does not say why, and nor should you assume.
Late starts are separate
A ride that is not running when the park opens is not counted as a breakdown. The page calls this a late start and keeps it in its own tally: "Rides that are not running at opening are counted separately as late starts, not as faults." A ride that opens 40 minutes after the gates is usually finishing its morning checks or waiting for a crew, not failing, and your response is different: do something else first rather than writing it off. The hour-by-hour chart excludes late starts for the same reason, and drops closures that begin in the park's final hour, since those are rides finishing their shift.
Weather closures are included
The page is explicit: "Water rides close in heavy rain, and exposed coasters close in lightning, high winds or very cold temperatures. These figures reflect actual operations including weather closures, which is why uptime varies through the year."
That is the right call for a planning tool: a shut coaster is shut whether the cause is a sensor or a storm. It also means a window with a stormy fortnight in it looks worse than a dry August, so read the date range at the top of the page before comparing parks.
Three parks, same window
The three pages below all cover the same 60 operating days, 13 July to 10 September, so the figures are directly comparable.
| Park | Uptime | Verdict | Least reliable ride | Breakdowns / late starts |
|---|---|---|---|---|
| Alton Towers | 79.6% across 40 rides | Patchy | Skyride to Forbidden Valley (from Towers St.), 47.8% | 1,962 / 1,011 |
| Thorpe Park | 78% across 22 rides | Patchy | Vortex, 0.6% | 1,079 / 442 |
| Magic Kingdom | 87.4% across 24 rides | Good | Main Street Vehicles, 55.2% | 1,064 / 178 |
The least reliable "ride" at two of the three is transport: the Alton Towers Skyride and the Main Street Vehicles at Magic Kingdom. Cable cars and vintage vehicles close for wind and crowds in ways coasters do not, and drag the park average down without touching the rides most people came for. Look past the headline verdict to the rides you actually want.
The headline coasters are mostly fine. At Alton Towers, Wicker Man ran 94% and Nemesis Reborn 87.5%; at Thorpe Park, Hyperia ran 91.4%. The one to watch is Stealth: 84.8% uptime but 99 breakdowns in 60 days, the most at the park, against only 3 days and 6 hours lost, which is well under an hour each. It goes down often but rarely stays down, exactly the profile where waiting nearby pays off.
Time of day matters too. At Alton Towers, 706 of 1,837 recorded closures started in the 5pm hour; at Magic Kingdom the peak was 4pm and at Thorpe Park 1pm. The page draws the obvious conclusion: the ride you most want is safest earlier in the day, not saved for last.
Why rides break down
The reliability pages tell you what closed and when, not why, because most park feeds do not say. The causes fall into a few groups.
- Sensor and control faults. Coasters are wrapped in sensors checking every block of track, restraint and brake, and if one reads wrong the ride stops itself. Most are cleared in minutes, which is why the ten-minute rule exists; a sensor that needs replacing can cost an afternoon.
- Weather limits. Tall coasters have wind speed limits, exposed rides shut for lightning, and water rides go down in heavy rain and cold. This is the main reason uptime shifts with the season.
- Staffing. A ride needs a minimum crew. A park short of staff opens a ride late or for part of the day, which shows up as a late start or a long closure.
- Scheduled maintenance. Rides are pulled for planned work, for a day or for months. From the feed this looks identical to a breakdown, and it is what a ride near 0% uptime usually means.
- Guest-related stops. A phone on the track, someone unwell in the station, a restraint check that fails. Short, frequent and mostly under ten minutes.
What happens when a ride reopens
The queue does not come back gradually. When a headline coaster reopens, everyone hovering nearby, plus everyone watching the app, converges at once, and the posted wait can jump from nothing to its usual afternoon level within minutes. If you are within a couple of minutes of the entrance when it reopens, you are at the front of that surge instead of the back.
The practical version:
- If a ride you want goes down and you are close, give it 15 to 20 minutes on something adjacent before walking away.
- If it has been down for over an hour with no reason shown, move on and set an alert (below).
- When it reopens, go straight there. Do not finish lunch first.
The reverse is also true: a ride going down empties its queue into its neighbours, which get busier for the next hour. The live board shows this happening.
Using the live board and alerts
The live page for each park, for example Alton Towers, shows every ride as open, closed or walk-on, with the reason where the park provides one, refreshed every few minutes. The "rides open" count at the top tells you at a glance whether the park is having a bad day.
Alerts need a free account. You can ask to be told when a ride reopens, goes down, or drops under a wait you set. The reopen alert is the one for a day around breakdowns: set it the moment a ride goes down, do something else, and your phone tells you when the feed starts reporting a wait again. Park Queue Times Plus adds a "crashes" alert for a sudden fall with no threshold to guess, but the reopen and queue-drop alerts are free.
Two habits help. Set reopen alerts for your two or three must-ride attractions before you enter, not after they break. And check the reliability page the night before: if the ride you care about carries a "down on 60 of 60 days" line, assume it will go down at some point and plan a fallback.
Closed all day versus 0 minutes
These look similar on a phone and mean different things.
A ride showing closed from park open with no reason is usually one of three things: a late start (check back in an hour), scheduled maintenance (closed for days on end, and near 0% on the reliability page), or a genuine fault the park has not explained. The park's hours page and its own website are where to look for a published refurbishment.
A ride showing 0 minutes, which the site labels walk-on, usually means exactly that. First thing in the morning and in the last hour of the day it is common and real. But some park feeds report a closed ride as a plain 0 rather than a closed status, so a 0 on a headline coaster mid-afternoon, while everything around it shows 40 minutes, is more likely a stopped ride than a free one. Walk over and look; do not sprint.
Questions people ask
Does a short stop count as a breakdown?
No. A closure has to last ten minutes or more. Shorter stops still take minutes off the ride's uptime, but are not counted as faults, because a brief reset is normal operation.
Why is a transport ride the least reliable at a park?
Cable cars, trains and trams close for wind, crowds and staffing far more often than coasters do, and the site tracks them like any other ride. That is why the Skyride tops the Alton Towers list and Main Street Vehicles tops Magic Kingdom. Read the ranking for the rides you care about rather than the park average.
Are weather closures included in uptime?
Yes. The figures reflect actual operations including weather closures, so a wet or windy fortnight lowers a park's uptime for the whole 60-day window. Check the date range at the top of the page before comparing parks.
Should I wait by a ride that has just gone down?
If you are close, yes, for 15 to 20 minutes. Many closures are short, and the queue surges the moment a ride reopens, so being nearby puts you ahead of it. If it has been down longer than that, set a free reopen alert and go elsewhere.