title: NuGet fails to find existing package
body: <p>How it's possible that NuGet's <code>Install-Package</code> fails with <code>Unable to find version 'x' of package 'y'</code> when that exact version is released as NuGet to the official repository and it shown on the <a href="https://www.nuget.org/packages/y" rel="nofollow noreferrer">https://www.nuget.org/packages/y</a> page.</p>
  
  <p>Here is specific sample with nuget.org content and NuGet <code>Install-Package</code> command output.</p>
  
  <p><img src="https://i.stack.imgur.com/NyOFm.png" alt="nuget package snapshot"></p>
  
  <p><img src="https://i.stack.imgur.com/Gdbeu.png" alt="install package failure"></p>
  
  <p><strong>UPDATE.</strong> Package sources are set to defaults (from nuget.org). Actually, you can see the issue just by running <code>Install-Package Log4Net.Async -Version 1.3.0</code>.</p>
  
  <p><img src="https://i.stack.imgur.com/6ZCBJ.png" alt="package sources"></p>
  
  <p><strong>UPDATE 2.</strong> I want to highlight that it's not about some developer's machine - the same things happen on Visual Studio Online Hosted Build Controller.</p>
  
  <p><strong>UPDATE 3.</strong> Here is how NuGet tries to load package and it looks like NuGet API just broken, because all these requests fail with the error below.</p>
  
  <p><img src="https://i.stack.imgur.com/L07UO.png" alt="install-package intercepted http requests"></p>
  
  <blockquote>
    <p>Resource not found for the segment 'Packages'</p>
  </blockquote>
  
  <p>Also NuGet produces a strange output on NuGet API calls that issued at VS search packages stage, please see here: <a href="http://pastebin.com/qveadrZB" rel="nofollow noreferrer">http://pastebin.com/qveadrZB</a>.</p>