Ticket tips and Tricks for 2025 festival

[MilkyJoe]

22 minutes ago, Someoni said:

Logging on after 6 or 7 years to see this monumental change!

Welcome back.🙂

[Someoni]

20 minutes ago, MilkyJoe said:

Welcome back.🙂

Thank you! Going for tickets for the first time in years and it's the year of the change. Apparent fairness, equality is disappointment. Love it. 

 

Trying to rope my 3 other cohorts into my military device and ip plan but feel like it'll  just be me on next week..

[MilkyJoe]

19 minutes ago, Someoni said:

Thank you! Going for tickets for the first time in years and it's the year of the change. Apparent fairness, equality is disappointment. Love it. 

 

Trying to rope my 3 other cohorts into my military device and ip plan but feel like it'll  just be me on next week..

Good luck, I feel we may all need some. 

 

If you have nobody to help you try for tickets you can have a look at this thread here and see if there's any groups with spare slots. Would probably do it sooner rather than later though and remember you'll have to commit to the cause and try for everybody else in your group too.

 

Another point worth mentioning if you go down this route is that you couldn't be in a group and have separate friends trying for just you alone as if they got through it would mess up the whole group if somebody else got through. Anyone you rope into helping would have to be prepared to try for the whole group too.

[Nobody Interesting]

2 hours ago, Suprefan said:

oasis wasnt calm for anyone

I was very calm.

[charlottelydrose]

Are we supposed to refresh on payment page or are we avoiding pressing refresh the entire process?

[Ayrshire Chris]

5 minutes ago, charlottelydrose said:

Are we supposed to refresh on payment page or are we avoiding pressing refresh the entire process?

Only refresh when the all tickets allocated message appears. Refreshing when you are waiting in the queue will bump you to the end of the queue.

in a previous sale the payment page froze when I put in details and I hit the back button and it restarted. I’d be scared to do that now. 

Edited Sunday at 09:13 AM by Ayrshire Chris

[charlottelydrose]

Yeah I would 

42 minutes ago, Ayrshire Chris said:

Only refresh when the all tickets allocated message appears. Refreshing when you are waiting in the queue will bump you to the end of the queue.

in a previous sale the payment page froze when I put in details and I hit the back button and it restarted. I’d be scared to do that now. 

Yeah I would be scared to refresh.. that's what happened to me with Oasis, I had tickets in my basket within minutes but the payment screen froze and I refreshed and went to the back of the queue. It was painful

[charlottelydrose]

I'm unsure how we 'log in' to see tickets prior, I can log into see tickets from their website but I can't see an option from the Glastonbury see tickets page? 

[Sorcha17]

14 minutes ago, charlottelydrose said:

I'm unsure how we 'log in' to see tickets prior, I can log into see tickets from their website but I can't see an option from the Glastonbury see tickets page? 

You don't log in, you'll just need your registration details when you get through to the booking page

[Jack.194]

On 11/7/2024 at 3:14 PM, gsp8181 said:

Here's how it's working

 

You go onto glastonbury.seetickets.com. You'll hit an Akamai CDN which is protected with Akamai Bot Manager

 

It will calculate an initial score for you based on your hostname, IP address, useragent, ISP, and how many people are going through that IP. So if you're going through something dodgy like a cloud datacentre or a commercial VPN you'll be a lot higher. If you're going through a mobile network AND are a mobile phone you'll probably be given more leeway.

 

If your score is too high you'll be instantly blocked, if you're in the mid zone you'll be 'flagged', and if it's low you'll be let on instantly.

 

If you're in the midpoint you can usually tell because the first time you log into the website you'll see a short delay before you get on while it 'fingerprints' your browser. Whereby it uses Javascript to gather all the information it can and can identify you with surprising accuracy, from stuff like, do you have any custom fonts, what plugins do you have in your browser, to the weirder stuff like drawing animations and analysing them to see if your graphics card has any minute differences. So they can track you if you've got firefox and chrome on the same machine.

 

Akamai will then set a load of cookies to link you to a session.

 

They'll then continuously run the fingerprinting script to watch for changes. So if you transfer any queue cookies to another browser they'll figure it out pretty fast when suddenly that browser starts giving completely different information. It will also look at stuff like your mouse pattern and you tabbing in and out to build a behavioural pattern

 

They analyse it all serverside with machine learning to compare what you're doing, to that of a typical user and bot.

 

They can also link you to activity on previous Akamai sites to work out if you're bot like or not.

 

If it thinks you're a bot it will flag you for a ban which doesn't happen instantly but typically in a minute or two.

 

If you clear the cookie it will just refingerprint you and then ban you again.

 

Queue-It is integrated into the Akamai suite and uses Akamai session handling.

 

