I have no idea what the "time" field is. That appears to be some sort of nonstandard crap. Linux perhaps? They fill their userland with bug-riddled reinvented crap.
It's saying that it sent 7 packets and it received 7 packets. If the RTT min is 209ms and the RTT max is 211ms, then it looks like return traffic is happening expeditiously.
My best guess would be that this is saying that the command ran for 44 seconds, but that could potentially include things like name resolution time. Did the command actually run for 44 seconds?
Yes, the "time" field is the run time of the command, and it is actually taking over 40s to return 7 results.
Certainly weird, ping from my Windows client returns normal results but on Ubuntu desktop:
If I do ping jira.ixsystems.com - I get the slow results above, if I ping the exact IP that the name resolves to (as per what the ping command itself is telling me), the results are normal, all the metrics are the same except for the time to get each response is much less.
I've only tested a half dozen other names to ping but nothing else is behaving this way.
DNS lookup doesn't take that long - clearing caches and running again makes no difference to how long this is taking.
Can't think of what could be causing this very specific issue that I've never seen before and only seems to be affecting a site/name which has had known recent problems. Perhaps it is simply some odd behaviour of the ping implementation.