Mass outage or your home only?

When a connected device fails, the cause can be local, cloud-side or linked to progressive end of support.

Local failure

Only one home is affected: power, Wi-Fi, DNS, mobile app or account.

Vendor outage

Several users report the same symptom: cloud, API, certificate or app change.

End of support

The service rarely comes back: app removed, cloud closed, firmware absent or protocol abandoned.

5-minute triage checklist

Reboot router + device and verify system time.
Retry the same service over mobile data to isolate local Wi-Fi.
Check vendor status pages and public outage reports.
Compare with a second device in the same ecosystem.
If failure persists beyond 24h, prepare a maintained alternative.

Investigation playbook

Capture exact model, firmware version and outage start time.
Classify incident: local issue, vendor outage, or support sunset.
Apply reversible fixes first (DNS, re-auth, soft reset).
Escalate to replacement only when root cause is structural.

Mass-outage FAQ

How do I separate cloud outage from local failure?

If the symptom disappears on mobile data but not on local Wi-Fi, local network remains primary. If many users report the same symptom at the same time, vendor outage is more likely.

When should I replace the device?

When support sunset is confirmed, no durable fix exists, or a critical security risk remains unpatched.

Should I factory-reset at first incident?

No. Start with non-destructive fixes, then export configuration before any deep reset.