If you're on something that meets a typical shared IP pattern such as a CGNAT like using a phone on mobile data or on a work computer they will give you a lower score and more leeway basically. If you're logging on from those AWS instances you spun up you'll be given a high score. Plus like you might have different drivers, fonts, setups, running different mobile os versions, bought different device models, languages etc. If you're doing something it considers weird like running Linux, or keeping the tab in the background you'll be given a higher score.

 

My friends got a screen reader and triggered it trying to register so I guess they've got it on a pretty high setting. I emailed them to tell them

 

Also interesting is that the SeeTickets side after the CDN is not changed at all and still has the 'youre on a holding page, refresh in 20 seconds' active which I saw triggered the other day.

 

So i'm guessing the queueit will block access to the website until you're at the front of the queue and then give you a 10 minute token to access it normally

 

If they don't properly clear the queueit session then you will be able to buy as many tickets as you like in those 10 minutes

 

A lot of it is similar to how those click here if you're a human boxes work, sometimes they let you straight on because you look like a typical user from a typical network and haven't done anything funny, sometimes they might ask you to solve a picture puzzle if you're on a shared network, and if you're on a VPN it will blast you with tons of pictures that it intentionally makes very grainy to try and trip you up

 

I do DevOps work and have seen some presentations from their competitor so figured out how this ones working

This is incredibly helpful. Is this the same system that was used for the Oasis sale?

[dirtysteve]

4 hours ago, Suprefan said:

oasis wasnt calm for anyone

 

