> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/troubleshooting/broadband-clarity.md).

# Broadband Clarity

## Overview

This page explains symptoms experienced with Broadband Clarity.

## Symptom 1. Chart showing no data

Once added into Highlight, datapoints take up to an hour to start appearing.

## Symptom 2. Chart showing gaps in data

If no reliable datapoints are gathered during any quarter hour period (starting on the hour), the chart will show a gap.

## Symptom 3. Broadband Bandwidth chart absent

The chart is generated as a result of Broadband Clarity being enabled on the Features tab of the watch. Edit the watch to turn on Broadband monitoring.

Note: turning **Collect data** off/on from the watch Main tab disables Broadband Clarity.

## Symptom 4. Broadband Clarity will not enable

If the Broadband Clarity feature will not enable when in Edit watch, check that the watch type was originally activated in Highlight as an ADSL service. If not, and was incorrectly set as symmetric (type "bearer"), then the only way to enable Broadband Clarity is to first re-add the watch as ADSL or Broadband.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.highlight.net/troubleshooting/broadband-clarity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.