I'm in NC, as well, and have been experiencing the same error message since Friday. Nothing has changed.
