Posting this 4 days later, what happened next: http://www.businessinsider.com/google-cloud-won-skeptic-after-shutting-site-down-2016-8 http://www.businessinsid

Posting this 4 days later, what happened next: http://www.businessinsider.com/google-cloud-won-skeptic-after-shutting-site-down-2016-8 http://www.businessinsider.com/google-cloud-won-skeptic-afte... Google then shocked him again, in a good way. Within four hours of tweeting, someone from Google had contacted him and had restored access to his project. Trotter says that, it turns out, he and his team bear some responsibility. They had inadvertently set up a server wrong, exposing a hole, and a hacker was using his company's to conduct a "denial of service attack," which is when hackers overload another website or online service with so much traffic, it shuts down.