Oh how I would love if RouterOS CLI had fping like funcionality.
Something like this:
fping -e -l -Q 60 -p 5000 ip1 ip2 ip3 ip4
pings ip1, ip2, ip3, ip4, one icmp request every 5000ms
And only show summary every 60 seconds.
This would allow to send heavy ping traffic (to measure latency and packet loss under load) and only see the summary.
And the ability to ping multiple hosts at once.
A real world example (just changed the host names/ips):

> fping -e -l -Q 60 -p 50 ip1 ip2 ip3
[08:00:20]
ip1 : xmt/rcv/%loss = 1198/1198/0%, min/avg/max = 0.16/0.31/13.0
ip2 : xmt/rcv/%loss = 1197/1188/0%, min/avg/max = 34.2/34.7/39.2
ip3 : xmt/rcv/%loss = 1196/1180/1%, min/avg/max = 34.1/36.3/42.0
[08:01:20]
ip1 : xmt/rcv/%loss = 1196/1196/0%, min/avg/max = 0.17/0.29/3.50
ip2 : xmt/rcv/%loss = 1196/1178/1%, min/avg/max = 34.2/34.8/46.4
ip3 : xmt/rcv/%loss = 1196/1169/2%, min/avg/max = 34.0/36.6/48.8
^Cip1 : xmt/rcv/%loss = 2432/2432/0%, min/avg/max = 0.16/0.30/13.0
ip2 : xmt/rcv/%loss = 2432/2404/1%, min/avg/max = 34.2/34.8/46.4
ip3 : xmt/rcv/%loss = 2432/2387/1%, min/avg/max = 34.0/36.5/49.2

Should also have the -b option (number of bytes per ping), -I (ping using interface), -S (source ip address), -R (random bytes), -H (ttl), -c (number of pings per target to send)
fping can replace ping altogether. Except it doesn't have flood ping.

Doesn't traceroute give the same effect as your example?

Howdy normis.
No it doesn't because the vast majority of times I would not be pinging IPs that aren't along a route, but rather multiple IPs otherwise related:
1 - Multiple VPN end points
2 - Multiple external IP addresses belonging to branches
3 - Key ip addresses that assess overall Internet health (one USA IP, a couple domestic IPs belonging to a few different transit backbones, ...)
But the way to present the information is great for the non aggregated view.
If that functionality could be re-used to ping multiple IPs it would handle a lot of cases.