Is it your camera or their servers? Only four of ten publish a status page
People whose cameras stop are asking Reddit whether the company is down. Four of ten will answer, one page was abandoned in 2024, and five say nothing.
Last updated · source-check dates are listed at the foot of this page
On this page
Four of the ten camera companies this site tracks will tell you when the problem is theirs. One more has a status page it stopped configuring in May 2024. The other five publish nothing at all.
That gap is why 47 different phrasings of "{brand} issues today" turn up in Google's suggestions, one of them ending in the word reddit. People are asking strangers whether a company's servers are up, because the company will not say.
Six of the ten will not tell you when the fault is theirs. A camera that records to a card in your house does not need them to: when their servers are down it is still recording, and you can still watch it back.
Check the price on AmazonReolink Argus 4 Pro(paid link)Which camera companies publish a status page?
Four of the ten this site tracks. Ring, Google Nest and Arlo run one at status.ring.com, status.nest.com and status.arlo.com, and Wyze keeps a dated incident log inside its help centre instead. Blink, eufy, Reolink, TP-Link Tapo and SimpliSafe publish nothing.
| Brand | Status page | What it is |
|---|---|---|
| Ring | status.ring.com | 20 named components, updated the day this was checked, Atom and RSS feeds |
| Google Nest | status.nest.com | Real and configured — Setup & Pairing, Nest Apps — but blank without JavaScript |
| Arlo | status.arlo.com | Log In, Notifications, Library, Live Streaming, Video Recording, plus dated past incidents |
| Wyze | A help-centre article | Timestamped incident notes with root causes, archived back to 2024 |
| Lorex | lorex.statuspage.io | Abandoned — placeholder components, last touched 22 May 2024 |
| Blink | None | status.blinkforhome.com does not resolve |
| eufy | None | No status subdomain resolves |
| Reolink | None | No status subdomain resolves |
| TP-Link Tapo | None | No status subdomain resolves |
| SimpliSafe | None | No status subdomain resolves |
Each brand probed at status.
Blink is the one that stands out. It is owned by Amazon, as Ring is, and Ring runs the best status page in this comparison — so the capability plainly exists inside the same company.
What does a good camera status page look like?
Ring's, and it is not close. It breaks the service into 20 named components — Doorbells, Indoor Cams, Outdoor Cams, Stored Video Recordings, the iOS and Android apps, Alexa, Neighbors — and its own API reported the page updated the day this was written.
The 20 things Ring will tell you about separately
- Doorbells · Indoor Cams · Outdoor Cams · Smart Lighting · Security Systems · Accessories
- Ring iOS App · Ring Android App · Ring Mobile Apps · Ring.com
- Video On Demand · Stored Video Recordings · Ring Device Health · Access Control
- Alexa · Works with Ring · Partner Integration · Neighbors · Ring Account Management · Customer Support
Read from Ring's own status API on 26 August 2026. Whatever else this site has found about Ring, this page is the best of its kind here by a wide margin.
That granularity answers the actual question. "Ring is having problems" is not useful; "Stored Video Recordings is degraded, Doorbells is fine" tells you whether to stop rebooting your doorbell. It offers Atom and RSS too, so you can be told rather than having to check.
This site has been hard on Ring — its cameras record nothing without a plan and its pricing is unreadable. This page is the counterexample, and it is worth saying plainly.
What does an abandoned status page look like?
Lorex's, which still carries the placeholder components StatusPage ships with. Two of its five are named API (example) and Management Portal (example), every component was last touched on 22 May 2024, and it has recorded zero incidents ever.
Those "(example)" entries are the demo rows a new StatusPage account starts with. Somebody at Lorex created the page, added Lorex.com and help.lorex.com, and never came back — and in the two years and three months since, the company has apparently never had an incident worth posting.
That is worse than publishing nothing. A page reading All Systems Operational while nobody is watching answers the question wrongly rather than not answering it.
Why can't you find the status pages that do exist?
Because three of the four are not where you would look. Wyze's is a help-centre article, and that help centre returns HTTP 403 to a browser. Google Nest's renders nothing without JavaScript. Arlo's is not linked from its own support page.
| Brand | The obstacle |
|---|---|
| Ring | None — and it is linked from Ring's own support search |
| Wyze | The help centre returns HTTP 403 to a browser; the article is reachable through the public search API |
| Google Nest | The page is a JavaScript application and renders nothing without it |
| Arlo | Not linked from the support page its own site redirects you to |
| Lorex | Only at lorex.statuspage.io — status.lorex.com does not resolve |
Checked from one machine with a full browser header set. A status page nobody can reach during an outage is doing half the job.
Wyze's is the frustrating one, because the writing is the best here. Its entries are timestamped to the minute, follow through to a cause, and the archive runs back to 2024.
The incident log nobody can reach with a browser
- 7 July 2026, 12:33 PM PT — "We have located the root cause and the user experience should be back to normal. We will continue to monitor the status and thank you for your patience."
- 20 October 2025, 4:23 PM PT — "AWS (Amazon Web Services) has identified and resolved the issues that affected parts of Wyze's infrastructure."
- 17 June 2025, 4:46 PM PT — "We have found the issue causing delayed notifications and were able to resolve it. Notification delivery should be returning to normal."
Three entries from Wyze's Service Status and Known Issues article and its archive, read 26 August 2026 through the public help-centre search API. The second is a company naming its cloud provider as the cause of its own outage, which nothing else in this comparison does.
The middle entry is the one worth noting. Naming your own cloud provider as the reason your customers' cameras stopped is not a comfortable thing to publish, and no other brand in this comparison publishes anything comparable. It is a company being straight with people, on a page a browser is refused.
What do you do when a company publishes no status page?
Buy a camera that does not need their servers. A camera recording to a card in its own body keeps recording through an outage, which is the only version of this problem you can solve from your side.
An outage is the cleanest illustration of a conclusion this site keeps reaching from other directions. A Reolink camera writing to a microSD card does not care whether Reolink's cloud is up.
Short of that: if your brand is one of the four, bookmark the page now rather than hunting for it mid-outage. If it is one of the five, you will find out from Reddit — which is what the search data already shows people doing.
Cameras that keep working when the cloud does not
Specifications as published by each maker, read 26 August 2026. Nothing was tested and nothing is ranked. Both of these write to storage you own, which is the only part of an outage you control — a card or a hub in your house does not go down with a company's servers.
- Form
- Base station for eufy cameras and sensors
- Storage
- 16 GB built in, expandable to 16 TB
- Expansion
- 2.5" SATA drive, 5V — 12V drives unsupported
- Subscription
- No monthly fee for local storage
- Form
- Outdoor camera on a bracket
- Power
- 5000 mAh battery, optional 6W solar panel
- Video goes to
- microSD in the camera, up to 512 GB
- Subscription
- Not required for local recording
As an Amazon Associate I earn from qualifying purchases. This costs you nothing and never affects what is covered here.
How this was checked
Every brand was probed on 26 August 2026 at status.<brand>.com and <brand>.statuspage.io from one machine with a full Chrome header set, then confirmed through the machine-readable summary endpoint where one exists. Ring's component list and Lorex's dates are read from those endpoints rather than from the rendered pages: https://status.ring.com and https://lorex.statuspage.io.
Arlo's services are from https://status.arlo.com, Nest's configuration from the JSON embedded in https://status.nest.com , and Wyze's wording from its Service Status article, read through the public help-centre search API because the help centre refuses a browser.
Two lookalike pages were excluded. blink.statuspage.io is titled "blink Status" and belongs to a Bitcoin wallet — its components are Bitcoin layer, Lightning layer and Stablesats. And a search result claiming status.blinkforhome.com is Blink's official page is wrong: it does not resolve. Third-party monitors that watch these brands from outside were not counted, because the question here is what the companies themselves publish.
No cameras were tested and nothing here is troubleshooting advice. This is a comparison of what ten companies publish about their own outages.
Corrections
Status pages appear and disappear quietly — one here has sat untouched since 2024. If a brand publishes one, or Lorex's starts naming real services, this page gets the new answer and a new date. If you know of an official page we missed, tell us: a page that exists and cannot be found is exactly what this article is about, so that correction would be a finding rather than an embarrassment.
