Skip to main content
Bscheck checks availability from external networks. In Flow, open the Health tab. New checks require configured external provider integration; viewing the saved report does not trigger a new check.

Run the check.

  1. Select the desired login or target of Flow and the verification provider.
  2. Filter the available points by operator and region, mark the necessary verification units and base stations.
  3. Check the selected parameters and run the check. The blank list is rejected until the ISP is asked.
  4. Wait for the result and open the details.
Checks can be paid. An incomplete request remains incomplete; the panel does not send a repaid POST automatically; an API error, authorization, transportation, or lack of funds does not prove a failure of the checked connection.

Read the result

In the tab, up to 100 saved reports are available: time, target, provider, operator, region, base station, ICMP/TCP/TLS, errors, omissions and cost. Response details are cleared of sensitive fields. The history of external reports is not limited to the last 50 internal samples. Successful completion of the request means that the provider has performed the operation. Accessibility is determined by the results of specific checks: HTTP 200 from the plug does not make the connection serviceable, and a successful ICMP does not cancel the failure of the TCP / TLS of the desired port.

Impact on health and Telegram

A current confirmed negative result can reduce Flow’s health to degraded; existing critical from internal checks remains a more serious condition. The evaluation takes into account the new report, the version applied, the login binding and the availability of the provider. Results older than six hours do not continue to confirm the current external problem. Manual external verification does not update the time of internal L1-L4 checks. In Settings → Telegram has a category Bscheck: availability of with common addressee and repeat settings. Before sending, the relevance of the report is checked. The recovery message is not sent without a previous delivered error. Background recalculation of status and notifications uses saved reports and does not run paid checks.

Verification

Match target, login, Flow version, time and selected networks. If a confirmed failure, check the connection from the affected network and compare it to internal diagnostics: test levels.

Rollback

Verification retains surveillance and can change health and notification scores, but does not rewrite route configuration. Paid request cannot be reversed by Flow rollback. For new launches, change point selection; for notifications, category and repeats. Inappropriate old result is not corrected by rolling back a running circuit. The availability of features depends on the version installed; code verification is not a substitute for checking your infrastructure.