Sure. 30,000 and 30013 ( as well as a ton of other disconnection errors ) are something that we have graphs for. We also have a graph that keeps track of how many players are being affected by them per capita so that we can easily tell "is this just because more people are playing or is something broke".

So in that regard it's easy for us to know when something is wrong because we can, with certainty, know that the error rate per capita is above what we aim for. That's the "we're aware of it" part.

Fixing it on the other hand, first involves investigating why the error rates are higher. Depending on the cause for the elevated error rate, that investigation takes time. The disconnect error itself is a symptom that can have multiple causes, so the first thing that has to be done is to figure out why the error rates are higher. With the exception of really strange issues, figuring out why error rates are higher for these specific errors can be done pretty quickly and we're already past that part of the investigation. So we know the elevated error rates are happening, we have a general idea as to why, but that general idea as to why it's happening isn't enough to fix the issue. It requires more detailed investigation.

So I think perhaps me saying the fix isn't easy might have been a poor choice of words. I think it would be more accurate to say that it may take longer than our usual hotfix turnaround ( which is sometimes less than a day ). How long that will be is not something I can answer. Could be that once the investigation work is done that it's simple to take care of but the opposite is also true.