Documentation

Appearance

ISP tags and connection quality ​

When a wave of devices goes dark, the first operational question is whether the population shares a connectivity provider. Dataplicity can attach ASN-derived ISP property tags and, on supported plans, a short per-device connection-quality window.

What the product provides ​

SignalWhat it isWhat it is not
ISP property tagsAutomatic tags such as location:isp:starlink and other location:isp:* slugs inferred from viewer ASN at authenticationModem-reported carrier telemetry or a multi-month ISP analytics warehouse
Connection qualityRecent reachability and latency for a device (about the last day on Pro+ plans)Proof of application health or customer-impact without monitors

Use both with device monitors scoped to the same tags so provider cohorts raise their own alerts.

Separate provider from product ​

  1. Filter inventory or the fleet map by the ISP tag that matches the report (location:isp:starlink or another location:isp:* value).
  2. Compare that cohort with peers in the same class that do not share the tag.
  3. Open connection quality on representative affected units to distinguish “cannot reach us” from “reachable but slow.”
  4. Write the altitude on the incident - provider vs product - before dispatch, firmware bisects, or customer status updates.

If the ISP-tagged monitor moves while untagged peers stay healthy, treat it as a connectivity-cohort investigation first.

Monitor the cohort ​

Scope offline or ratio monitors to the ISP tag plus the usual production filters. Example shape:

text
class: edge-gateway
include: environment:production, location:isp:starlink
exclude: maintenance:active
condition: offline ratio with hysteresis

Tune thresholds in Create monitors and alerts and Device monitors. Keep customer-facing status free of internal hostnames and diagnostics.