Statuses and freshness
Ride status
A ride’s status is the park’s own status, in uppercase, except lowercase "unavailable", which Parky adds when it has no live feed for that ride. wait_minutesis a number only while a posted wait exists; it is never 0 for “unknown”.
OPERATING | Running. wait_minutes is the posted standby wait. |
|---|---|
DOWN | Temporarily stopped during the day. It usually returns. |
CLOSED | Closed for the day, or the park is closed. |
REFURBISHMENT | Closed for a planned refurbishment. |
UNKNOWN | The park reported the ride without a usable status. |
unavailable | Lowercase on purpose: Parky added it because it has no live feed for this ride right now. |
Park data_status
Every waits response and stream message says whether the park’s feed is current:
live | The park's direct feed answered within the last 90 seconds. The numbers are current. |
|---|---|
unavailable | The feed is not current. Rides carry no waits rather than old ones; try again shortly. |
checked_at is when Parky last read the feed and data_age_secondshow long ago that was. A ride’s changed_at is when its value last changed, not how fresh it is: a 20-minute-old changed_at on a live park means the wait has held for 20 minutes.
How often it updates
The server checks every 5 seconds and pushes a ride only when Disney or Universal changes it; posted waits usually change every few minutes, so quiet minutes are normal. REST responses for live data are cached for 15 seconds; everything else for 5 minutes.
Timestamps
Timestamps are UTC ISO 8601 strings, as JavaScript's toISOString() writes them (2026-10-05T16:42:10.311Z). Parse them before comparing or doing arithmetic.