MCC (Master Chief Collection) Server Incident Summary

The most interesting part of this to me is that they have a path, both in code and in process, to fallback to peer-to-peer if stuff breaks. That's pretty impressive.

I know we normally never hear about this stuff from game compaies at all, but it would be nice to have a little bit more detail.<p>&gt; Finally, it was identified that there had been some updates behind the scenes to the servers we use to relay STUN traffic as part of the ICE process which had resulted in misconfigurations.<p>What updates? How were they tested (or not)?

Really cool to see this level of transparency on an issue from a multiplayer game dev. Really cool write up

Given that the error resulted from the STUN and ICE servers, which from my understanding exist solely to play a part in the NAT punching process, would this entire situation have been mitigated if things were end-to-end IPV6?

Wow, that was a fun read! I don&#x27;t envy the people who had to stare at wireshark logs for 3 days though. Oof.

I don&#x27;t recall seeing this sort of post-mortem from a gaming provider before. Really cool to see! Kudos, Halo team and Microsoft!

The root cause is REALLY surprising. If it&#x27;s really an unrelated change to the NAT&#x2F;STUN relay server, it means that there was a pretty broad lack of change management framework.

Interesting that they call their service UDS. I was under the impression that they used PlayFab.

So if I wanted to refer to a group of them, would they be called &#x27;Masters Chief&#x27;?

Anyone else having issues viewing this on Firefox? I can see the whole webpage for an instant, then everything disappears, then it is &quot;slowing down my browser&quot;.