From what I was seeing all day yesterday you should keep trying to buy. New f2f seats yesterday were suddenly cartable more than 30 mins after appearing. Everything seems delayed right now.
I was right on the Hollywood N2 Section 117 row R seats 19 & 20 but couldn't even cart. Frustrating, but will keep trying and good luck to all
2008 MSG I & II 2010 Newark, MSG I 2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego 2014 Detroit, Moline, St. Paul & Milwaukee 2015 Ed Sullivan Theater/ Central Park 2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1 2017 RRHOF 2018 Seattle I & II, Missoula, Boston I & II 2022 Apollo, MSG, Camden, Nashville & St. Louis 2023 St.P. 1 & 2, Austin 1 & 2 2024 MSG 1 & 2, Baltimore, Philly 1 & 2, Fenway 1
^^ Had those carted but the dreaded double authentication screwed up everything!
Ouch!, at least we are starting to see a few seats. Keep trying and good luck. C U there!
2008 MSG I & II 2010 Newark, MSG I 2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego 2014 Detroit, Moline, St. Paul & Milwaukee 2015 Ed Sullivan Theater/ Central Park 2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1 2017 RRHOF 2018 Seattle I & II, Missoula, Boston I & II 2022 Apollo, MSG, Camden, Nashville & St. Louis 2023 St.P. 1 & 2, Austin 1 & 2 2024 MSG 1 & 2, Baltimore, Philly 1 & 2, Fenway 1
it definitely seems like those Hollywood 2 and Pittsburgh 2 are stuck.
As I typed that the Hollywood 2 disappeared.
They seem to remain visible (but not purchasable) for about 30 minutes, even though they are usually claimed within 1-3 seconds after appearing in the inventory. Bots, scripters, etc. are always faster than manual reload/refreshers.
I feel like even though they’re stuck for an unknown amount of time, as soon as they become purchasable if there is a bot running it will buy them. I don’t think an API bot is necessarily always running, but the ones that automate the purchase in a web browser are essentially doing everything someone manually refreshing is doing, just faster.
The way they work is loading up the event page in a browser tab either in the background or literally on someone’s desktop. As soon as the HTML elements of the page load, sometimes before it’s even done rendering on the front end, it will select a pair of tickets and complete the purchase using stored variables. If no tickets are found it ends the process and tries again however many seconds later. Over and over. When the IP gets temp blocked it just cycles to a new one. It’s why I’m not even trying because it’s too frustrating. The best you can hope for is to get lucky when one isn’t running or after they stop buying a certain show or level of ticket which for GA I don’t think they do until very close to the show. I suppose if you’re persistent you’ll eventually be the first one to be successful but man it wears you down.
not sure why my other thread was removed, but i am looking for 1 (or 2) tickets to both Hollywood, FL shows - i have cash, tickets for Atlanta N1, tickets for Atlanta N2, and hotel reservations in Hollywood, FL that i am willing to trade
Atlanta N1 GA x2 SEC 3 F x2
Atlanta N2 108 JJ x2 110 DD x2
Dolce by Wyndham Hollywood - 4/24 to 4/27 Staybridge Suites Fort Lauderdale - 4/24 to 4/27
buf dtw buf sce yyz tol grr yhm yyz pit yyz yyz pit bna cae aus lax lax san phl phl cle buf mke mke atl pit buf clt san lax lax gsp cae bna sea sea
I feel like even though they’re stuck for an unknown amount of time, as soon as they become purchasable if there is a bot running it will buy them. I don’t think an API bot is necessarily always running, but the ones that automate the purchase in a web browser are essentially doing everything someone manually refreshing is doing, just faster.
The way they work is loading up the event page in a browser tab either in the background or literally on someone’s desktop. As soon as the HTML elements of the page load, sometimes before it’s even done rendering on the front end, it will select a pair of tickets and complete the purchase using stored variables. If no tickets are found it ends the process and tries again however many seconds later. Over and over. When the IP gets temp blocked it just cycles to a new one. It’s why I’m not even trying because it’s too frustrating. The best you can hope for is to get lucky when one isn’t running or after they stop buying a certain show or level of ticket which for GA I don’t think they do until very close to the show. I suppose if you’re persistent you’ll eventually be the first one to be successful but man it wears you down.
Thats pretty accurate. But I can tell you from personal experience that even having the browser scripts to automate the process doesn't guarantee anything. It's still a race to see who refreshed and saw the ticket first and who has faster internet.
I feel like even though they’re stuck for an unknown amount of time, as soon as they become purchasable if there is a bot running it will buy them. I don’t think an API bot is necessarily always running, but the ones that automate the purchase in a web browser are essentially doing everything someone manually refreshing is doing, just faster.
The way they work is loading up the event page in a browser tab either in the background or literally on someone’s desktop. As soon as the HTML elements of the page load, sometimes before it’s even done rendering on the front end, it will select a pair of tickets and complete the purchase using stored variables. If no tickets are found it ends the process and tries again however many seconds later. Over and over. When the IP gets temp blocked it just cycles to a new one. It’s why I’m not even trying because it’s too frustrating. The best you can hope for is to get lucky when one isn’t running or after they stop buying a certain show or level of ticket which for GA I don’t think they do until very close to the show. I suppose if you’re persistent you’ll eventually be the first one to be successful but man it wears you down.
Thats pretty accurate. But I can tell you from personal experience that even having the browser scripts to automate the process doesn't guarantee anything. It's still a race to see who refreshed and saw the ticket first and who has faster internet.
100%, I think how fast the refresh period is depends on how many IP addresses they have to burn because it'll get blocked pretty quickly if they have it set to every second for example. But if there's multiple going, which I have to assume there are for some of the shows, from our perspective it very well could average out to once/sec.
There's definitely multiple parties buying tickets, you can tell by the seller note in TickPick because they'll put the same thing for all of their listings. Some list seat numbers and some don't etc.
Congrats on getting the other thread closed y'all!
ISO Raleigh N2 GA -- FT Raleigh N1 FLR (Pair for Pair)
Post edited by PrezIntense on
1996 Charlotte 1998 Raleigh 2000 Virginia Beach 2003 Raleigh 2016 RaleighThanks HB2 2016 Columbia 2020 BaltimoreThanks COVID 2022 BaltimoreThe only original COVID venue not rescheduled (due to construction) :( 2022 Denver 2024 Baltimore 2025 Raleigh 1 and 2
Congrats on getting the other thread closed y'all!
ISO Raleigh N2 GA -- FT Raleigh N1 FLR (Pair for Pair)
"F2F is Open" had a good run. Hopefully everyone will now share in this thread.
1993
– San Diego 1995 – San Diego 1998 – San Diego 2000 – San Diego 2003 – San Diego 2006 – San Diego 2009 – San Diego 2013 – San Diego 2022 – San Diego, LA1, LA2, Glendale, Oak1, OKC
2023 – Fort Worth1, Forth Worth2, Austin1, Austin2 2024
– Sacramento, Vegas1, Vegas2, LA1, LA2
Comments
A similar pair popped up for Raleigh N2, and there's also a pair of uppers for Pittsburgh N1, but I guess I missed out on those as well
2010 Newark, MSG I
2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego
2014 Detroit, Moline, St. Paul & Milwaukee
2015 Ed Sullivan Theater/ Central Park
2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1
2017 RRHOF
2018 Seattle I & II, Missoula, Boston I & II
2022 Apollo, MSG, Camden, Nashville & St. Louis
2023 St.P. 1 & 2, Austin 1 & 2
2024 MSG 1 & 2, Baltimore, Philly 1 & 2, Fenway 1
2024: Wrigley II, Fenway II
2010 Newark, MSG I
2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego
2014 Detroit, Moline, St. Paul & Milwaukee
2015 Ed Sullivan Theater/ Central Park
2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1
2017 RRHOF
2018 Seattle I & II, Missoula, Boston I & II
2022 Apollo, MSG, Camden, Nashville & St. Louis
2023 St.P. 1 & 2, Austin 1 & 2
2024 MSG 1 & 2, Baltimore, Philly 1 & 2, Fenway 1
As I typed that the Hollywood 2 disappeared.
2018: Fenway 1
2021: Sea.Hear.Now
2022: San Diego, MSG, Camden
2023: Ft. Worth 1, Ft. Worth 2, Austin 1, Austin 2
2024: Las Vegas 1, Las Vegas 2, Wrigley 1, Wrigley 2, MSG 1, MSG 2, Philly 2, Fenway 1, Fenway 2
Atlanta N1
GA x2
SEC 3 F x2
Atlanta N2
108 JJ x2
110 DD x2
Dolce by Wyndham Hollywood - 4/24 to 4/27
Staybridge Suites Fort Lauderdale - 4/24 to 4/27
2024: Wrigley II, Fenway II
Thats pretty accurate. But I can tell you from personal experience that even having the browser scripts to automate the process doesn't guarantee anything. It's still a race to see who refreshed and saw the ticket first and who has faster internet.
There's definitely multiple parties buying tickets, you can tell by the seller note in TickPick because they'll put the same thing for all of their listings. Some list seat numbers and some don't etc.
ISO Raleigh N2 GA -- FT Raleigh N1 FLR (Pair for Pair)
1998 Raleigh
2000 Virginia Beach
2003 Raleigh
2016 Raleigh Thanks HB2
2016 Columbia
2020 Baltimore Thanks COVID
2022 Baltimore The only original COVID venue not rescheduled (due to construction) :(
2022 Denver
2024 Baltimore
2025 Raleigh 1 and 2
1993 – San Diego
1995 – San Diego
1998 – San Diego
2000 – San Diego
2003 – San Diego
2006 – San Diego
2009 – San Diego
2013 – San Diego
2022 – San Diego, LA1, LA2, Glendale, Oak1, OKC
2023 – Fort Worth1, Forth Worth2, Austin1, Austin2
2024 – Sacramento, Vegas1, Vegas2, LA1, LA2
2025 – ATL1, ATL2, Nashville1, Nashville2
Lower bowl first few side sections either side
Atlanta n2
Nashville either show
Thanks