Connectivity
Network outages across a fleet
Check whether affected devices share a carrier or site, then gather evidence for the next connectivity check.
Network outages across a fleet →Worked scenarios for investigating device drift, rollout faults and support requests. Follow the available evidence to a decision, then check the result on your own fleet.
Connectivity
Check whether affected devices share a carrier or site, then gather evidence for the next connectivity check.
Network outages across a fleet →Product quality
Correlate repeated syslog signatures with firmware version, device class, and rollout group.
A firmware cohort logging the same error →Customer trust
Turn device evidence into incident response, customer-facing status, and warranty context.
Support, status, and warranty share the facts →A device capture shows what happened during a specific window. A comparison with similar devices helps reveal unexpected differences.
From a device record, run about fifteen to twenty minutes of health, network path, clock skew, and process evidence - then analyse that window.
See remote diagnostics →In-app Device Check is attached to a device. Separate from free public Device Check (no account).
Open public Device Check →Pulse compares devices in the same Device Class, a group for a product type. It flags differences to investigate. Evaluation needs comparable devices on a paid plan and time for evidence to accumulate.
See how to evaluate Pulse →Install the agent, register devices, prove the loop.
Bring the first fleet online →Phone alerts, fleet conditions, and live shells on one record.
Alerts, monitors, and terminals in one workflow →Logs, alerts, remote access, and service history during support.
Run incidents from device evidence →What Dataplicity replaces, and what it complements.
Check the operating requirements →