There is great debate as to how Ticketmaster distributes tickets during a sale. Some people say they release the nosebleed tickets to get rid of them first, then they start offering the better seats later on.
Some also think that it’s completely random and pretty much a crapshoot the first few minutes.
And then there’s the theory that the faster you get in, the better seats you will get.
I am going to focus on the last one. Now don’t get me wrong, connection speed isn’t everything. There are lots of varying factors in obtaining good seats and the more experience (and luck) you have the better off you will be. And after you’ve been in the business a while, you’ll learn when Ticketmaster drops tickets days after the general onsale so connection won’t matter at this point.
Having a good connection speed certainly does help though, so I am going to show you a trick to determine your connection speed to Ticketmaster.
Go to:
> Run
> Type “cmd” and hit enter
> You should now be in the MS DOS screen
> Type “tracert Ticketmaster.com” (without quotations)
This command will show the time and hops it takes to connect to Ticketmaster.
The last number in the right hand column will be your connection speed.
The lower the ms number the faster you will connect to Ticketmaster. If your speed is 120ms your extremely fast connection is not as extremely fast as you think it is. My connection speed was .69ms at home and .23ms at the library.
Just because you have a 3.0+GHz system does not mean that your Internet connection is fast. The system may be fast but the connection speed to Ticketmaster really depends on how many switchovers your connection has to go though to get to Ticketmaster! Your connection speed to another site, maybe Yahoo or MSN, etc. may be much faster because you may not have to go through as many switchovers.
Traceroute is a utility that helps diagnose network congestion between your computer (ISP) and the destination server (www.domainname.com). Traceroute works by sending packets of information from your location to the destination and timing how long it takes to receive a response. In addition to tracking the time it takes to reach the final destination, you are provided with the times to each 'Hop' between your terminal and the destination. Each Hop is a separate 'router' that your information must pass through. By providing the times for each hop, we can often find the source of problems accessing a server.
You can do this at your house, work, friends, library, school etc. to see what one connects the fastest. Try this out and see if it makes a difference when you pull tickets for the next event.
No comments:
Post a Comment