The reason for this is that Battlelog asks origin to ping the servers over Origins local API.
Origin then directly pings the IP of the game server and returns the ping to the open Battlelog browser tab (just some java script running in the background).
That's why Origin has to be running for the ping to show up.
Also, especially on campus networks and on other networks a firewall might block pinging.
Download the UOTrace program and on THIS page you can find complete tutorial how to trace EA servers. If you can not trace any of them turn off your windows firewall completely for a moment (private and public network) and start UOTrace and trace EA servers again, if you see servers (host names, IP`s pings...) and you will surely see them after the Firewall is turned off, then something is blocked in firewall and you must determine what is that.
You can also test your battlelog are the pings visible, but if UOTrace see EA servers, battlelog will show pings, dont forget to refresh battlelog page with CTRL-F5 (deleting cache only on that page).
Firewall can block a lot of things like origin, pbsvc, punkbuster, some paths... play with outbound rules to see what it is.
I just want to narrow range of problems, this is the only fix for missing ping in BF3 and BF4.
Good luck.
And I found it, in my case blocked prosess was - NT Kernel & System, and now I can see all pings as you can see in the image I provide. Same thing for BF3 and BF4.
