Gmail is working fine on east coast. I did hear youtube having 503 errors.
East coast, been on YouTube all day. Didn't notice anything. /shrug
Gmail, Google Maps and YouTube had outage issues
51–60 of 105 posts
Re: Gmail, Google Maps and YouTube had outage issues
#52GSuite has status reports for things like this, and it tends to be a good way to confirm a Google service outage[0]. Direct link to the issue[1].
[0] https://www.google.com/appsstatus#hl=en&v=status
[1] https://www.google.com/appsstatus#hl=en&v=issue&sid=1&iid=d4...
Re: Gmail, Google Maps and YouTube had outage issues
#53Earlier quoted context omitted.
reboot helps. May be Google runs Windows. Then they just need to reboot more frequently, ie. proactively.
Funnily enough, in one previous company I worked, which used Linux exclusively, the software was very buggy, and the servers were rebooted daily. We jokingly called that the "Windows solution". When we proposed adding a daily reboot to cron, the tech lead (which encouraged practices which lead to this low quality software) retorted that "this in not Windows, it doesn't need constant reboots", totally missing the poin…
I used to have a service that was like that, it was third party and only handled a specific function so I had a cron job that would reboot it at 4am every day.
Sometimes the hammer approach is the only solution.
Re: Gmail, Google Maps and YouTube had outage issues
#54Earlier quoted context omitted.
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…
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 some other site. Which of these versions do you have cached? 3.2.1, 3.2.0, 3.1.1, 3.1.0, 3.0.0, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2.0, 2.1.4, 2.1.3, 2.1.1, 2.1.0, 2.0.3, 2.0.2, 2.0.1, 2.0.0, 1.12.4, 1.12.3, 1.12.2, 1.12.1, 1.12.0, 1.11.3, 1.11.2, 1.11…
How many do you need to make this worthwhile?
The ratio of cost of storing a library versus the cost of GETing a library is very low, so the chances of already having a library cached can be very low for the EV to be worthwhile.
Weighing that against the chance of downtime is a bit more complicated, admittedly.
Re: Gmail, Google Maps and YouTube had outage issues
#55Earlier quoted context omitted.
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…
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 some other site. Which of these versions do you have cached? 3.2.1, 3.2.0, 3.1.1, 3.1.0, 3.0.0, 2.2.4, 2.2.3, 2.2.2, 2.2.1, 2.2.0, 2.1.4, 2.1.3, 2.1.1, 2.1.0, 2.0.3, 2.0.2, 2.0.1, 2.0.0, 1.12.4, 1.12.3, 1.12.2, 1.12.1, 1.12.0, 1.11.3, 1.11.2, 1.11…
Just two versions of jQuery, 1.12 and 1.11, represent approximately half of all jQuery versions in use. The top four most common versions (1.12, 1.11, 1.7, 1.8) represent close to 3/4 of all versions of jQuery in use. Version 3.x and 2.x are hardly being used by comparison to those.
That narrows your suggested problem down dramatically.
Re: Gmail, Google Maps and YouTube had outage issues
#56I think it's a little premature to be calling this a "meltdown". It's like calling one block of houses with power fluctuations a "blackout".
[deleted]
Re: Gmail, Google Maps and YouTube had outage issues
#57Earlier 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…
> You can generally load just 6 assets in parallel per origin
This seems to only apply to Chrome, whereas Firefox will happily download everything as fast as possible.
I know this because I fixed a bug recently where chrome was taking so long to download images that other resources on the page were timing out. No problem in Firefox.
Re: Gmail, Google Maps and YouTube had outage issues
#58Updated to say AWS and GitHub also affected. North Korean cyber attack anyone?
They were probably aiming at some IT system at Hyundai and they hired the same people to do routing software as they do to do rocket guidance.
Re: Gmail, Google Maps and YouTube had outage issues
#59Earlier quoted context omitted.
reboot helps. May be Google runs Windows. Then they just need to reboot more frequently, ie. proactively.
[Removed]
There is a common practice for Node.js developers to use one of those tools that automatically reboot the site either whenever the single-threaded-event-loop-server crashes, or periodically...
Re: Gmail, Google Maps and YouTube had outage issues
#60Earlier quoted context omitted.
Funnily enough, in one previous company I worked, which used Linux exclusively, the software was very buggy, and the servers were rebooted daily. We jokingly called that the "Windows solution". When we proposed adding a daily reboot to cron, the tech lead (which encouraged practices which lead to this low quality software) retorted that "this in not Windows, it doesn't need constant reboots", totally missing the poin…
I used to have a service that was like that, it was third party and only handled a specific function so I had a cron job that would reboot it at 4am every day. Sometimes the hammer approach is the only solution.
Was the software loading kernel modules? I'm curious why a more simple kill process routine wouldn't work.