Overall It is an excellent tool for monitoring network infrastructure. Currently, I have almost 100 network interface monitoring with this tool. All details historical data & reports in one place. Now I can fight with my upstream ISP with solid proof that there is no lag in our office infrastructure but at ISP side latency.

Thanks, team Smokeping. Review collected by and hosted on G2.com.

Nothing to dislike, but it could be better if we get a better color code. Review collected by and hosted on G2.com.

It's free! If you know what you are doing, it could be the best tool for you to monitor all your circuits, branch office; basically anything that allows ping reply. It could show the historical state of any circuit as long as 365 days ago. Ideally, you could add as much as node as you want. Off course, it depends on many factor such as the Smokeping server's capacity, bandwidth etc. Not only it shows the downtime of any node, but also the latency of the circuit. There are some colored representation so that one could understand the severity of packet loss of any circuit. Review collected by and hosted on G2.com.

One of the major drawback of the tool is there is no support. You have to spend much time to understand the nitty-gritty of the tool. For a small business. it's fine. But for large scale monitoring, this tool breaks sometime. Only then you have to change some of the core settings like "probe time", "CheckLatency" etc. Setting up a server is also painful. As there is no GUI management interface for the tool. Review collected by and hosted on G2.com.

As the name implies , it is a tool for measuring and graphing network latency using ping. It is said that the name was given because the graph looks like smoke, cool right. A must have tool when checking the quality of communication where latency is critical (e.g. VoIP environment) and provide historical latency visualization. This was way better than our self-implementation of capturing historical network deterioration using CLI mtr logs.

Aside from being free and open-source, it works even on a server with fairly low specifications as it only do pings and graphs metrics. Review collected by and hosted on G2.com.

Configuration is really painful because this is an old-fashioned OSS. It takes time and effort when changing settings and / adding new probes to monitor-not done via web UI. Review collected by and hosted on G2.com.

SmokePing is free fully OpenSource and provides graphical visualization for monitor the latency and packet loss. SmokePing also have the option to trigger alarm as per threshold settings. SmokePing uses RRDtool to maintain a long-term data archive and provides graphical visualisation. SmokePing supports a plug-in architecture that can easily add new latency measurement capabilities. Review collected by and hosted on G2.com.

From my view, I haven't faced any issues with SmokePing, so there is nothing I found to dislike. Review collected by and hosted on G2.com.

It's easy to configure and nice to keep track of network latency or any packet lost.

Simple and easy tool but very helpful and powerful. Review collected by and hosted on G2.com.

Smokeping make his job very well and graphically it's easy and nice to see the latency on the network but the design is a little bit old school in comparaison of other tools like grafana. Review collected by and hosted on G2.com.

This tool is good for WAN optimization and especially in MPLS and now SDWAN scenario.

For the corporate sector this product is good. Review collected by and hosted on G2.com.

It's a little bit difficult for begginers and newly network engineers. Review collected by and hosted on G2.com.

Monitoring graph. Which are real-time show-up and down time. Review collected by and hosted on G2.com.

Time latency. if a dashboard for adding nodes or ips. Review collected by and hosted on G2.com.

A great tool for monitoring multiple nodes in a network. It shows the exact downtime and the level of packet loss. Also, it is free. Review collected by and hosted on G2.com.

There is no alarming system if any node gets down. One has to check manually momentarily to know the status of a node. Review collected by and hosted on G2.com.

If something goes down, I get an alert. If latency is too high, I get an alert. Setting it up was a fun and educational experience. Review collected by and hosted on G2.com.

The learning curve is a bit steep, but I actually liked that about it. I'm just mentioning it here, because if you're looking for something that works out of the box, this ain't it. Review collected by and hosted on G2.com.

Alerts and graphs smoke. Isnt easy to read it but when you got it is very useful. Review collected by and hosted on G2.com.

Sometume offset of probes brokes.

Config file can be made easier. Review collected by and hosted on G2.com.