IRCTC Tatkal at 10 AM: What Happens in the First 60 Seconds

I've never booked a Tatkal ticket myself. But I've watched my friends do it. Phone in hand before 10, passenger details ready, eyes on the clock, nobody allowed to talk. All that waiting for one ticket, and it gets decided in about a minute.

Watching them, I kept asking myself one question. What is actually happening on the other side of that button?

So here's what happens during IRCTC Tatkal booking at 10 AM, in short. Your tap first hits a CDN and a bot filter, because up to half the logins at that moment are bots. Then it reaches the Passenger Reservation System (PRS), which could handle about 32,000 tickets a minute until a cloud upgrade began rolling out in August 2026. Your seat is only locked after your payment comes back, so a slow bank step can cost you the berth.

That's the whole thing in one paragraph. Now let's slow the first minute right down and watch it second by second.

TL;DR

• Tatkal opens at 10 AM for AC classes and 11 AM for non-AC classes, one day before the journey.
• Agents are blocked for the first 30 minutes, so at 10:00 you're up against other passengers. And bots.
• Up to 50% of login attempts in the first five minutes of Tatkal are bots, according to Indian Railways.
• The old PRS maxed out around 32,000 tickets a minute. Its record is 31,814, set on 22 May 2025.
• The seat is confirmed after payment, not when you tap "Book". That gap is where most people lose.
• The new cloud PRS handles 1.5 lakh bookings a minute. That fixes speed, not the number of berths.

A quick note before we start: the timestamps below are for illustration. Every number inside them comes from Indian Railways, PIB or IRCTC.

What are the Tatkal rules at 10 AM, before anything happens?

Let's set the stage first, because the rules decide who's even allowed in the room.

• Timing: AC classes (2A, 3A, 3E, CC, EC) open at 10:00 AM. Sleeper and 2S open at 11:00 AM. Both open one day before the journey date from the train's starting station.
• Price: Tatkal adds 10% of the base fare for 2S and 30% for every other class, with caps. Sleeper pays ₹100 to ₹200 extra, 3A pays ₹300 to ₹400, and 2A pays ₹400 to ₹500.
• Limit: Max 4 passengers per Tatkal PNR.
• Refund: A confirmed Tatkal ticket gets no refund if you cancel. The exceptions are a train running more than 3 hours late, a diverted train, or the railway failing to give you the class you paid for.
• Agents: Barred from 10:00 to 10:30 (AC) and 11:00 to 11:30 (non-AC).

And the big one. Since 1 July 2025, only Aadhaar-authenticated users can book Tatkal on the IRCTC website and app. From 15 July 2025, an Aadhaar OTP became mandatory for every online Tatkal booking. Counter and agent bookings need an OTP too.

Keep that OTP in mind. It shows up again in a few seconds.

9:59:00. Who is already waiting?

Three kinds of people are staring at that button.

1. You. Plus a few lakh people just like you. For context, IRCTC averaged 82.57 lakh logins a day in FY 2024-25, up 19.53% in a year. Tatkal is when a big chunk of that traffic hits all at once.

2. The agents. They're locked out until 10:30. That rule exists because agents used to grab seats in bulk in the opening seconds.

3. The bots. This is the part most people don't know about.

Indian Railways itself said in June 2025 that bot traffic makes up up to 50% of all login attempts during the first five minutes of Tatkal.

Half. Every second login at 10 AM wasn't a person. It was a script that fills forms faster than your thumb ever will.

So how do you stop a crowd that's half robots?

10:00:00. Where does your tap actually go first?

Not to the booking system. That surprises people.

Your tap first lands on a CDN, a Content Delivery Network. Think of it as a string of photocopy shops spread across the country. The logos, the page layout, the scripts, all the stuff that looks the same for everyone, gets served from the shop nearest you. IRCTC says 87% of its static content now comes from a CDN, so the main servers don't waste energy sending the same logo to lakhs of phones.

Next comes the bouncer. IRCTC uses anti-bot tools from Akamai that look at each request and decide if it's a human or a script. Behind that sits a web application firewall, network firewalls, and DDoS protection spread across several internet providers with a combined capacity of about 30 Gbps.

The bouncer is busy. Look at what Railways told the Rajya Sabha in February 2026:

