NuGet Performance

After a lengthy observation period, we can consider this issue resolved.

We have changed the status to Operational as the NuGet service has been stable and performant for over 18 hours. We will be keeping this incident open, closely monitoring performance, until all the dependent services have finished deploying their planned upgrades.

We are aware of degraded performance resulting in a timeout when fetching NuGet packages; this is due to a dependent system, rather than the NuGet Server itself. A fix is currently in testing and is planned to be deployed to those dependent systems within the next 24 hours,

Until the fix is implemented, if you experience any timeout errors when searching or restoring packages, please wait a few minutes and try again (we're seeing an average unresponsiveness timeframe of 2-3 minutes per occurrence).