Gmail, Google Maps and YouTube had outage issues

Post by hobofan » Tue, Sep 12, 2017, 4:23 PM UTC

omni wrote: post #32

eric_b wrote: post #25

Earlier quoted context omitted.

I see this argument a lot but I don't think it's necessarily a good one. If a third party CDN goes down, your site is down. A few extra ms in initial download isn't so bad compared to having your site be completely inaccessible for reasons outside your control.

Why doesn't having the resources cached provide a buffer against short-term outages of the CDN?

Post by aneutron » Tue, Sep 12, 2017, 4:23 PM UTC

trhway wrote: post #20

dom0 wrote: post #6

Does not seem to affect Europe. In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any YouTube page.

reboot helps. May be Google runs Windows. Then they just need to reboot more frequently, ie. proactively.

Post by dom0 » Tue, Sep 12, 2017, 4:25 PM UTC

wil421 wrote: post #31

eric_b wrote: post #25

Earlier quoted context omitted.

I see this argument a lot but I don't think it's necessarily a good one. If a third party CDN goes down, your site is down. A few extra ms in initial download isn't so bad compared to having your site be completely inaccessible for reasons outside your control.

Self hosting will probably cause more downtime than if you are using a decent CDN. CDN is just one of many points of failure, I would expect there's a fine balancing act where you could achieve benefits of both.

Post by aneutron » Tue, Sep 12, 2017, 4:26 PM UTC

asdfologist wrote: post #40

excalibur wrote: post #30

Updated to say AWS and GitHub also affected. North Korean cyber attack anyone?

Yes, Donald Trump is strategizing a retaliation with Jeff Bezos and other allies at GitHub as we speak.

Post by hungerstrike » Tue, Sep 12, 2017, 4:27 PM UTC

bcherny wrote: post #19

ocdtrekkie wrote: post #10

Earlier quoted context omitted.

Is there a good reason to use these things hosted by a third party source? Libraries are tiny, the fonts can be downloaded from Google Fonts and embedded locally, etc. Even the Google Analytics JS script I presume can be stored and run local. Shouldn't a goal be to mitigate the number of possible failures which can bring down your site by reducing the number of single points of failure?

2 reasons: 1. If you're still using HTTP 1.x, sharding assets across origins lets the browser load them in parallel (if set up correctly). You can generally load just 6 assets in parallel per origin, and sharding is a way to get around that limit. 2. A library like jQuery is so popular, and is so often served from googles CDN, that chances are a user already has it in their local cache from when they downloaded it on…