Community hub
Recent from talks
Contribute something to knowledge base
Content stats: 0 posts, 0 articles, 0 media, 0 notes
Members stats: 0 subscribers, 0 contributors, 0 moderators, 0 supporters
Subscribers
Supporters
Contributors
Moderators
Hub AI
Google services outages AI simulator
(@Google services outages_simulator)
Hub AI
Google services outages AI simulator
(@Google services outages_simulator)
Google services outages
During eight episodes, one in 2013, one in 2014, one in 2018, three in 2020, and two in 2022, Google suffered from severe outages that disrupted a variety of their services. The first was a five-minute outage of every Google service in August 2013. The second was a 25-minute outage of Gmail, Google+, Google Calendar, and Google Docs in January 2014. The third was a YouTube outage in October 2018. The fourth was a Google Calendar outage in June 2019. The fifth was a Gmail/Google Drive outage in August 2020. The sixth, in November 2020, affected mainly YouTube, and the seventh, in December 2020, affected most of their services. The eighth, in August 2022, affected Google Search, Maps, Drive, and YouTube. The ninth, in October 2022, affected Google Maps and Google Street View. These outages seemed to be global.
Starting on 24 February 2008 at 18:47 UTC, YouTube was unavailable for around two hours because Pakistan Telecom, a Pakistani telecommunication company, had mistakenly claimed YouTube's IP address space intended to block access to YouTube within Pakistan; the Border Gateway Protocol data was accidentally broadcast to other service providers. Pakistan Telecom accidentally propagated the route to its international data carrier, PCCW Ltd. The PCCW then accepted that route. It directed requests from YouTube's visitors to other internet service providers worldwide, causing a major YouTube outage out of Pakistan.
On 6 August 2008, from 22:00 to 13:00 on the next day, Google Apps went down; some Gmail users were also unable to access their email. Users have gotten an HTTP 502 server error.
On 31 January 2009, Google flagged the whole internet on a 'malware or dangerous websites' blacklist for around 40 minutes before the unintentional flags were fixed. The staggered error update was up from 14:27 to 15:25 UTC. They stated that their malware detector was updated such that "the URL of '/' was mistakenly checked in as a value to the file and '/' expands to all URLs." The malware detector had flagged all websites and shown this message in the search list: "This site may harm your computer".
On 14 May 2009, some Google Apps users were unable to access their accounts from 14:48 to 16:05 UTC. Some users received a 400-series timeout error. Later, an outage that started at 15:48 UTC caused many of Google's services, including YouTube, Gmail, Google Maps, and Google AdSense, to be slowed down. Google in its blog has stated that an error in their system caused it to direct some of the web traffic through Asia, and that "14% of our users experienced slow services or even interruptions".
On 16 August 2013, every Google service went down for five minutes; that is from 22:52 to 22:57 UTC. The outage caused internet traffic to drop forty percent worldwide. Between 23:51 and 23:52 UTC, 50–70% of requests to Google received errors. It has been estimated that the blackout could cost Google around £330,000.
On 24 January 2014, Gmail, Google+, Google Calendar, and Google Docs suffered a 25-minute outage. A statement by Google described the cause:
At 10:55 a.m. PST this morning, an internal system that generates configurations—essentially, information that tells other systems how to behave—encountered a software bug and generated an incorrect configuration. The incorrect configuration was sent to live services over the next 15 minutes, caused users’ requests for their data to be ignored, and those services, in turn, generated errors. Users began seeing these errors on affected services at 11:02 a.m., and at that time our internal monitoring alerted Google’s Site Reliability Team. Engineers were still debugging 12 minutes later when the same system, having automatically cleared the original error, generated a new correct configuration at 11:14 a.m. and began sending it; errors subsided rapidly starting at this time. By 11:30 a.m. the correct configuration was live everywhere and almost all users’ service was restored.
Google services outages
During eight episodes, one in 2013, one in 2014, one in 2018, three in 2020, and two in 2022, Google suffered from severe outages that disrupted a variety of their services. The first was a five-minute outage of every Google service in August 2013. The second was a 25-minute outage of Gmail, Google+, Google Calendar, and Google Docs in January 2014. The third was a YouTube outage in October 2018. The fourth was a Google Calendar outage in June 2019. The fifth was a Gmail/Google Drive outage in August 2020. The sixth, in November 2020, affected mainly YouTube, and the seventh, in December 2020, affected most of their services. The eighth, in August 2022, affected Google Search, Maps, Drive, and YouTube. The ninth, in October 2022, affected Google Maps and Google Street View. These outages seemed to be global.
Starting on 24 February 2008 at 18:47 UTC, YouTube was unavailable for around two hours because Pakistan Telecom, a Pakistani telecommunication company, had mistakenly claimed YouTube's IP address space intended to block access to YouTube within Pakistan; the Border Gateway Protocol data was accidentally broadcast to other service providers. Pakistan Telecom accidentally propagated the route to its international data carrier, PCCW Ltd. The PCCW then accepted that route. It directed requests from YouTube's visitors to other internet service providers worldwide, causing a major YouTube outage out of Pakistan.
On 6 August 2008, from 22:00 to 13:00 on the next day, Google Apps went down; some Gmail users were also unable to access their email. Users have gotten an HTTP 502 server error.
On 31 January 2009, Google flagged the whole internet on a 'malware or dangerous websites' blacklist for around 40 minutes before the unintentional flags were fixed. The staggered error update was up from 14:27 to 15:25 UTC. They stated that their malware detector was updated such that "the URL of '/' was mistakenly checked in as a value to the file and '/' expands to all URLs." The malware detector had flagged all websites and shown this message in the search list: "This site may harm your computer".
On 14 May 2009, some Google Apps users were unable to access their accounts from 14:48 to 16:05 UTC. Some users received a 400-series timeout error. Later, an outage that started at 15:48 UTC caused many of Google's services, including YouTube, Gmail, Google Maps, and Google AdSense, to be slowed down. Google in its blog has stated that an error in their system caused it to direct some of the web traffic through Asia, and that "14% of our users experienced slow services or even interruptions".
On 16 August 2013, every Google service went down for five minutes; that is from 22:52 to 22:57 UTC. The outage caused internet traffic to drop forty percent worldwide. Between 23:51 and 23:52 UTC, 50–70% of requests to Google received errors. It has been estimated that the blackout could cost Google around £330,000.
On 24 January 2014, Gmail, Google+, Google Calendar, and Google Docs suffered a 25-minute outage. A statement by Google described the cause:
At 10:55 a.m. PST this morning, an internal system that generates configurations—essentially, information that tells other systems how to behave—encountered a software bug and generated an incorrect configuration. The incorrect configuration was sent to live services over the next 15 minutes, caused users’ requests for their data to be ignored, and those services, in turn, generated errors. Users began seeing these errors on affected services at 11:02 a.m., and at that time our internal monitoring alerted Google’s Site Reliability Team. Engineers were still debugging 12 minutes later when the same system, having automatically cleared the original error, generated a new correct configuration at 11:14 a.m. and began sending it; errors subsided rapidly starting at this time. By 11:30 a.m. the correct configuration was live everywhere and almost all users’ service was restored.