There's no logical reason I can think of that would link the first incident you describe with the second. If these are different sites as you suggest, the VC's wouldn't even know about each other.
The first site loop problem could theoretically destabise the IAPs I suppose, potentially resulting in a memory issue. Difficult to be sure. If a reboot clears that, I'd just put it down to experience and concentrate on preventing the loops if possible.
In terms of the second site, I think you should consider the incidents unrelated. VC anomalies could theoretically have different root causes, but display very similar symptoms as a result on the GUI (things missing etc).
This second issue is more strange. If nothing signficant occured to that network around that time, you could try upgrading code? Check your version against the latest for VC communication issues to member IAPs. If nothing jumps out, I'd log it with TAC I think.