After several days of monitoring and investigation, the cloud-to-cloud networking problem from South Central US and West US appears to be resolved.
As we were not able to determine a specific root cause, we ask that you please open a support ticket if you experience the problem again. In the ticket, include the results of a ping and tracert for nuget.telerik.com, along with the machine's public IP address. This will allow us to directly investigate that specific connection.
Posted Mar 18, 2024 - 17:57 UTC
Monitoring
We have investigated this with the datacenter vendor and they are unable to determine any possible cause with the available information. This status has been moved to Monitoring, both the datacenter and Progress teams will be monitoring closely over the next several days.
If you experience this again, please provide us with all of the following information from the affected machine: ping, traceroute, and public IP address.
Posted Mar 15, 2024 - 20:42 UTC
Update
We have confirmed there are no issues with the Telerik NuGet services or their firewalls, so the components statuses will revert to Operational for the remainder of this investigation.
If you are affected by this issue, please open a support ticket (or reply to your existing case) with your build agent's public IP address. This will allow us to speed up the investigation with the vendor and help restore their connection to your build machines.
Posted Mar 15, 2024 - 18:09 UTC
Investigating
The Telerik NuGet servers are operating nominally. However, we are investigating reports of networking issues that are only affecting some customers who are using hosted Azure DevOps agents and AWS build hosts that are located in the West US region. This problem results in a timeout, but only in that environment's networking.
At this time, we have not been able to replicate the problem, so we are working with affected customers to try and isolate the issue and determine a solution. This status item will be updated as we learn more information.
Posted Mar 15, 2024 - 14:42 UTC
This incident affected: Telerik NuGet v3 and Telerik NuGet v2.