Skip to main content

Is NETGEAR Down?

No — NETGEAR is up

Reachable from all 8 checked regions

Average response time: 111ms

Last checked · checks run every 6 hours

Official status page: https://status.netgear.com

NETGEAR uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
83ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 40 checks
Aug 11: 100.00% uptime, 40 checks
Aug 12: 100.00% uptime, 38 checks
Aug 13: 100.00% uptime, 36 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 30 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
65ms
DNS 0ms TCP 1ms TLS 4ms TTFB 54ms
jnb
239ms
DNS 1ms TCP 0ms TLS 2ms TTFB 232ms
lax
119ms
DNS 0ms TCP 2ms TLS 5ms TTFB 104ms
lhr
71ms
DNS 0ms TCP 2ms TLS 5ms TTFB 59ms
nrt
85ms
DNS 1ms TCP 2ms TLS 4ms TTFB 74ms
ord
65ms
DNS 0ms TCP 2ms TLS 4ms TTFB 50ms
sin
56ms
DNS 0ms TCP 1ms TLS 3ms TTFB 49ms
sjc
213ms
DNS 0ms TCP 19ms TLS 21ms TTFB 134ms
syd
44ms
DNS 0ms TCP 1ms TLS 3ms TTFB 39ms

What NETGEAR does

NETGEAR makes routers, mesh systems and business access points, and runs cloud services alongside them: Orbi and Nighthawk apps for home users, Insight for business networks, and Meural for digital art frames. The distinction that matters during an incident is that the hardware routes traffic locally while the apps, remote management and account features depend on NETGEAR's servers.

What an outage looks like

The Orbi or Nighthawk app fails to connect to a router that is plainly working, since devices on the network still reach the internet. Remote management from outside the home stops while local admin over the router's own address is unaffected. Insight dashboards fail to load or show stale device state for business networks. Meural frames stop pulling new artwork. Firmware update checks return errors.

What to do about it

Check status.netgear.com, which reports Insight, Orbi, Nighthawk, Meural and the NETGEAR Store separately. If your internet works but the app does not, the outage is in the cloud layer and your network needs nothing done to it. Reach the router directly on its local address to change settings. Resist factory-resetting hardware because an app cannot see it, since that turns a temporary problem into a full reconfiguration.

Is it down for everyone, or just you?

If this page says NETGEAR is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

R
Ring
A
Arlo
S
Sonos
Cloudflare
Cloudflare

NETGEAR outage FAQ

Will my internet stop working if NETGEAR is down?
No. Routing, switching and Wi-Fi run on the hardware in your home or office and do not call out to NETGEAR to move traffic. A cloud outage affects the app, remote management, account features and firmware checks. If your devices have lost internet access at the same time, that is far more likely to be your internet provider, and the two problems are worth separating before you touch any settings.
Why can't the app find my router?
The mobile apps reach the router through NETGEAR's cloud when you are away, and often use it for account and pairing steps even on the same network. An outage in that layer makes a healthy router look absent. You can usually still administer it by browsing to its local address from a device on the network, which bypasses the cloud path entirely and confirms the hardware is fine.
Should I factory reset my router during an outage?
No, and this is the costliest mistake available during a NETGEAR incident. A reset wipes your Wi-Fi names, passwords, port forwards and mesh pairing, and re-running setup usually requires the very cloud service that is currently unavailable, leaving you worse off than before. Wait for the status page to clear, then re-check the app before concluding anything is wrong with the hardware.
Does an outage affect NETGEAR Armor or subscription features?
Subscription and account services depend on NETGEAR's servers, so licence checks and dashboards can fail during an incident. Protection already provisioned on the router generally keeps enforcing locally rather than switching off the moment the cloud is unreachable. What you lose during the incident is visibility and the ability to change configuration, which is inconvenient rather than a security gap.
Is Insight down for everyone or just my site?
The measurement above checks from several regions, which separates a NETGEAR incident from a problem at one location. Insight is listed as its own component, so it can fail while the consumer apps are healthy. If our probes are green and the status page reports nothing, look at the site's own uplink next, because access points that cannot reach the internet report as offline in Insight even though they are running.

How we measure this

  • We request NETGEAR's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where NETGEAR publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when NETGEAR goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required