Router offline recovery and reconciliation

Prerequisites and authority

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

Recover a temporarily unreachable router

Preserve existing connected sessions during a temporary management outage where the router and upstream remain operational. This is the agreed behavior, bounded by router-local enforcement and actual network conditions. Subscription expiry must still be enforced; an outage is not an unlimited extension of paid access.

Identify whether the failure is management-only or also affects customer internet.
Record the last successful sync, outage start and affected router.
Check power, upstream, VPN/routing and API service without changing entitlements.
Restore the management path.
Inspect queued/failed operations and run supported reconciliation.
Verify valid accounts, expired access, active sessions and accounting gaps.
Confirm a subsequent scheduled sync succeeds.

Do not disable customer accounts merely because an API health check timed out. Equally, do not promise that already-connected sessions survive router power loss, upstream failure or locally enforced expiry.

Recovery must reconcile changes made while the router was unavailable, including expiry, device blocks and profile transitions. Avoid duplicate accounting when events arrive late or counters restart.

Outage timing and expiry enforcement depend on your release and managed RouterOS scripts. Record the affected accounts and timing, then use Router connection fails or API authentication is rejected, Remote router WireGuard tunnel fails or Cross-router provisioning and reconciliation issues to isolate the failed layer.

Router offline recovery and reconciliation

Prerequisites and authority

Recover a temporarily unreachable router

Related guides