do i smell a spanning tree loop...
Router error sounds a bit like a generic "IT" problem for a network organisation.
Similar to "its a batch scheduling problem" when there are no issues with the scheduler but the CR*P scripts being scheduled.
Probably translated by a press officer that has only the vaguest notion of networks existance, let alone technical issues.
I smell a fundamental configuration error rather than a router problem, spanning tree, BGP, backup route switched off or under specified or similar. Magnify that by poor monitoing and you get a nice combination for management flappage (dont change anything / blamestorming) and a nice long outage.