3 ms·
Given how many services it affected and the mention of 404 errors, I would suspect a GFE bug or bad configuration that started rolling out worldwide (hence the
by puzzle 8y ago
Given how many services it affected and the mention of 404 errors, I would suspect a GFE bug or bad configuration that started rolling out worldwide (hence the geographically diverse, but not 100% spread of the issue). A decade ago, Tuesdays were a special day for GFEs, but that hasn't been the case for years now. Perhaps it's just the Tuesday curse that persists. :-)
My money is either on that or the static content service.
- bamboozled 8y agoGFE?
- chx 8y agohttps://medium.com/@jerub/the-production-environment-at-google-part-2-610884268aaa https://medium.com/@jerub/the-production-environment-at-goog... > The browser connects to the HTTP server on this IP. This server (named the Google Frontend, or GFE) is a reverse proxy that terminates the TCP connection (2). The GFE looks up which service is required (web search, maps
- skj 8y ago"Google Front End", the process directly between the open internet and internal Google services.
- kerng 8y agoHistorically Google terminated all security at that front door layer- hope that changed by now. But interestingly a cert issue down the pipe could easily be the root cause.