This website shows that people started reporting issues with Google around 1:28 AM (Pacific Time), and it currently shows a spike of 7,419 reports.
EDIT: Spike went down at around 2:04 AM (Pacific Time). Thanks, Google Site Reliability Engineers, now go to sleep!
Just a reminder: DownDetector doesn’t actually check if a website is down. It collects data on how many people have reported issues or asked about a site’s status. So, while it doesn’t always reflect the real-time status of a website, it can give a rough idea of the scale of the problem—assuming the site really is down.
Getting “Error 502 (Server Error)!!1” from 142.250.217.78 (“A” DNS record).
Worth noting though that SREs at Google are rarely woken up. One of the main differences between SREs who support a service and dev owners who may also be on call is that the SREs will be in some sort of follow the sun configuration of 12 hour shifts. My team in Sydney partners with San Francisco for example, so worst case for me is a page at midnight just before I hand over, worst case for them is about 5am. So not usually anything happening in the middle of the night, at worst a late night or early morning, but never both.
This website shows that people started reporting issues with Google around 1:28 AM (Pacific Time), and it currently shows a spike of 7,419 reports.
EDIT: Spike went down at around 2:04 AM (Pacific Time). Thanks, Google Site Reliability Engineers, now go to sleep!
Just a reminder: DownDetector doesn’t actually check if a website is down. It collects data on how many people have reported issues or asked about a site’s status. So, while it doesn’t always reflect the real-time status of a website, it can give a rough idea of the scale of the problem—assuming the site really is down.
Getting “Error 502 (Server Error)!!1” from 142.250.217.78 (“A” DNS record).