NuGet feed down?

[Scott]

Our automated builds have started failing, and it does not appear we can connect to the NuGet server.  We're using the v3 URL. 

It also fails when trying to connect from Visual Studio.  Error message in Visual Studio is:

[telerik.com] Failed to retrieve metadata from source 'https://nuget.telerik.com/v3/search?q=&skip=0&take=26&prerelease=false&supportedFramework=.NETStandard,Version=v2.0&supportedFramework=.NETCoreApp,Version=v3.1&supportedFramework=.NETStandard,Version=v2.1&semVerLevel=2.0.0'.
  Response status code does not indicate success: 500 (Internal Server Error).

Any idea when the feed will be back up?

[Jose]

me too

[Telerik] No se pudieron recuperar metadatos del origen "https://nuget.telerik.com/v3/search?q=telerik&skip=0&take=26&prerelease=false&supportedFramework=.NETCoreApp,Version=v3.1&semVerLevel=2.0.0".
  El código de estado de la respuesta no indica un resultado correcto: 500 (Internal Server Error).

[Dess | Tech Support Engineer, Principal]

Hello, Scott,

I am really sorry to hear that you were experiencing any difficulties.

Indeed, yesterday we were experiencing difficulties with the Nuget feed. Could you please share with us whether the problem is present today? Or it is OK now?

I am looking forward to your reply.

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

[Scott]

Yes, it is working now. Thank you!

[n/a]

I experienced the same issues yesterday with an Azure Pipelines CD build.  I submitted a case but have yet to hear back.  Initially, I was getting errors similar to Scott's.  Later in the day, I started getting 401 Unauthorized when the build is trying to restore the telerik packages.  This issue is persisting for me today.

I am using a Service Connection as detailed here:

Azure DevOps and Telerik NuGet Packages

I tried creating a new service connection and tried tweaking a few other things, but nothing seems to work.  Any help would be appreciated.

[n/a]

Disregard my comment.  In my troubleshooting, I switched my nuget.config to the v3 feed, but the service connection was pointing to the v2 feed, so there was a mismatch.