The IRS having their services being down with AWS and having the same trajectory means that whatever hit one also hit the other.
That connects them. They shouldn't be connected, by their own standards even.
Then Twitter getting spotty indicates that whatever happened might have spiked on Twitter, and they had to clamp down on internet chatter about the connection.
The Twitter censor bots are in overdrive right now, otherwise the server system wouldn't be strained as such.
They run Fastly, which does run at least a third of all website server spaces.
But we aren't seeing the widespread outages like we did with other AWS outages recently.
Which means Fastly is likely still running fine.
Something else in their network got tanked.
That being said, whatever that something is should absolutely not be involved with the IRS. The IRS contains the absolute most sensitive information for all United States Citizens. You would expect they'd have to be stored/accessed on completely proprietary networks, but they aren't.
Reasoning being?
The IRS being down is odd in general.
The IRS having their services being down with AWS and having the same trajectory means that whatever hit one also hit the other.
That connects them. They shouldn't be connected, by their own standards even.
Then Twitter getting spotty indicates that whatever happened might have spiked on Twitter, and they had to clamp down on internet chatter about the connection.
The Twitter censor bots are in overdrive right now, otherwise the server system wouldn't be strained as such.
Exactly! Proof they are connected. Just look at the others, all cell carrriers having the same curve as well.
They are connected, network, hardware, something. But should not be.
AWS is a hosting company and basically everyone uses them. AWS having issues probably caused the other two to go down.
They run Fastly, which does run at least a third of all website server spaces.
But we aren't seeing the widespread outages like we did with other AWS outages recently.
Which means Fastly is likely still running fine.
Something else in their network got tanked.
That being said, whatever that something is should absolutely not be involved with the IRS. The IRS contains the absolute most sensitive information for all United States Citizens. You would expect they'd have to be stored/accessed on completely proprietary networks, but they aren't.
Which is suspicious.