Something slightly strange just happened so quickly that we managed to resolve it before any bot could update…
I noticed that my local tracker was spasming again and went to check the origin memory, and sure enough, the timestamp was suddenly set to -16 instead of 0. I sent the email below to Archie about this:
Immediately after this, the origin memory’s timestamp shifted back to 0, which was followed up by the following reply from Archie:
To which I responded with:
Currently waiting on any status update or log. This one went by in a rush so its weird recapping it. I think only I and a handful of others on the NMScord managed to catch it as it went down 
Update 1:
That “error message” sounds suspiciously like what NMS tells you when you can’t connect to the discovery servers
