For the last few days, I've been unable to stay connected (sometimes I can't even select a character.) due to the error known as "cattle." I have a LOT of network experience, seeing as I recently acquired my CCNP and am looking forward to attempting the CCIE certification process, so please understand when I say I am almost certain that this is not an issue on my end of the spectrum. I've monitored my network using various methods, from my personal desktop, my laptop, my mobile phone and last but not least, my Xbox one's interface (as limited as it is.) Over the course of my time monitoring the network, here are my observations: - 10-12mb/s Download Speed consistently. - ~1mb/s Upload Speed consistently - < 2% Packet Loss, even on the worst of days with multiple devices using the network for large periods of time. - Consistent 100-130ms to Bungie's/Microsoft's Servers. - No connectivity issues on other Xbox One, PC, Playstation or Mobile games (that were not experiencing documented outages.) - 70-89% Wifi signal strength to the XBox One at all times. (Yes I've tried hard wiring to solve this issue.) - The recommended (and some select other) ports have been open for forwarding on my firewall. - Tracerts to Bungie/Microsoft Servers have not encountered any large latency spikes from hop to hop. Conclusion: Giving the evidence above, and the knowledge that my other TWC backed services are not experiencing any major service issues in my area, I can say with fairly confidently that this issue is not a result of my personal network, nor my provider whom many of my friends are using just fine. So I would like to implore that Bungie please reevaluate their stance on this "cattle" error, as it's completely prevented me from playing the game today, and has made my overall experience with destiny a rather frustrating one. A response would not only be welcome, but very much appreciated. If I don't get some response (even a simple "we're looking at it") I believe I'll be requesting a refund, or at the very least, will not invest in any DLC or future titles from the studio. I don't apologize for being a consumer, and neither should anyone else who's had these issues. The same was said for when Blizzard's Diablo 3 came out, and until I saw vast improvements in that title, I steered clear of that as well.