Diagnose a router before changing it
Open the router detail page and read several signals together. Centipid Billing can show reachability history/incidents, WireGuard state, live bandwidth/system metrics, top consumers, service state, monitoring, trends, collections, and diagnostic findings.Signal interpretation
Run diagnostics
- Verify the router identity and incident time.
- Choose Diagnose.
- Wait for findings to complete.
- Review Issues, Passed, and the full result set.
- Open a finding and read its evidence and proposed remediation.
- Apply remediation only when it matches the observed failure.
- Re-run the check and an end-to-end subscriber test.
Targeted recovery actions
- WireGuard reconnect: re-establish the management transport without rebuilding all services.
- Rotate WireGuard port: use when transport is blocked or colliding; update dependent firewall/NOC expectations as applicable.
- Sync router time: correct clock drift that affects certificates, schedules, accounting, or logs.
- Sync walled garden: refresh captive destinations needed for payment/login flows.
- Redownload Hotspot: refresh portal assets/configuration when the router copy is stale.
- Reprovision: reapply broader managed configuration after evidence shows drift/incomplete setup.
- Reboot: use only after understanding service impact and having a recovery path.
Monitoring and alerts
Add the router to monitoring, then configure Settings → Operator alerts. Verify recipient numbers and whether WhatsApp is preferred. Alert delivery depends on communication-provider readiness; a monitoring finding and a delivered SMS are separate states.High CPU or bandwidth
Use live metrics and top consumers to identify timing and scope. Check whether load corresponds to expected traffic, a package without limits, a subscriber/device anomaly, or router process pressure. Avoid changing every package or rebooting before capturing the active evidence.Escalation packet
Provide support with sanitized evidence:- the ISP and router identity (not secrets);
- start/end time and timezone;
- affected access type and approximate subscriber count;
- reachability/WireGuard/service state;
- diagnostic finding text;
- RouterOS version where available;
- one test subscriber result;
- actions already attempted and their outcomes.