Month	Total requests	Bot requests
July 2025	9.06 billion	5.03 billion
September 2025	19.04 billion	12.05 billion
October 2025	24.04 billion	17.00 billion
December 2025	14.28 billion	7.25 billion

October 2025 had 17 billion bot requests out of 24 billion. That's around 70%. In the six months up to December 2025, 60.43 billion bot requests were blocked in total.

This is the first big idea. Most of what IRCTC fights at 10 AM isn't humans. It's scripts. Blocking them at the door is what keeps the actual booking engine alive.

10:00:05. Why is there a CAPTCHA and an Aadhaar OTP?

You get past the bouncer. Now the app wants a CAPTCHA and, for Tatkal, an Aadhaar OTP.

These feel annoying at 10 AM. But each one blocks a different trick.

The CAPTCHA stops scripts from hammering the login. Railways says CAPTCHA runs "at multiple levels" to block scripting, brute force login attempts and DDoS traffic.

The Aadhaar OTP stops something sneakier: fake accounts. Before this rule, one tout could run hundreds of IRCTC IDs, each booking its own 4-passenger Tatkal ticket. Aadhaar adds a uniqueness check, one real person per account. Railways calls it a constraint against "account multiplication".

The cleanup numbers show how bad the problem was:

• 2.5 crore suspected user IDs deactivated by June 2025
• 3.03 crore suspicious user IDs deactivated across 2025
• 12,819 suspicious email domains blocked in 2025
• 376 complaints filed on the cyber crime portal, covering 3.99 lakh suspicious bookings

Crores of accounts. Not lakhs. Crores.

So now we're down to mostly real people. And now they all want the same berths at the same time.

10:00:20. Can the reservation system handle everyone at once?

This is the part everyone blames when Tatkal goes badly.

Behind the IRCTC app sits the PRS, the Passenger Reservation System. It's older than most of us. PRS started in 1986, built by CRIS (Centre for Railway Information Systems). It manages seat allocation, waitlists, RAC, charts and enquiries. IRCTC is the shop window. PRS is the godown where the berths actually live.

The PRS version running through most of this era was deployed in 2010 on Itanium servers with the OpenVMS operating system. Railways' own August 2026 note says it "was designed for a different scale of digital demand".

Its ceiling was roughly 32,000 tickets a minute. And it hit it. On 22 May 2025, it booked 31,814 tickets in a single minute, the highest ever.

Here's why that ceiling matters at Tatkal. Imagine one railway counter clerk who can print exactly one ticket a second. On a normal morning, the queue moves. At 10 AM, lakhs of people try to reach the counter in the same minute. Often nothing has "crashed". The clerk is working at full speed while the line grows faster than the printer.

That's what a slow Tatkal page often is. The system isn't dead. It's full.

And the seat itself? When you book, PRS has to check the train's Tatkal quota, find a free berth, and mark it taken so nobody else gets it. That last step can't be split. Two people can't both get berth 23 in B2. So for any one berth, bookings have to be settled one at a time. Adding more web servers in front doesn't change that.

10:00:40. Is the seat yours once you tap "Book"?

No. And this is where most people lose.

You filled details, entered the OTP, and tapped Pay. Now your request leaves IRCTC and goes to a payment gateway, then to your bank, then back. If you pay by UPI, there's a whole chain behind that too (I broke it down in how UPI works).

While your money travels, the Tatkal berths are still being handed out to whoever finishes first.

We know this because of IRCTC's own "money debited but ticket not booked" notice. It lists a case where the payment settles, but the ticket isn't booked because the berth you asked for was no longer available. In plain words: the booking is completed only after the payment comes back, and by then your berth can be gone.

What happens to your money then?

• Payment settled, ticket not booked: IRCTC sends it back the next day, and your bank credits it within 2 to 3 working days.
• Settlement failed: The money never reached IRCTC. It's with your bank, and the bank refunds it after checking.

So no, the money isn't lost. But the berth is.

This is also why that "choose berth preference" box is risky in Tatkal. If you insist on a lower berth and only upper berths are left, IRCTC's notice counts that as a reason for "ticket not booked".

10:01:00. Why does it already say WL?

One minute in, most AC Tatkal quota on a popular train is gone.

