> This kind of fault would be more indicative of a configuration error Multiple networks being affected simultaneously would seem to rule that out, no? That,

> This kind of fault would be more indicative of a configuration error Multiple networks being affected simultaneously would seem to rule that out, no? That, to me, implies either an intrinsic fault (date/time related bug) or external factors, which could be as you've said a dependency (or hostile action.)