Does refreshing push you back in the queue? How sold-out tickets and online queues really work

FOR KOR Chochim editorial team · November 4, 2026

Written as of November 4, 2026. How online queues behave follows Cloudflare's official developer documentation for its Waiting Room service. Korean train refund fees and waitlist assignment follow major Korean press reports, because Korail's official pages could not be read directly. We could not confirm which queue system any Korean ticket site uses, so this article does not claim that a specific site works this way.

The screen says "12,384 people ahead of you." The number barely moves. One friend says refreshing sends you to the back; another says opening more windows gets you in faster. When you finally get in, every seat is grey. Yet a few days later, the same show has a handful of empty seats. Where did those sold-out tickets come from?

This guide answers two questions using only what official documents and reports confirm: when and why cancelled tickets come back, and what decides your order in an online queue. Both turn out to be more about rules than luck.

How a queue remembers your place

Busy sites don't let everyone into the booking page at once. They park visitors in a waiting room first, because the servers can only handle so many people. Cloudflare, a web security and delivery company, sells such a service called Waiting Room and documents how it works. That doesn't mean Korean ticket sites use it, but it's a clear, official example of how online queues operate.

According to the docs, the site owner sets two numbers: how many users can be inside at once and how many new users may enter per minute. Once traffic exceeds them, newcomers go to the waiting room. When people inside finish or go idle, space opens and the next visitors get in. That's why the counter can stall and then suddenly drop.

So where is your place in line stored? Not on the server, but in your browser. Cloudflare gives each visitor a cookie (a small note a site saves in your browser), and in first-in-first-out mode that cookie holds the time you first reached the waiting room. That timestamp is your ticket number.

Does refreshing really push you back?

Here a common belief flips. In a Cloudflare-style FIFO waiting room, refreshing in the same browser does not change your number, because the order comes from the cookie's first-arrival time and refreshing doesn't delete the cookie. In fact the docs say the waiting page refreshes itself every 20 seconds to update the estimated wait.

What can send you back is coming in fresh without that cookie: a private window, another browser, or cleared cookies. The new browser has no ticket, so it gets a new, later timestamp. That's why "open lots of windows" doesn't reliably help; a window opened late holds a late number.

This is one company's documented behavior. A ticket site running its own queue may follow different rules, and many sites tell you not to refresh. Follow the site's instructions first. The safe takeaway: your order is usually fixed when you first join, so getting in right on the minute matters most.

But does arriving early always mean entering early? Not necessarily.

Not always first come, first served: random mode

Cloudflare lists four queueing methods: FIFO, random (visitors are picked at random from the waiting room), passthrough (everyone goes straight in), and reject (everyone sees a static page). In random mode, the docs explain that people who arrived earlier get more chances to be picked and so are more likely to get in before their estimated time, but order is not guaranteed.

The docs also say that while an event is in pre-queue, no one in the waiting room is let through. Being on the page early doesn't open the door before the start time.

You usually can't tell which mode a queue uses. Either way the right move is the same: join once on time and keep that window. Now, where do sold-out tickets come back from?

Cancelled tickets appear when the rules change

Seats return in two ways: people hand tickets back, or the system cancels bookings that weren't paid in time. Both happen at predictable moments.

Kyunghyang Shinmun reported that during the 2025 Lunar New Year booking, train tickets not paid by the deadline were automatically cancelled and given to people on the waitlist. So the moment right after a payment deadline is when seats are released. Concert bookings cancelled after an unpaid bank-transfer deadline follow the same pattern.

Refunds come with a fee clock. SBS Biz reported that from May 28, 2025, refund fees for Friday-to-Sunday and holiday trains in Korea became:

When refunded (Fri–Sun and holiday trains)	Fee
Up to 2 days before	400 won
1 day before	5% of fare
Departure day, up to 3 hours before	10%
3 hours before to departure	20%
Up to 20 minutes after departure	30%

Maeil Shinmun (October 2026) reported the same scale and added that Monday-to-Thursday trains are free to refund up to 3 hours before departure. People whose plans change will likely refund just before a fee step. That's an inference from the rules, not an official statistic, but it suggests checking right after each threshold.

Did the fees change behavior? BizWatch reported that after the weekend increase, the no-show rate fell from 4.1% to 3.4%. Maeil Shinmun reported that no-shows still left 202,000 seats empty over the 2026 Chuseok holiday.

The hidden line for concert tickets: 7 days after booking

In 2010 Korea's Fair Trade Commission had 13 online ticket sites stop charging fees on cancellations within 7 days of booking. The principle: cancel free within 7 days of booking, but if the show is fewer than 10 days away, a fee can still apply. Exact rates vary by show, so check each booking page.

Chochim checkpoint Fees and payment deadlines are judged by the ticket site's server clock. If your phone is a few seconds off, a refund you think is "still 3 hours before" may already fall into the next band. Check the site's time on Chochim first.

What you can do

In a queue, join once on time and don't switch to a private window or another browser. After a sellout, check right after payment deadlines and around fee thresholds, and for trains, put yourself on the waitlist. Never use bots or auto-refresh tools; most sites forbid them, and Korean law has tightened penalties for scalping since August 2026. See the ticketing guide.

FAQ

Will refreshing the waiting page lose my place?

It depends on the site. In a cookie-based FIFO queue like Cloudflare's, refreshing in the same browser keeps your order, and the page refreshes itself every 20 seconds. If the site says not to refresh, follow that.

Do more windows get me in faster?

A private window or another browser gets a new number at the moment you open it, so a late window stands further back.

When do cancelled train tickets appear?

After unpaid bookings expire, and around refund-fee thresholds: 2 days, 1 day and 3 hours before departure for weekend and holiday trains (per press reports of the May 28, 2025 rules).

In short

Queues cap users inside and users per minute, letting people in as others leave.
In a FIFO waiting room, your place is the first-arrival time in your browser cookie.
Switching to a fresh browser can give you a later number.
Cancelled seats tend to appear after payment deadlines and around fee changes.
Thresholds follow the site's server clock, so check it on Chochim.

Check server time