I thought maybe someone had leaked the Apollo XI watch and Omega zapped OF off the net in retribution.
Nope, a log file generating 50gb of garbage data and filling up a disk due to a software update turning on verbose logging for some reason, so one little script generated a mountain of data.
Funny thing is I assumed it might be traffic overhead due to a leaked Omega image, so I tried to access Watchuseek and that seemed to be down as well or painfully slow....then I was certain it was an embargo leak! LOL