Skip to content

Outage tracker / Netdata / In the US

Is Netdata down in the US?

Vendor lists an old incident, not shown as liveWhat Netdata reports

Netdata still lists an incident opened on 2026-10-22 with no update since 2026-10-23; we do not show it as live.

As of the last successful poll, 2026-11-05 16:31 UTC.

Netdata's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Netdata at Nov 5, 2026, 4:32 PM UTC.

Over the last 24 hours we completed 252 checks from Ashburn and San Jose and 252 answered cleanly, 100.00% availability.

Of the 2 other regions we check Netdata from, all 2 read checks passing right now.

Email me when Netdata reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Netdata's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing141 checks in 24h, 100.00%
San JoseChecks passing111 checks in 24h, 100.00%

Last checked Nov 5, 2026, 4:32 PM UTC.

Netdata from Ashburn and San Jose over the last 30 days

Over the last 30 days, Netdata answered our Ashburn probe in 811 ms on average, and 1 check in 20 took longer than 1,107 ms.

Over the last 30 days, Netdata answered our San Jose probe in 952 ms on average, and 1 check in 20 took longer than 1,503 ms.

Ranked by average response time across the 4 cities we check Netdata from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 497 ms and Tokyo slowest at 1,457 ms.

From Ashburn and San Jose we ran 775 checks of Netdata in 4 days, and 774 answered cleanly: 99.87% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 247 checks.

In Ashburn local time (EST), Netdata was slowest around 4 PM, at 1,049 ms on average over the last 14 days, and quickest around 11 AM, at 463 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5170100.00%896 ms
Wed, Nov 4254100.00%808 ms
Tue, Nov 324799.59%928 ms
Mon, Nov 2104100.00%860 ms

Netdata outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Netdata outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Netdata from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 99 checks
TokyoChecks passing100.00% of 60 checks

Other countries we check Netdata from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Netdata's public endpoints. They are not user reports, and they are not Netdata's own status page.

See Netdata's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Netdata has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

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

Run 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