On 22 April 2026 at 17:07 UTC, our monitors picked up what looks like a service issue with NuGet.org. We saw an HTTP 503 error — a server-side problem that typically means the service is temporarily overwhelmed or undergoing maintenance. Here's what we're seeing and what it might mean for you.
What Our Monitors Are Showing
Our automated checks detected a 503 Server Error from NuGet.org's servers at 17:07 UTC on 22 April. A 503 error generally signals that the service is temporarily unavailable, often due to high load, a backend service failure, or planned maintenance.
We looked at NuGet's official status page and found that they've confirmed a degradation. According to their latest update, NuGet.org itself — the web gallery where you browse and manage packages — is showing as degraded. The good news is that from what we can see, the core restore and package publishing functions appear to be operational. That means:
- Downloading packages (via Restore) is working normally
- Uploading new packages is operational
- Search functionality seems unaffected
- V3 and V2 API protocols for restoration are both running
So while browsing the gallery website might feel sluggish or throw errors, the backbone services that power most developer workflows appear to be holding up. NuGet's team posted their degradation notice at 17:10 UTC — just a few minutes after our monitors flagged it — so they were already aware and tracking it.
What We Don't Know Yet
As an independent monitoring service, we're seeing what our checks detect, but we don't have visibility into NuGet's internal systems or what triggered this issue in the first place. NuGet's status page hasn't shared a root cause yet, so we can't tell you whether this is a load spike, infrastructure problem, or something else. It's worth checking their status page directly for updates as more information becomes available.
What You Can Do in the Meantime
If you're experiencing trouble with NuGet.org:
- Try again in a few minutes. Degradation events like this are often resolved quickly.
- If you need to restore packages, use your package manager or IDE directly rather than browsing the web gallery. The restore services appear to be working fine.
- Check NuGet's status page at status.nuget.org for the latest official updates.
- Reach out to NuGet support if you're blocked. They provide support at support@nuget.org or via @nuget on social media.
Keep an Eye on NuGet with Uptrue
If you rely on NuGet and want to catch issues like this as soon as they happen, you can monitor it yourself with Uptrue. We're an independent uptime monitoring platform, and you can add any service you care about to your own dashboard for free at https://uptrue.io. That way, you'll get alerts the moment something looks off — no need to wait for someone else to spot it.
A Note on Timing
What we've shared here is based on what our monitors detected at 17:07 UTC on 22 April 2026. The situation may well have improved or changed since then. For the most current and authoritative information, always check NuGet's official status page directly. That's where the team posts real-time updates about their services.