It's tempting to blame bots or servers for all of it. But even with zero bots and an infinitely fast server, the math wouldn't change much. Tatkal is a fixed quota of berths on each train. Say 4,000 people want 60 Tatkal berths in 3A. Then 3,940 people will be disappointed. The only question is how fast they find out.

A faster system just tells you "WL" sooner.

One interesting detail from the Railways rulebook: the same Tatkal berth can be sold in multiple legs of a journey before charting. So if someone books a Tatkal berth for only the first half of the route, the same berth can still be sold for the second half. Whatever stays unused at chart time gets released to RAC and waitlisted passengers.

What changes with the new cloud PRS in 2026?

This is the good news.

Railways is replacing the 2010 PRS with a cloud-enabled, next-generation PRS. The numbers:

	Old PRS	New PRS
Bookings per minute	~32,000	1.5 lakh+
Enquiries per minute	~4 lakh	40 lakh+

That's about 5x booking capacity and 10x enquiry capacity. Trains started moving onto it in phases in August 2026. Railways also launched a beta of the new IRCTC website on 15 July 2026, with fewer CAPTCHAs, fewer steps and saved passenger details.

And the old system is still getting pushed hard. On 7 September 2026, PRS booked 22,26,786 tickets in one day, beating the previous record of 20,45,272 from 19 August 2025.

My honest take? The new PRS will make Tatkal feel less broken. Fewer spinning screens, fewer "service unavailable" pages, faster answers. But it can't add berths to a train. It speeds up the queue. It doesn't shorten it.

So what can you actually do at 10 AM?

None of this is a hack. It's just not wasting the seconds you do control.

1. Do the Aadhaar authentication days before. Link your Aadhaar to your IRCTC profile early, and keep your phone handy at 10 so the OTP doesn't slow you down.
2. Save passengers in your master list. Typing four names at 10:00:30 is how you lose.
3. Log in at 9:55-ish, not 10:00. You'll clear the login rush and CAPTCHA before the flood.
4. Skip strict berth preference. A middle berth beats WL.
5. Keep a fast payment method ready. A payment that stalls for 40 seconds gives your berth to someone else.
6. Don't touch "Tatkal software" or shady agent IDs. Those are exactly the accounts in the 3 crore that got deactivated. Use a strong, unique password for your IRCTC account too. This free password generator makes one in a click.

If you're a developer, look at this system once more. A CDN out front, a bot filter, OTP for identity, a 40-year-old reservation core, a payment round trip, and a cloud migration done while the trains keep running. That's a whole system design course hiding inside one 10 AM tap.

Frequently Asked Questions

What time does IRCTC Tatkal booking open?

Tatkal booking opens at 10:00 AM for AC classes and 11:00 AM for non-AC classes like Sleeper and Second Sitting. It opens one day before the journey date, counted from the train's originating station. Authorised agents cannot book in the first 30 minutes of each window.

Is Aadhaar mandatory for Tatkal booking on IRCTC?

Yes. Since 1 July 2025, only Aadhaar-authenticated users can book Tatkal tickets on the IRCTC website and app. Since 15 July 2025, an Aadhaar-based OTP is also required for every online Tatkal booking. Counter and agent Tatkal bookings need an OTP sent to the mobile number given at booking.

Why do Tatkal tickets get sold out in one minute?

Each train has a fixed Tatkal quota, and far more people want it than there are berths. Bots added to the rush, making up to 50% of login attempts in the first five minutes before Railways cracked down. The old reservation system also topped out around 32,000 tickets a minute, which a big Tatkal rush can hit.

Money was deducted but my Tatkal ticket was not booked. Will I get a refund?

Yes. If the payment settled but no ticket was booked, IRCTC returns the money the next day and your bank credits it within 2 to 3 working days. If the payment never settled with IRCTC, the money is still with your bank, and the bank refunds it after verification. You don't need to file a TDR, because there's no PNR.

Can I get a refund if I cancel a confirmed Tatkal ticket?

No. Confirmed Tatkal tickets get no refund on cancellation. You get a refund only if the train is more than 3 hours late, runs on a diverted route, or you aren't given the class you booked. Waitlisted Tatkal tickets that don't get confirmed are refunded.

Curious how the payment half of your booking works? Read how UPI works, myth by myth.

Written by Adithya Guttha, Founder of Art of Code.