could be network congestion at a node or backbone, it happens once in a while. If you can run a traceroute to na.vaultf4.com it will usually highlight where along the route the issue is occurring
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.