July 27 01:27 UTC: The problem was caused by a failed network device in the server rack where opal17 is located. The failed component has been replaced, and connectivity to opal17 has been fully restored.
July 27 00:50 UTC: Connectivity to opal17 was recently disrupted by local network hardware issues, techs on site working to restore connectivity.
