On the server side we are working on boosting performance, scalability and reliability. We were also in need of a new status page to better communicate the status of the service. Without further ado: meet the new status.nuget.org!
We’re happy with this new incarnation of our status page. It not only shows whether individual services are up or not, it also adds some insights in our back-end jobs like search indexing. And when we want to communicate written context about potential issues, we can now do so as well.
The question we get when we have a production service issue is the one which is displayed in a prominent position on the status page: is NuGet up or not? All our status checks are aggregated into one status which immediately tells users of our status page what is going on.
One of the key elements that we kept from the previous status page is the services status. Where our old status page just showed indivivual checks, we decided to show the current status of individual NuGet features. By clicking a particular feature we can see more details of the individual services that contribute to that feature, including their datacenter region when applicable.
Insight into back-end jobs
NuGet is not only front-end. Package uploads are a separate service. We also have several jobs running in the background - for example our indexing job. The index lag chart shows the time it takes for a new package to show up in the index. The lower the time, the faster new packages are available for consumption.
Additional context through status messages
When we detect a potential issue with the NuGet services, we are now able to comminicate about it through the status page. Whenever there’s a “hot” issue, we will show additional context about the issue at the top of the status page.
Older messages are shown near the bottom of the page. Messages are visible for one week.
With this new status page we now can provide more insight into the status of the various services that serve NuGet features and provide more accurate details on potential issues through status messages.