Is NuGet down?
Checks passingchecked 9 minutes ago
Our checks of NuGet pass from all 10 regions we check.
As of Nov 5, 2026, 3:32 PM UTC, RealUptime's checks of NuGet passed in all 10 regions that returned a reading.
Our checks of NuGet did not fail from two or more distant regions in the 75 days we have checked it (since Aug 22, 2026). This does not show NuGet works for users.
NuGet publishes no status feed we can read, so the only reading here is our check reading on the left.
NuGet response time, by region
Check your own site while you wait on NuGet
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not NuGet. It cannot diagnose NuGet's own systems.
What we measured, function by function
NuGet answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Get an email when our checks of NuGet fail from two or more distant regions, and again when they pass
Get an email when our checks change
We will email you when our checks of NuGet fail from two or more distant regions, and again when they pass. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 687msstatus code: 200checked: Nov 5, 2026, 3:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach NuGet normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1066msstatus code: 200checked: Nov 5, 2026, 3:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach NuGet normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 783msstatus code: 200checked: Nov 5, 2026, 2:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach NuGet normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 310msstatus code: 200checked: Nov 5, 2026, 2:59 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach NuGet normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 549msstatus code: 200checked: Nov 5, 2026, 3:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach NuGet normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 196msstatus code: 200checked: Nov 5, 2026, 3:30 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach NuGet normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 482msstatus code: 200checked: Nov 5, 2026, 3:19 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach NuGet normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1499msstatus code: 200checked: Nov 5, 2026, 3:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach NuGet normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1044msstatus code: 200checked: Nov 5, 2026, 3:21 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach NuGet normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1159msstatus code: 200checked: Nov 5, 2026, 3:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach NuGet normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using NuGet, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for NuGet yet, which is not evidence that nothing is wrong.
Recent probe events
No probe events on record yet for NuGet.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring NuGet since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for NuGet covering any window you pick, with our check readings and NuGet's own claim at the time, side by side.
Full check history for NuGet: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/nuget)<a href="https://realuptime.io/outages/nuget"><img src="https://realuptime.io/outages/nuget/badge.svg?days=30" alt="NuGet uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is NuGet down?", https://realuptime.io/outages/nuget. The readings change with every check, so give the date you read them.
How our checks compare with NuGet's stated SLA
At or above your target
Our checks of NuGet failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from NuGet's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: api.nuget.org