{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by SenseiSub:
11/25/2019 6:13:37 AM
2
A detailed statement from Bungine on the 22nd, 23rd of November outage
Given the extensive time (10+ hours) it took to recover from this failure on the 22nd/23rd of November [1] (depending where you are in the world) it would be adequate to share the high level bullet points of the devops techincal postmortem, ie. what was the root cause, how did they go about it and how does Bungie plan to avoid it in the future. This kind of public report is standard at least in the cloud industry.
I am sure your community would find it re-assuring. Yes/No?
1. [url]http://twitter.com/BungieHelp/status/1197950856852721664[/url]
-
Are accidents not allowed to happen? Sheesh.
-
All we know soo far is someone made an critical error writing code for an update. Bungie does need to clarify exactly what happened. Transparency is key to keeping a happy playerbase. Otherwise all trust goes out the window.
