BryanNet

Usage or device/session accounting looks wrong

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Usage or session totals look wrong

Basic

Check the selected subscription, period and timezone. Current-subscription data is different from lifetime usage or a daily device graph. Identify whether the connection is active or completed.

Intermediate

Compare live sessions, completed accounting segments and worker/sampling progress. Check outage windows and a recent subscription transition. Delayed polling can make the display stale.

Advanced

Inspect approved usage/session records and router counters. Check counter resets, reconnects, duplicate events and segments crossing subscriptions. Do not sum cumulative samples or overlap live and stored usage.

Fix synchronization or aggregation through the supported product path. Preserve original counters and timestamps before any controlled correction. Avoid zeroing totals to make the allowance appear correct.

Verify the expected total across devices/routers and correct quota-triggered transition. If evidence cannot establish the accounting boundary, escalate with session IDs, subscription activation time, sample times and outage history.

Related guides

Related guides: Troubleshooting start here: observe, scope and collect evidence, Database diagnostics and safe query reference, Restore BryanNet safely, Logs, audit history and incident records.