Speed Meter schedule breaks on unreachable server

Speed Meter appears functionally broken. Many might want to use Speed Meter when battling with a problematic internet connection, scheduled logging could be ideal for this (introduced in this forum post), but an unattended schedule is interrupted by a Yes/No dialog box when a line speed cannot be calculated due to an unreachable test server. These 0.0Mbits/s results are exactly what we want to log, failure logging is more important than success logging. The schedule does not resume until manual intervention with the dialog to acknowledge the unreachable server.

This seems like a simple feature fix: unreachable servers should be logged as 0Mbits/s, and the next scheduled attempt made. The ability to change test servers is already in the interface, so the dialog box that suspends the schedule to suggest this is redundant. Alternatively the Speed Test function could try alternate test servers without manual intervention.

Here is an example where the scheduled logging has been suspended for 10 hours waiting for manual interaction with the Yes/No dialog. The period of downtime on the line has not been logged and its duration is also unknown.

Thank you for the feedback. Unfortunately it's not clear why the speed testing was not working for 10 hours. Basically there are three possibilities:

1. A testing server is down. In this case another server is attempted automatically in the next round without user intervention.
2. Internet connection is down. Since the application can't determine whether it's the connection or the server, it will likewise attempt testing with another server in the next round.
3. Something went wrong and a bug prevented the application from continuing speed testing. We will run a long-time test to see if there is an issue there.

The reason you had to acknowledge using a new server is that you initiated a test manually. In this case if the test fails, NetWorx lets the user know that there was a problem. When running unattended, no prompt will be shown and the application will keep trying different servers.

Logging failures, while applicable to your case, is not something the application does. If a test fails, recording a zero speed is misleading as the test could fail due to a server issue, while the connection is still up and running.

For connection testing, there is a separate feature called Connection Monitor. It tests the availability of major Internet web-sites and keeps a log of downtime.