@justhost the issue was, in fact, temporary-as-hoped; everything seems to be back and running; guess nobody's hurt, thanks for your patience