Agreed. It's going to be a nail biting experience, as always, doubtless compounded by the feeling of comparative helplessness we'll all have (can't spam F5 to try and proactively improve our chances) and also by the inevitable technical issues that will occur on the day. It's not going to be any less stressful than the old system, of that I'm certain. 

[Crazyfool01]

Should all know our fates this time next week .... 

[tarw]

I don’t know why people in big groups are panicking so much. Yes you won’t be able to hit back and sort out the other groups but you still have an advantage. 
If there are 36 in your group that’s 36 entries in the queue ballot. When 1 group is successful then the other 5 members of that group who already have a queue position start trying for the next group. So you then have 35 people trying  for 30 tickets. When the next group secure tickets you have 34 people in the queue trying for 24 ticket. 
 

it’s still a big advantage 

[MilkyJoe]

5 minutes ago, Crazyfool01 said:

Should all know our fates this time next week .... 

Assuming no issues with the new system and the sale is done in 2 hours.....

[Crazyfool01]

1 minute ago, MilkyJoe said:

Assuming no issues with the new system and the sale is done in 2 hours.....

see highlighted word 🙂 

[Expectedtofly]

11 minutes ago, tarw said:

I don’t know why people in big groups are panicking so much. Yes you won’t be able to hit back and sort out the other groups but you still have an advantage. 
If there are 36 in your group that’s 36 entries in the queue ballot. When 1 group is successful then the other 5 members of that group who already have a queue position start trying for the next group. So you then have 35 people trying  for 30 tickets. When the next group secure tickets you have 34 people in the queue trying for 24 ticket. 
 

it’s still a big advantage 

Ah yes, but the probability has changed.

 

Assume that the 36 are spread evenly over the entire queue.  Then only a certain number of these 36 have any real chance of getting tickets.  Once those that could get tickets have got their tickets, that's them done, they won't be able  to continue to get tickets.   So there is a high chance that some of those in big groups won't get tickets.

 

Whereas before,  not only did all 36 have a chance of getting tickets, those that did get tickets could keep trying.  There is also a slight advantage in that the people in big groups knew how to tip the technicalities in their favour.

 

I'm sure somebody with A level maths could work out the probabilities.  But certainly, the probabilities have changed.

 

 

[tarw]

3 minutes ago, Expectedtofly said:

Ah yes, but the probability has changed.

 

Assume that the 36 are spread evenly over the entire queue.  Then only a certain number of these 36 have any real chance of getting tickets.  Once those that could get tickets have got their tickets, that's them done, they won't be able  to continue to get tickets.   So there is a high chance that some of those in big groups won't get tickets.

 

Whereas before,  not only did all 36 have a chance of getting tickets, those that did get tickets could keep trying.  There is also a slight advantage in that the people in big groups knew how to tip the technicalities in their favour.

 

I'm sure somebody with A level maths could work out the probabilities.  But certainly, the probabilities have changed.

 

 

But surely before not everyone would get tickets as well. You could improve your chances by f5ing at the optimum rate but just as all 36 won’t have a guaranteed position in the queue not all 36 used to get through 

[Expectedtofly]

12 minutes ago, tarw said:

But surely before not everyone would get tickets as well. You could improve your chances by f5ing at the optimum rate but just as all 36 won’t have a guaranteed position in the queue not all 36 used to get through 

 

Yes, I agree.  

 

I guess its just more cut and dried now.

For example.  Say, for simplicity and  arguments sake, only the first 10% in the queue get tickets.

In a team of the 36.  3 (or maybe 4) people will actually get tickets.  So that would only be 18 of the 36 strong group who will get tickets.

 

That is indeed an advantage over a group of 6 only have a 50% chance of getting tickets.  But not much of one.  Because the group of 36 also only have 50% chance (plus the slightly higher chance of having a 4th person in the top 10%).

 

[EDIT]  I've changed my mind there is no advantage of a team of 36 over a team of 6.  Other than the pyramid scheme advantage, ie you are at the top of the spreadsheet!!!

 

 

Whereas before it was much more nuanced, with all 36 continually trying until the tickets run out.  Also they had the advantage of persistence, motivation and technical knowledge of how it all worked.

Edited Sunday at 11:34 AM by Expectedtofly

[Avalon_Fields]

We should gain a better understanding of the total numbers trying because of the new system. If you're say 25% to the front of the queue at 9am, and you're one of the last to get a ticket, then 4x people trying vs. number of tickets. Plenty of variables of course.

[Crazyfool01]

8 minutes ago, Avalon_Fields said:

We should gain a better understanding of the total numbers trying because of the new system. If you're say 25% to the front of the queue at 9am, and you're one of the last to get a ticket, then 4x people trying vs. number of tickets. Plenty of variables of course.

do we average it out at 2 devices/ connections  per person ? or is it more ? ...... if theres 100,000 tickets sunday  .....and everyone has 6 devices you could be 600,000 in the queue ..... if everyone has 2 devices you could be 200,000 so not sure we will learn much inn terms of people trying .... also the queue doesn't look like it will have a queue place number so would mess everything up 

[Nobody Interesting]

19 minutes ago, Crazyfool01 said:

do we average it out at 2 devices/ connections  per person ? or is it more ? ...... if theres 100,000 tickets sunday  .....and everyone has 6 devices you could be 600,000 in the queue ..... if everyone has 2 devices you could be 200,000 so not sure we will learn much inn terms of people trying .... also the queue doesn't look like it will have a queue place number so would mess everything up 

 

Only if there are only 100,000 people trying for those 100,00 tickets.

There will be more than 1 million in the queue plus multiple devices by some.

As for probabilities...................................

 

The probability of getting tickets before now was minimal and very hard.
It is now minimal and very hard, just more so.

[Crazyfool01]

2 minutes ago, Nobody Interesting said:

 

Only if there are only 100,000 people trying for those 100,00 tickets.

There will be more than 1 million in the queue plus multiple devices by some.

As for probabilities...................................

 

The probability of getting tickets before now was minimal and very hard.
It is now minimal and very hard, just more so.

Agree 

[Crazyfool01]

Oh some advice for those using plugins …. I’d avoid the glade one it won’t work but your room will smell nice at least 

[clarkete]

On 11/8/2024 at 9:37 AM, Fake Encore said:

I don't want to go to Glastonbury with people who use tunnel servers, vpn re-routing systems or pay £900 for slots in the tickets queue or stop in a kubutz 2 miles away.

 

I want the hippies at Strummerville, the great unwashed, the ones who will go to the JP Tent at 11.30am as they half heard a song on 6 a year ago, the one getting a swedish massage and not just for instragram but, because there back hurts lugging the thatchers up the hill.

 

Amen 

Some folks have used VPNs for different reasons for decades, whether for work or whatever.

 

I use them for a variety of reasons but still made it to Kneecap in Woodsies at 1130 on Saturday, along with many thousands of others and yes it was based on only knowing a song or two.  And feck me, after going for 39 years you'd better believe my back hurts if I'm carrying stuff up the hill 😉 

[Adster]

1 hour ago, Expectedtofly said:

 

Yes, I agree.  

 

I guess its just more cut and dried now.

For example.  Say, for simplicity and  arguments sake, only the first 10% in the queue get tickets.

In a team of the 36.  3 (or maybe 4) people will actually get tickets.  So that would only be 18 of the 36 strong group who will get tickets.

 

That is indeed an advantage over a group of 6 only have a 50% chance of getting tickets.  But not much of one.  Because the group of 36 also only have 50% chance (plus the slightly higher chance of having a 4th person in the top 10%).

 

[EDIT]  I've changed my mind there is no advantage of a team of 36 over a team of 6.  Other than the pyramid scheme advantage, ie you are at the top of the spreadsheet!!!

 

 

Whereas before it was much more nuanced, with all 36 continually trying until the tickets run out.  Also they had the advantage of persistence, motivation and technical knowledge of how it all worked.

Isn't there still a small advantage?

If you are in a team of 6 and two of you get a low place in the queue then the second lowest spot goes to waste.  However in a team of 36 (6 groups of 6) if two of you in one group get a low place in the queue the second lowest spot would be used to get tickets for one of the other groups in the team.

Its a small advantage, but it evens out some of the randomness around queue positioning.

You solve the pyramid problem by agreeing that every group gets tickets for the group below themselves next, and the bottom group gets them for the top group