Router profiles, speed limits and concurrency

Prerequisites and authority

Network/RouterOS authority, known topology and a recovery management path are required. Preserve existing router configuration before managed changes.

Profiles, speed and concurrency

A plan's speed/concurrency settings must translate into the router account/profile used by its active subscription. Speed is a configured limit, not a guarantee that the internet source can deliver that throughput at all times.

Confirm the active subscription and its plan.
Inspect the intended router profile and account assignment.
Verify enabled state and applied rate/concurrency settings.
Test throughput under representative conditions.
Test simultaneous sessions across applicable routers.

Stored max_devices and concurrent_devices fields must be interpreted according to the agreed product rule: device replacements are unlimited, while simultaneous connections are controlled. Do not turn the stored-device list into a lifetime device cap without an approved policy change.

Concurrency counts customer-wide live sessions and unexpired pending reservations. At capacity new admissions are rejected; existing connections are preserved. The allowance is not multiplied by router count, and device history does not itself consume a simultaneous-session slot. Test the intended admission policy across your actual routers, including disconnect and outage recovery, before using it for customers.

When a queued plan activates, profile changes and accounting boundaries must follow it. Reusing an existing connection across a subscription transition must not attribute new traffic to the old plan.

Avoid manual profile edits as a permanent fix. Desired State or later provisioning can replace them. Record a mismatch and repair it through BryanNet's supported operation.

Router profiles, speed limits and concurrency

Prerequisites and authority

Profiles, speed and concurrency

Related guides