As has already been mentioned so far in this topic, RideTimes isn't always the best tool to use when gauging actual downtime as a) it is only updated every 30 minutes and b) just because an attraction is listed as closed it doesn't necessarily mean it has a technical issue.
I believe at least one of the occasions where The Smiler was shown as being closed was a result of a guest illness. The attraction was closed while it was cleaned up and when RideTimes updated the clean-up was still ongoing so it was showing as being closed for the next half an hour.
Totally agree with you there.
It does however give us at least a rough overall picture of what is going on, especially for the extended lengths of downtime experienced. It is clear to see the difference in uptime records between say Nemesis or Galactica, and Oblivion or Spinball Whizzer this season. From my experience of collecting this data for the past year, ridetimes is not usually updated to show "closed" for short cleanup type delays, however it obviously depends on the member of staff responsible, and it does happen from time to time.
Interestingly, "closed" is actually updated more frequently than every 30 minutes, and only the actual wait times have a 30 minute delay on being updated. An odd set up indeed, but the website tech hasn't been changed in years! I do however only collect data from the website every 30 minutes so as to not unnecessarily spam it with data requests, so some of the "0.5 hour" downtimes may have actually only been minutes in reality, I will accept.
So the numbers are not to be taken as "exact", and are just a summary of what was published onto the website