7 ms·

Surprised nothing shows up on https://www.google.com/appsstatus#hl=en&v=status https://www.google.com/appsstatus#hl=en&v=status for it. What's the point of a st

Surprised nothing shows up on https://www.google.com/appsstatus#hl=en&v=status https://www.google.com/appsstatus#hl=en&v=status for it. What's the point of a status site that doesn't reflect the status?

deleted 7y ago
[deleted]
butler14 7y ago
"We're investigating reports of an issue with Google Calendar. We will provide more information shortly. The affected users are unable to access Google Calendar."
twostorytower 7y ago
It's amazing how many of these status pages don't actually work in many situations.
- db48x 7y ago
  I guess technically the "server" is responding, so...
- bluetidepro 7y ago
  Edited my comment to just say the same thing. Haha What's the point of them then?
  - michaelmior 7y ago
    It's certainly helpful to know that Google is aware of the problem and fixing it.
- hknd 7y ago
  These pages at Google/Amazon/Netflix are updated by the incident response team, so it's a manual task.
- SilasX 7y ago
  Wasn't there that time AWS had some outage, but the red-circle picture (for failure) was itself hosted on the unavailable AWS service, so their status page didn't show it as being unavailable? Or am I mis-remembering something/repeating an urban legend?
  - Dragonai 7y ago
    Nah, you're remembering correctly, this happened. The failure icon was hosted on S3, but S3 was down. It was a great moment. Here's their tweet about it: https://twitter.com/awscloud/status/836656664635846656 https://twitter.com/awscloud/status/836656664635846656
    - SilasX 7y ago
      Thank you for confirming, and the citation!
  - aglionby 7y ago
    Yep, the icons were hosted on S3, which was unavailable https://www.theregister.co.uk/2017/03/01/aws_s3_outage/ https://www.theregister.co.uk/2017/03/01/aws_s3_outage/
  - jgroszko 7y ago
    Yes, that was the S3 outage last year... https://news.ycombinator.com/item?id=13756111 https://news.ycombinator.com/item?id=13756111
RutZap 7y ago
On that page's footer: > ©2019 Google - Last updated: June 18, 2019 at 3:12:13 PM UTC+1 Looks like it was last updated before the outage.
falcolas 7y ago
Status pages are not driven by automation, they are driven by PMs. Amazon, Google... all of the big players work them this way. And I'm not surprised, since actually reporting it as down has a lot of political blowback (not to mention contract blowback) within the company.
- Iggy173 7y ago
  Also, accurately reporting about an arbitrary source of downtime means you're smart enough to avoid the same sources of downtime. Not that this can't have been an obvious reason (deleting all the servers in a datacenter or similarly trivial but severe) but it's likely impossible to ensure status page accuracy.
  - chipperyman573 7y ago
    You could just ping the servers once a minute and tell if they're up or not. No need to know why they've gone down.
    - lukeschlather 7y ago
      Most outages aren't so obvious as this one, and any ping will fail intermittently (often because the ping agent has a failure.) Google definitely has loads of pings hitting Google Calendar in various ways. Exposing this monitoring to the public is not practical or really useful. (And would aid would-be attackers.)
    - yegle 7y ago
      That only indicate the frontend of the service is up and potentially running. Being about to respond to ping and being able to serve HTTP request are two different things, and being able to serve HTTP request vs a fully functional website are two different things. Think about wrong SSL certification, wrong domain mapping between frontend/backend, broken JS/CSS etc.
      - CloudNetworking 7y ago
kyrra 7y ago
it's there now. https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc... > We're investigating reports of an issue with Google Calendar. We will provide more information shortly. The affected users are unable to access Google Calendar.
- bluetidepro 7y ago
  Hmm, I don't see anything there yet for me.
  - deleted 7y ago
    [deleted]
deleted 7y ago
[deleted]

deleted 7y ago

[deleted]

butler14 7y ago

"We're investigating reports of an issue with Google Calendar. We will provide more information shortly. The affected users are unable to access Google Calendar."

twostorytower 7y ago

It's amazing how many of these status pages don't actually work in many situations.

db48x 7y ago
I guess technically the "server" is responding, so...
bluetidepro 7y ago
Edited my comment to just say the same thing. Haha What's the point of them then?
- michaelmior 7y ago
  It's certainly helpful to know that Google is aware of the problem and fixing it.
hknd 7y ago
These pages at Google/Amazon/Netflix are updated by the incident response team, so it's a manual task.
SilasX 7y ago
Wasn't there that time AWS had some outage, but the red-circle picture (for failure) was itself hosted on the unavailable AWS service, so their status page didn't show it as being unavailable? Or am I mis-remembering something/repeating an urban legend?
- Dragonai 7y ago
  Nah, you're remembering correctly, this happened. The failure icon was hosted on S3, but S3 was down. It was a great moment. Here's their tweet about it: https://twitter.com/awscloud/status/836656664635846656 https://twitter.com/awscloud/status/836656664635846656
  - SilasX 7y ago
    Thank you for confirming, and the citation!
- aglionby 7y ago
  Yep, the icons were hosted on S3, which was unavailable https://www.theregister.co.uk/2017/03/01/aws_s3_outage/ https://www.theregister.co.uk/2017/03/01/aws_s3_outage/
- jgroszko 7y ago
  Yes, that was the S3 outage last year... https://news.ycombinator.com/item?id=13756111 https://news.ycombinator.com/item?id=13756111

RutZap 7y ago

falcolas 7y ago

Status pages are not driven by automation, they are driven by PMs. Amazon, Google... all of the big players work them this way. And I'm not surprised, since actually reporting it as down has a lot of political blowback (not to mention contract blowback) within the company.

Iggy173 7y ago
Also, accurately reporting about an arbitrary source of downtime means you're smart enough to avoid the same sources of downtime. Not that this can't have been an obvious reason (deleting all the servers in a datacenter or similarly trivial but severe) but it's likely impossible to ensure status page accuracy.
- chipperyman573 7y ago
  You could just ping the servers once a minute and tell if they're up or not. No need to know why they've gone down.
  - lukeschlather 7y ago
    Most outages aren't so obvious as this one, and any ping will fail intermittently (often because the ping agent has a failure.) Google definitely has loads of pings hitting Google Calendar in various ways. Exposing this monitoring to the public is not practical or really useful. (And would aid would-be attackers.)
  - yegle 7y ago
    That only indicate the frontend of the service is up and potentially running. Being about to respond to ping and being able to serve HTTP request are two different things, and being able to serve HTTP request vs a fully functional website are two different things. Think about wrong SSL certification, wrong domain mapping between frontend/backend, broken JS/CSS etc.
    - CloudNetworking 7y ago

kyrra 7y ago

it's there now. https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc21ebe3962430b2e4ae2b52e3dde98f https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc... > We're investigating reports of an issue with Google Calendar. We will provide more information shortly. The affected users are unable to access Google Calendar.

bluetidepro 7y ago
Hmm, I don't see anything there yet for me.
- deleted 7y ago
  [deleted]

deleted 7y ago

[deleted]