3 ms·

> Mar 08, 2023 - 13:14 EST > Update - We are continuing to make progress towards recovering all services. Data ingestion and monitor notifications remain delaye

> Mar 08, 2023 - 13:14 EST > Update - We are continuing to make progress towards recovering all services. Data ingestion and monitor notifications remain delayed across all data types. > Mar 08, 2023 - 12:29 EST > Update - We continue progress towards recovering all services. Data ingestion and monitor notifications remain delayed across all data types. > Mar 08, 2023 - 11:46 EST > Update - We continue progress towards recovering all services. Data ingestion and monitor notifications remain delayed across all data types. ----- I won't post all of it, but you get the picture. Datadog's status updates go on like this for 12 hours. This is a status update anti-pattern. These updates add no value, except maybe some small reassurance that Datadog hasn't forgotten they are down, and they continue to work on it. But it's actually worse than no update at all, because now every customer needs to parse through a whole mess of these updates to try and figure out what's happening, and if you subscribe to the updates, you start getting spam with no new information every 45 minutes. I know companies are in a bind here. They don't want to provide estimates they might miss, or adhoc engineering info without vetting. On the other hand, customers complain about a lack of communication if there are no updates. But spamming your status page like this is not a real update, it's a pretend update. Just something to point to when customers complain about a lack of communication, but ultimately still a lack of communication.

palijer 4y ago
I agree they don't add anything and do subtract, but I think it is the lesser of the two evils. I find myself wasting a lot of time refreshing, and force reloading JavaScript on incident updates if they haven't had an update in hours. I'd much rather have a look and "cool, the auto-communicate thing is still broadcasting the same message as of 12 minutes ago". StatusPage is definitely missing a "last update still current as of $time" option, but I prefer the repetition personally. It likely reduces customer anger as well saying "there hasn't been an update in hours!?!" like the recent Atlassian outage and Okta as well.
- jlmorton 4y ago
  > It likely reduces customer anger I think you're probably right, and I think that's what ultimately irks me. It's like an infinite no-update-required hack. With that said, the recent updates have been informative, so I'll stop complaining. Cheers to the team working through what must've been a tough problem.

palijer 4y ago

I agree they don't add anything and do subtract, but I think it is the lesser of the two evils. I find myself wasting a lot of time refreshing, and force reloading JavaScript on incident updates if they haven't had an update in hours. I'd much rather have a look and "cool, the auto-communicate thing is still broadcasting the same message as of 12 minutes ago". StatusPage is definitely missing a "last update still current as of $time" option, but I prefer the repetition personally. It likely reduces customer anger as well saying "there hasn't been an update in hours!?!" like the recent Atlassian outage and Okta as well.

jlmorton 4y ago
> It likely reduces customer anger I think you're probably right, and I think that's what ultimately irks me. It's like an infinite no-update-required hack. With that said, the recent updates have been informative, so I'll stop complaining. Cheers to the team working through what must've been a tough problem.