Random Server Errors = Sweat Bullets for an Hour

I woke up this morning with about four hours of sleep. I'Ve got a funny alert on my phone or static city and server was returning errors strange errors. Sometimes it was working. Sometimes it wasn't. I looked at the logs a little bit on my phone and decided to get up and investigate it. It turned out back blaze B2, which is an AWS, is three alternative that we use to store static files was down. Was it a bad? Push to production occurred problem now, due to an abuse report. Go daddy had suspended one of the domains they used by the service so instantly millions of people who depended on back, please be to the other apps that use the service were off-line or broken or in someway impacted.