A private session
One visit. One place.
A signed, HttpOnly browser cookie identifies the visit. Refreshing or opening another tab in that browser keeps the same place. Your visible reference cannot be used to claim it.
When everyone wants in, every place matters. A clear line, time to choose, and inactive places returned to the people still waiting.
Temporarily paused · event access is open.
Ticket selection
Next in line 3
Press play to watch, or confirm B2’s activity to keep its place.
Demo ready. B2 has 30 seconds of activity time left.
Illustration only. Three demo places; the normal queue policy has ten. No real sessions, tickets or queue positions are created. Other demo visitors confirm activity automatically.
Without confirmed activity
Without confirmed activity
A warning before inactivity expiry
A fixed browsing window
LESS REFRESHING. MORE CLARITY.
A place that belongs to your session, with simple rules everyone can understand.
Your browser receives a signed session. A short queue ID lets you recognise your visit without exposing its credential.
DEMO-A1B2-C3D4Example referenceSee people ahead, including visitors already choosing tickets. Stay connected and confirm activity before the warning ends.
When a place opens, the next eligible session is admitted. Your browsing timer starts, with ticket availability checked at checkout.
BUILT INTO THE FLOW
Identity, admission and expiry are checked on the server. The interface shows the result.
A private session
A signed, HttpOnly browser cookie identifies the visit. Refreshing or opening another tab in that browser keeps the same place. Your visible reference cannot be used to claim it.
Ordered admission
Join order is assigned on the server. Expiry and promotion happen in one atomic operation, so earlier eligible visitors are considered before new arrivals.
Activity acknowledgements
Connection checks alone don’t refresh activity. Interaction is acknowledged using a rotating, session-bound value; replaying an old acknowledgement doesn’t renew the timer.
Server enforcement
The server sets deadlines and checks admission before protected ticket purchases and holds. Changing your device clock or the countdown on screen cannot grant access.
A queue protects access order and limits idle occupancy. It cannot guarantee ticket availability or prove someone is human. Session checks and rate limits are layers of protection, with additional measures needed against distributed attacks.
Read the detailsGOOD TO KNOW
What happens to your place, your payment and your data.
Still need a hand?While the page is visible, taps, keyboard actions, touches and scrolling can trigger an activity acknowledgement. You can also use Keep my place. Moving the mouse or leaving a tab open does not reset the activity window. Only a successful server acknowledgement renews it.
A warning appears during the final 30 seconds. Without confirmed activity, your browsing or waiting place can expire. The next eligible visitor is considered at the next queue request. Rejoining gives you a new place at the back.
There is a short connection grace: two minutes while browsing and three while waiting. Your activity limit still applies. Reconnect before either deadline to keep a live place; reconnection cannot revive one that has already expired.
No. Activity can refresh the inactivity timer, but it never extends the fixed ten-minute browsing maximum. Once that window ends, you need to rejoin before starting a new checkout.
The queue does not cancel an already-created payment or remove its payment screen. A new checkout requires a current admitted session. Ticket stock and any reservation expiry are checked separately; a queue place is not a reserved ticket.
No. Signed sessions, rate limits and rotating acknowledgements limit specific forms of abuse, but activity signals can be simulated. These controls are not proof that a visitor is human, and distributed bot attacks need additional protection.
Fair Queue is currently paused because its shared provider is at a service limit. Event browsing and ticket access are open with signed guest sessions and local rate limits. The interactive demo shows the normal policy, not a live queue. Shared admission will only be restored after the provider has capacity and live entry is verified.
The queue uses a session-derived reference, join order, last connection and acknowledged activity times, deadlines and short-lived expiry reasons. It does not record what you type, pointer coordinates or the content of your interactions. This describes queue data, not every separate service on Pullup.
THE NIGHT STARTS HERE
Fair Queue is temporarily paused. Ticket access remains open.