Across 3,930 posted-wait changes at Disney and Universal, Queue-Times showed the new number about 3½ minutes after Parky, on average. By then the line your guests are reading about has already moved.
WAIT CHANGES COMPARED3,930across Parky's ten Disney and Universal parks.
TWO MINUTES OR MORE BEHIND82%of every change Queue-Times showed.
MEDIAN RESPONSE41 msagainst 82 ms, from the same server.
How far behind Queue-Times ran
14.5%
51.8%
29.7%
3.9%Same minute as Parky
14.5%Up to 2 minutes behind
51.8%2 to 5 minutes behind
29.7%5 minutes or more behind
We gave Queue-Times every benefit of the doubt: a change only counts against it at its next poll after Parky's stream sent the change.
Only in Parky
/lightning-laneLightning LaneReturn times and prices for every ride that sells it.
/hoursPark hours and showtimesFrom Disney's and Universal's own calendars, up to 60 days out.
/historyWait historyEvery change in a ride's posted wait over the last 7 days.
/reliabilityRide uptime and breakdownsEach ride's last 30 days: uptime, outages a day, average and longest outage, least reliable first.
/crowdsCrowd forecast by dayA 1 to 10 level with a low–high range, up to 30 days out.
wss://…/streamLive stream without a keyOpen a WebSocket and get each change pushed within a second. No signup.
/busesBusesWalt Disney World departures, in the same API and with the same key as waits.
/park-availabilityPark reservations and hotel availabilityKnow a day is bookable before you send guests to plan it.
IN THE APIPARKYQT
ONLY PARKY8
Lightning Lane return times and prices✓—
Park hours and showtimes✓—
Live stream✓—
Wait history7 DAYS—
Ride uptime and breakdowns a day✓—
Crowd forecast by day✓—
Buses✓—
Park reservations and hotel availability✓—
BOTH2
Live waits and status✓✓
Single Rider✓✓
ONLY QUEUE-TIMES1
Parks outside the US—✓
Every number
QUEUE-TIMES VS PARKY’S CLOCK
Behind Parky, on average3 min 34 s
Behind Parky, typical4 min
Slowest 10% of changes6 min+
5 minutes or more behind30%
Wait changes compared3,930
HEAD TO HEADPARKYQT
Median responsePARKY41 ms82 ms
Slowest 5% of responsesQUEUE-TIMES366 ms267 ms
Rides with a posted wait, in Parky's ten parksPARKY212208
ParksQUEUE-TIMES10140
Which one to use
USE PARKY IF
You show Disney World, Disneyland, Universal Orlando or Universal Hollywood.
You need near-instant wait data.
You want breakdowns, crowd forecasts, buses or reservations without a second source.
USE QUEUE-TIMES IF
You need parks outside the US, or any of its 140 parks beyond Parky's ten.
A wait a few minutes old is fine for your users.
Switching takes one URL
Parks are plain keys like magic-kingdom, so there’s no ID to look up first.
BEFORE · QUEUE-TIMES
const res = await fetch(
`https://queue-times.com/parks/${parkId}/queue_times.json`
);
const { lands } = await res.json();
for (const ride of lands.flatMap((land) => land.rides)) {
show(ride.name, ride.wait_time);
}
AFTER · PARKY
const res = await fetch(
"https://api.parkypass.com/v1/parks/magic-kingdom/waits"
);
const { rides } = await res.json();
for (const ride of rides) {
show(ride.name, ride.wait_minutes);
}
Free, including commercially, as long as every page that shows the data links to parkypass.com.
How we measured
We polled both APIs once a minute for every park and logged each change in a posted wait. A change counts for Parky at Queue-Times' next poll after Parky's stream sent it, so Queue-Times never starts behind. Response times were measured from the same server for both.
Live waits in two minutesNo key needed to start. A free key raises you to 20,000 requests a day.
