remember folks, redundancy is the savior of all f***ups. :)
On Wed, Nov 25, 2015 at 2:21 PM, JoeSox <joe...@gmail.com> wrote: > I just waited 160 minutes for a tech call and the Bluehost tech told me he > was able to confirm that it wasn't malicious activity that took down the > datacenter but rather it was caused by a "datacenter issue". > So my first thought is someone didn't design the topology correctly or > something. > Some of our emails are coming thru but Google DNS still lost all of our DNS > zones which are hosted by Bluehost. > At least the #bluehostdown is fun to read :/ > -- > Later, Joe > > On Wed, Nov 25, 2015 at 10:04 AM, Stephane Bortzmeyer <bortzme...@nic.fr> > wrote: > > > On Wed, Nov 25, 2015 at 08:41:55AM -0800, > > JoeSox <joe...@gmail.com> wrote > > a message of 9 lines which said: > > > > > Anyone have the scope on the outage for Bluehost? > > > https://twitter.com/search?q=%23bluehostdown&src=tyah > > > > The two name servers ns1.bluehost.com and ns2.bluehost.com are awfully > > slow to respond: > > > > % check-soa -i picturemotion.com > > ns1.bluehost.com. > > 74.220.195.31: OK: 2012092007 (1382 ms) > > ns2.bluehost.com. > > 69.89.16.4: OK: 2012092007 (1388 ms) > > > > As a result, most clients timeout. > > > > May be a DoS against the name servers? > > > > bluehost.com itself is DNS-hosted on a completely different > > architecture. So it works fine. But the nginx Web site replies 502 > > Gateway timeout, probably overloaded by all the clients trying to get > > informed. > > > > The Twitter accounts of Bluehost do not distribute any useful > > information. > > >