I was aware of the access to KFN problem that presented earlier today. I'm certain it wasn't solely affecting me!
If you are reading this, you know that problem has been resolved. I spent hours investigating the problem with the help of Google AI. The short of it is that it 'appears' to have been some type of flood; a denial of service; that was the cause. Whether it was deliberate or some runaway internal corrupted process, I'm not knowledgeable enough to say. What counts, is that it has resolved.
If you are reading this, you know that problem has been resolved. I spent hours investigating the problem with the help of Google AI. The short of it is that it 'appears' to have been some type of flood; a denial of service; that was the cause. Whether it was deliberate or some runaway internal corrupted process, I'm not knowledgeable enough to say. What counts, is that it has resolved.


