This was resolved some time ago, but we kept the issue open here as we were still troubleshooting. All systems are now operational as normal. The cause was some config changes made by our network team today in efforts to resolve minor issues, which unfortunately went wrong due to human error introduced to some config files.
