I guess the best thing to do is keep trying? Not every second of course, but every couple minutes.
Anyone get through yet? Hopefully it won't be down long......

I started hitting the refresh on my link at 11:59. I do web development from home so I have a really good internet connection, it's just the luck of the draw. Good luck everyone!Thank you, your request to be added to the WANT List was successful! Being added to this list does not guarantee you a chance to buy tickets.
If tickets do become available, you will receive an email with a link to purchase tickets. You will have 72 hours to buy tickets using your unique link - nobody else can use it.
Please do not contact customer support asking about your status.
Dittosuicyco wrote:It is working, after getting the "save" button a few times and having the connection reset after hitting it, I finally got a confirmation page. It just has to wade through a great many connections.
I then received an email:"Thank you, your request to be added to the WANT List was successful! Being added to this list does not guarantee you a chance to buy tickets.
If tickets do become available, you will receive an email with a link to purchase tickets. You will have 72 hours to buy tickets using your unique link - nobody else can use it.
Please do not contact customer support asking about your status."
Now, I wonder if there's a way to view the WANT list I'm on? Or, at least find out how far down the line I am?"Thank you, your request to be added to the WANT List was successful! Being added to this list does not guarantee you a chance to buy tickets.
If tickets do become available, you will receive an email with a link to purchase tickets. You will be offered tickets at whichever face value is available, plus applicable delivery and service fees. You will have 72 hours to buy tickets using your unique link - nobody else can use it and it cannot be shared."
Oh boy.We're sorry, but the STEP queue is now closed. You should have received an email from Burning Man with information about the limitations of the queue including if and/or when it will be reopened.
Agree 100%, they need to go and BMORG needs to partner with a reputable ticketing vendor. I understand server overload, but contigency plans should be in place, like redirecting to a page with verbiage explaining the situation. Again, this is standard best practices in the industry. Ah well.RevDusty wrote:Horrible.
Got the "Save" button twice, and had the server crash on me twice. No confirm email. No nothing.
I can understand that not everyone can get into line.
I can't forgive the continuing terrible way tickets are handled, year after year.
In-Ticketing has repeatedly proven they don't know how to architect a scalable ticketing solution.
It's a travesty that we are still stuck with them, even though I am sure they are very nice burner people. They are not up to the job.
The Amazon cloud service is state of the art, it can handle very high volume, depending on what level account you have. As Trilo mentioned, it's pretty common to have server overload, it's how you handle that that matters.Robishop wrote:The Ticketing for STEP seemed to be hosted by Amazon Web Services, yes that Amazon... Did you notice the URL theat was in the addrwess of the links sent?
No matter, even Amazon is slow at times I guess.
Amazon Web Services
http://www.amazonaws.com/
Amazon Web Services (AWS) delivers a set of services that together form a reliable, scalable, and inexpensive computing platform “in the cloud”.
I'm very sorry that your patience (not refreshing when you got the white screen) is what cost you a place in the lineup. Patience should be rewarded, but in this case, it may have cost you a trip HomeSassy Britches wrote:After many "refreshes," got the screen to "click here." went to a blank screen, with URL of "burningman.tickets-secure.com/lottery/waiting list/save. Stayed blank for more than 30 minutes. Hit refresh only to be told it was closed.
Amazon can handle it, but InTicketing has to allocate the proper amount of resources to handle the load. Amazon is not going to do that for you automatically.Robishop wrote:The Ticketing for STEP seemed to be hosted by Amazon Web Services, yes that Amazon... Did you notice the URL theat was in the addrwess of the links sent?
No matter, even Amazon is slow at times I guess.
Amazon Web Services
http://www.amazonaws.com/
Amazon Web Services (AWS) delivers a set of services that together form a reliable, scalable, and inexpensive computing platform “in the cloud”.
The way it appeared to me was it was bouncing around several servers. The initial emailed link was to BM's servers. Which redirected to Amazon. The "SAVE" button page looked to be hosted on Amazon. However, hitting save seemed to redirect traffic back to burningman.com. I noticed that eplaya was very unresponsive during all of this. I got to the amazon page several times but it kept timing out when trying to redirect back to BM's servers. Eventually I got the confirmation message, but I think the big issue was the connection to BM's servers, not Amazon. Eplaya is working just fine again, so I would guess they shared the same connection. I doubt BM has as huge a pipe as Amazon.Robishop wrote:The Ticketing for STEP seemed to be hosted by Amazon Web Services, yes that Amazon... Did you notice the URL theat was in the addrwess of the links sent?
No matter, even Amazon is slow at times I guess.
Amazon Web Services
http://www.amazonaws.com/
Amazon Web Services (AWS) delivers a set of services that together form a reliable, scalable, and inexpensive computing platform “in the cloud”.