hello ,
i am new on the forum.
i am the network administrator for my company. we have a ccr 1036 which terminates our IP transit service. i have been mandated to ascertain what capacity is available on the transit circuit. i have been trying to do a speed test from the CCR to the mikrotik btest server
23.162.144.120
207.32.194.24
this has not been successful. see screenshot.
please i need help.
-
-
Olugbengaonadipe
just joined
- Posts: 2
- Joined:
unable to carry out speed test to mikrotik public test server
You do not have the required permissions to view the files attached to this post.
Re: unable to carry out speed test to mikrotik public test server
It seems @TomjNorthIdaho's server has some issue at the moment. Plus if you try too often, it won't let you connect for next 24 hours. So I'd suggest to post a question in the related topic.
The other server by @Martoo and yet another one by @Garrison1701 were both up at the time I was testing minutes ago.
If you are geographically distant from those servers, don't forget to use UDP, and even that way the results may be affected by some bottleneck on the path which is not related to the transit circuit you verify. Plus I'd recommend to run /interface monitor-traffic while running the btest, to see the total amount of traffic coming in if you'll run the btest while other data flow through the same circuit. There is no such possibility for traffic being sent through the circuit from your end, unfortunately.
And don't forget all those servers are run by enthusiasts as a gift to the community, so it would be unfair to require a five 9s availability.
You can use a commercial service like speedtest.net instead (commercial = sponsored by advertising), but you'll need a PC as the test client. The advantage is that it suggests geographically near servers, so the results are not that affected by overseas links.
The other server by @Martoo and yet another one by @Garrison1701 were both up at the time I was testing minutes ago.
If you are geographically distant from those servers, don't forget to use UDP, and even that way the results may be affected by some bottleneck on the path which is not related to the transit circuit you verify. Plus I'd recommend to run /interface monitor-traffic while running the btest, to see the total amount of traffic coming in if you'll run the btest while other data flow through the same circuit. There is no such possibility for traffic being sent through the circuit from your end, unfortunately.
And don't forget all those servers are run by enthusiasts as a gift to the community, so it would be unfair to require a five 9s availability.
You can use a commercial service like speedtest.net instead (commercial = sponsored by advertising), but you'll need a PC as the test client. The advantage is that it suggests geographically near servers, so the results are not that affected by overseas links.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.