You jump into WINBOX and go to TOOLS –> BANDWIDTH-TEST, fill in the info of another MikroTik somewhere else on the network that you want to validate the transit bandwidth capacity in between, and you hit START. So far, sounds safe enough, right? Here’s the deal though – if you like the GUI of Winbox, and most MikroTik users do – it’s much too easy to start a BTEST without setting any protections and filling your network pipe so full in one, or worse BOTH, directions, that you can’t regain enough control to hit the STOP button after you’ve STARTED a BTEST. In order to use this command – Bandwidth test server needs to be accessible. The “speed-test” command is based on the Ping Tool and Bandwidth Test. The Speed Test is an easy test tool for measuring ping, jitter, TCP and UDP throughput from one MikroTik device, to another. Let’s start with some documentation from MikroTik: What’s the problem?įirst, let’s describe what happens and why bad things can occur when you run a MikroTik BTEST bandwidth-test, then we can go into what steps can be taken to protect against it. In this article we’ll share a couple ways to ensure that you’re being a good steward of your network while also validating your available bandwidth capacity without resulting in outages or degraded services. YES! I can’t tell you how many times we’ve seen someone fire off a MikroTik BTEST to verify connectivity and bandwidth capacity between a couple of MikroTiks and not only cause themselves a painful outage, but also require a truck roll for an on-site visit to remediate.

Mikrotik router winbox