Skip to content

Outage tracker / NuGet

Is NuGet down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached NuGet from all 10 regions we check.

As of Oct 5, 2026, 9:00 PM UTC, NuGet answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured NuGet (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 9:00 PM UTC
US-East356 msOperational
US-West328 msOperational
Europe418 msOperational
Asia-Pacific1088 msOperational
US-Central240 msOperational
Canada212 msOperational
UK509 msOperational
Southeast Asia849 msOperational
Australia924 msOperational
South America987 msOperational
their status pagetheir claim, not our reading

NuGet publishes no status feed we can read, so the only independent reading here is ours on the left.

NuGet response time, by region

US-East
489msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 491ms2026-09-07 UTC: p95 511ms2026-09-08 UTC: p95 570ms2026-09-09 UTC: p95 538ms2026-09-10 UTC: p95 444ms2026-09-11 UTC: p95 543ms2026-09-12 UTC: p95 467ms2026-09-13 UTC: p95 571ms2026-09-14 UTC: p95 546ms2026-09-15 UTC: p95 647ms2026-09-16 UTC: p95 544ms2026-09-17 UTC: p95 448ms2026-09-18 UTC: p95 479ms2026-09-19 UTC: p95 478ms2026-09-20 UTC: p95 475ms2026-09-21 UTC: p95 454ms2026-09-22 UTC: p95 555ms2026-09-23 UTC: p95 570ms2026-09-24 UTC: p95 711ms2026-09-25 UTC: p95 542ms2026-09-26 UTC: p95 618ms2026-09-27 UTC: p95 536ms2026-09-28 UTC: p95 616ms2026-09-29 UTC: p95 601ms2026-09-30 UTC: p95 481ms2026-10-01 UTC: p95 594ms2026-10-02 UTC: p95 477ms2026-10-03 UTC: p95 470ms2026-10-04 UTC: p95 470ms2026-10-05 UTC: p95 489ms
Sep 6Sep 20Oct 5
US-West
462msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 630ms2026-09-07 UTC: p95 594ms2026-09-08 UTC: p95 404ms2026-09-09 UTC: p95 391ms2026-09-10 UTC: p95 410ms2026-09-11 UTC: p95 367ms2026-09-12 UTC: p95 352ms2026-09-13 UTC: p95 278ms2026-09-14 UTC: p95 345ms2026-09-15 UTC: p95 437ms2026-09-16 UTC: p95 552ms2026-09-17 UTC: p95 451ms2026-09-18 UTC: p95 485ms2026-09-19 UTC: p95 403ms2026-09-20 UTC: p95 444ms2026-09-21 UTC: p95 441ms2026-09-22 UTC: p95 539ms2026-09-23 UTC: p95 520ms2026-09-24 UTC: p95 742ms2026-09-25 UTC: p95 720ms2026-09-26 UTC: p95 718ms2026-09-27 UTC: p95 698ms2026-09-28 UTC: p95 659ms2026-09-29 UTC: p95 643ms2026-09-30 UTC: p95 460ms2026-10-01 UTC: p95 526ms2026-10-02 UTC: p95 520ms2026-10-03 UTC: p95 490ms2026-10-04 UTC: p95 393ms2026-10-05 UTC: p95 462ms
Sep 6Sep 20Oct 5
Europe
388msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 339ms2026-09-07 UTC: p95 278ms2026-09-08 UTC: p95 293ms2026-09-09 UTC: p95 286ms2026-09-10 UTC: p95 320ms2026-09-11 UTC: p95 274ms2026-09-12 UTC: p95 352ms2026-09-13 UTC: p95 348ms2026-09-14 UTC: p95 454ms2026-09-15 UTC: p95 318ms2026-09-16 UTC: p95 374ms2026-09-17 UTC: p95 410ms2026-09-18 UTC: p95 371ms2026-09-19 UTC: p95 388ms2026-09-20 UTC: p95 437ms2026-09-21 UTC: p95 440ms2026-09-22 UTC: p95 442ms2026-09-23 UTC: p95 411ms2026-09-24 UTC: p95 989ms2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 759ms2026-09-30 UTC: p95 392ms2026-10-01 UTC: p95 408ms2026-10-02 UTC: p95 474ms2026-10-03 UTC: p95 427ms2026-10-04 UTC: p95 405ms2026-10-05 UTC: p95 388ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 809ms2026-09-12 UTC: p95 934ms2026-09-13 UTC: p95 910ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 922ms2026-09-16 UTC: p95 993ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 914ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
337msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 379ms2026-09-07 UTC: p95 399ms2026-09-08 UTC: p95 357ms2026-09-09 UTC: p95 382ms2026-09-10 UTC: p95 421ms2026-09-11 UTC: p95 379ms2026-09-12 UTC: p95 397ms2026-09-13 UTC: p95 413ms2026-09-14 UTC: p95 423ms2026-09-15 UTC: p95 411ms2026-09-16 UTC: p95 381ms2026-09-17 UTC: p95 450ms2026-09-18 UTC: p95 403ms2026-09-19 UTC: p95 461ms2026-09-20 UTC: p95 436ms2026-09-21 UTC: p95 520ms2026-09-22 UTC: p95 377ms2026-09-23 UTC: p95 607ms2026-09-24 UTC: p95 323ms2026-09-25 UTC: p95 395ms2026-09-26 UTC: p95 325ms2026-09-27 UTC: p95 287ms2026-09-28 UTC: p95 358ms2026-09-29 UTC: p95 408ms2026-09-30 UTC: p95 447ms2026-10-01 UTC: p95 392ms2026-10-02 UTC: p95 374ms2026-10-03 UTC: p95 368ms2026-10-04 UTC: p95 392ms2026-10-05 UTC: p95 337ms
Sep 6Sep 20Oct 5
Canada
431msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 339ms2026-09-07 UTC: p95 245ms2026-09-08 UTC: p95 298ms2026-09-09 UTC: p95 328ms2026-09-10 UTC: p95 243ms2026-09-11 UTC: p95 328ms2026-09-12 UTC: p95 322ms2026-09-13 UTC: p95 300ms2026-09-14 UTC: p95 349ms2026-09-15 UTC: p95 347ms2026-09-16 UTC: p95 284ms2026-09-17 UTC: p95 415ms2026-09-18 UTC: p95 392ms2026-09-19 UTC: p95 241ms2026-09-20 UTC: p95 432ms2026-09-21 UTC: p95 682ms2026-09-22 UTC: p95 692ms2026-09-23 UTC: p95 358ms2026-09-24 UTC: p95 277ms2026-09-25 UTC: p95 630ms2026-09-26 UTC: p95 386ms2026-09-27 UTC: p95 426ms2026-09-28 UTC: p95 313ms2026-09-29 UTC: p95 365ms2026-09-30 UTC: p95 581ms2026-10-01 UTC: p95 643ms2026-10-02 UTC: p95 428ms2026-10-03 UTC: p95 452ms2026-10-04 UTC: p95 347ms2026-10-05 UTC: p95 431ms
Sep 6Sep 20Oct 5
UK
541msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 239ms2026-09-07 UTC: p95 302ms2026-09-08 UTC: p95 313ms2026-09-09 UTC: p95 449ms2026-09-10 UTC: p95 399ms2026-09-11 UTC: p95 751ms2026-09-12 UTC: p95 454ms2026-09-13 UTC: p95 529ms2026-09-14 UTC: p95 471ms2026-09-15 UTC: p95 448ms2026-09-16 UTC: p95 415ms2026-09-17 UTC: p95 436ms2026-09-18 UTC: p95 405ms2026-09-19 UTC: p95 461ms2026-09-20 UTC: p95 466ms2026-09-21 UTC: p95 435ms2026-09-22 UTC: p95 677ms2026-09-23 UTC: p95 458ms2026-09-24 UTC: p95 461ms2026-09-25 UTC: p95 432ms2026-09-26 UTC: p95 632ms2026-09-27 UTC: p95 496ms2026-09-28 UTC: p95 504ms2026-09-29 UTC: p95 495ms2026-09-30 UTC: p95 518ms2026-10-01 UTC: p95 539ms2026-10-02 UTC: p95 544ms2026-10-03 UTC: p95 555ms2026-10-04 UTC: p95 673ms2026-10-05 UTC: p95 541ms
Sep 6Sep 20Oct 5
Southeast Asia
1.9sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 483ms2026-09-07 UTC: p95 472ms2026-09-08 UTC: p95 683ms2026-09-09 UTC: p95 704ms2026-09-10 UTC: p95 460ms2026-09-11 UTC: p95 634ms2026-09-12 UTC: p95 753ms2026-09-13 UTC: p95 549ms2026-09-14 UTC: p95 652ms2026-09-15 UTC: p95 433ms2026-09-16 UTC: p95 396ms2026-09-17 UTC: p95 390ms2026-09-18 UTC: p95 916ms2026-09-19 UTC: p95 483ms2026-09-20 UTC: p95 732ms2026-09-21 UTC: p95 872ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5

Is it NuGet, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see NuGet go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching NuGet, and again when they can reach it again. That is our own measurement from ten regions, not NuGet's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 356msstatus code: 200checked: Oct 5, 2026, 8:50 PM UTC
      0 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-West
      Operationallatency: 328msstatus code: 200checked: Oct 5, 2026, 8:37 PM UTC
      0 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-Central
      Operationallatency: 240msstatus code: 200checked: Oct 5, 2026, 8:20 PM UTC
      0 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.
    • Canada
      Operationallatency: 212msstatus code: 200checked: Oct 5, 2026, 8:32 PM UTC
      0 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 America
    Operationallatency: 987msstatus code: 200checked: Oct 5, 2026, 9:00 PM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 418msstatus code: 200checked: Oct 5, 2026, 8:51 PM UTC
      0 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.
    • UK
      Operationallatency: 509msstatus code: 200checked: Oct 5, 2026, 8:55 PM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1088msstatus code: 200checked: Oct 5, 2026, 8:36 PM UTC
      0 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 Asia
      Operationallatency: 849msstatus code: 200checked: Oct 5, 2026, 8:47 PM UTC
      0 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.
    • Australia
      Operationallatency: 924msstatus code: 200checked: Oct 5, 2026, 8:54 PM UTC
      0 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 outages

No outages on record yet for NuGet.

measured 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 measurements and NuGet's own claim at the time, side by side.

Full availability history for NuGet: 90-day availability by region, month-by-month uptime, and every incident 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 servers

Put this badge in your README

NuGet uptime measured by RealUptimeLive, from this page's own readings.
[![NuGet uptime measured by RealUptime](https://realuptime.io/outages/nuget/badge.svg?days=30)](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What NuGet's SLA implies, from our measurement

At or above your target

We measured none of downtime for NuGet over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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

primaryfunctional: live API
https://api.nuget.org/v3/index.json
secondary
https://www.nuget.org/
secondary
https://status.nuget.org/
RealUptime is not affiliated with NuGet; the name identifies what we measured, and nothing here speaks for NuGet's own team. We send a single web request to NuGet from 10 regions on our own schedule and time the response. We do not see inside NuGet's systems, do not use an account or real transaction, and are not the same signal NuGet's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for NuGet is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.