Clearly they're using the same infrastructure for everything which IMHO is a huge mistake

Let's not forget that most Google services have exceptional reliability and things like today's outage are incredibly rare. I'd bet that failures due to interoperability between disparate services would cause a lot more downtime than Google suffers right now if teams ran different infrastructures.

Google outages are not that rare, see https://en.wikipedia.org/wiki/2020_Google_services_outages

If they had multiple instances of infrastructure, then yes the outage wouldn't be prevented but at least it would be minimized as only a few services would be down instead of the whole thing.

It's easy to prove it, when Google was down, except for those who depend directly on it, how many other services from the internet went down? None. If Google was truly distributed internally like the internet is, then they wouldn't have this problem. This is clearly a symptom of a crap thought out infrastructure. I know folks who work there, and if you think Google Services architecture is great then you better think twice. There are many smaller businesses with much better availability from that of Google.

Be aware that Search wasn't down, so it clearly doesn't share something in common between all the other services.

    function gc() { grep -rnI "$@" * ;}
    function gcA() { grep -rnI -A 5 "$@" * ;}
    function gcB() { grep -rnI -B 5 "$@" * ;}
    function gcC() { grep -rnI -C 5 "$@" * ;}
    function gcf() { grep -rnIl "$@" * ;}

edit: Thank you both!

-n enables line numbers

-I (eye) ignores matches on binary files

-l (ell) lists the filenames of matching files only (overrides -n)

-A, -B, and -C specify how many lines of context after, before, or around the match to display.

"$@" adds any additional command line arguments passed to the functions.

* selects all the files and directories in the current directory.

So, without other arguments, the first four functions list matches with line numbers for all files (ignoring binary files) in the current directory and below, with 0 lines context (match only), 5 lines context after, 5 lines context before, and 5 lines context around the match respectively. The final function lists the filenames only and provides no context or line numbers.

Also, while they haven't updated this blog post for a while, their status page has been very up-to-date and informative: https://status.github.com/messages

Is that satire? It said 2-hour ETA 5 hours ago and the last update was over two hours ago.

>12:56 British Summer Time

>The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.

I wonder what the total cost of this ordeal must be. Surely in the tens of millions.

"We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused."

Which is a bit scary. Half my requests appear to hit some storage which is still many hours behind. They should be seeing that...