Technical discussions on other sites have suggested it was likely a simple goof on a firewall setting update since DNS had continued responding over TCP throughout the outage but not UDP. In any case it’s all fixed now which would not be the case if it had been deliberate. Occam’s Razor still applies.
I’ve seen the technical discussions, it isn’t clear whether someone was:
- Messing with the routing, poorly
- Made a boo-boo while updating the NIH parent nameservers
- Tried to take down all NIH and its subdomains in a single sweep, but alternate DNS servers still had them in cache
There has been a lot of personnel churn so it could have been a lot of things ranging the spectrum of run of the mill goofs by staff, goofs by people coming into new roles ranging all the way up to insider activity by staff or vandalism by fired staff (very common). Or it could be a failed attack by adversaries NIH has always been a high priority target for state sponsored cyberattacks.
One thing it is certainly does not seem to be is deliberate action by the Administration otherwise it would have gone fully down and would have stayed down.
Dunno, seeing how DOGE/Musk have been shutting stuff down and firing people in bulk, then scrambling to restore those that/who turn out to be necessary, it seems like par for the course.
Relaxation of anti-cyberatrack measures, could also play a role.
The way people are running around yelling about the sky falling in, We could use Occams Guillotine of Truth I think.
“Yes sir, just pop your head there, and all will be revealed “
Elon’s henchmen don’t know how to properly code, no surprise
All of these sites load for me; looks like this is either localized, or out of date information.
