Sony PlayStation 2017 E3 Ticket Site [ www.gofobo.com ] Down ALL DAY

 

Like many other enthusiasts, I was excited to get the opportunity to purchase tickets to my Local Theatre to experience Sony PlayStation’s E3 LIVE simulcast on the big screen!

The link to get tickets is at this site:

https://www.playstation.com/en-us/campaigns/2017/e3experience/

which points to a 3rd party ticket provider, gofobo.com  with this URL:

http://www.gofobo.com/PlaystationE32017

At approximately 10 AM PT http://www.gofobo.com/  CRASHED HARD and has been down ever since. 

Main response code all day has been http 503 – Service Unavailable.  Now it is showing as a 404 not found. ( screen shot above ) One attempt earlier in the afternoon brought up the main gofobo.com page once today; but then said that the “PlayStationE32017” code was invalid.

Earlier today, GoFobo had two public IP’s registered; I tried them both. No go.

All other requests have hung, or been met with 503 (until now which has turned to 404) –  I think this is really gofobo.com simply being overwhelmed  by Sony Playstation fans – FAILURE TO SCALE. This could have been another intentional, malicious DDoS against Sony, or maybe perhaps a human error killed it.   I was able to get tickets within 5 mins last year and I don’t remember gofobo.com as part of that.   That 404 happening on their main site is because I believed they moved their site to new digs:

At present,  4:11 PT, it appears they are shifting their DNS records around . . .. ( there were only two IP entries before and they were different IPs ) from a previous dig at 1 PM.

Here is a DIG now:

;; ANSWER SECTION:

http://www.gofobo.com. 148 IN CNAME screenings-346088557.us-west-2.elb.amazonaws.com.

screenings-346088557.us-west-2.elb.amazonaws.com. 59 IN A 54.191.95.244

screenings-346088557.us-west-2.elb.amazonaws.com. 59 IN A 52.35.41.68

screenings-346088557.us-west-2.elb.amazonaws.com. 59 IN A 52.32.184.40

screenings-346088557.us-west-2.elb.amazonaws.com. 59 IN A 52.25.144.120

So… looks like they are moving this to AWS! Thinking this move happened when the 503 error code became a 404.

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s