https://www.facebook.com/ should not be resolving to 62.24.155.2. It's not responding to ping requests for me either. That in itself is not 100% conclusive since ping requests can be ignored, but to my knowledge Facebook is not doing that.
For example, on the Mac I happen to be using at the moment:
john@iMac36 ~ % ping facebook.com
PING facebook.com (57.144.230.1): 56 data bytes
64 bytes from 57.144.230.1: icmp_seq=0 ttl=56 time=15.322 ms
64 bytes from 57.144.230.1: icmp_seq=1 ttl=56 time=19.512 ms
64 bytes from 57.144.230.1: icmp_seq=2 ttl=56 time=25.770 ms
64 bytes from 57.144.230.1: icmp_seq=3 ttl=56 time=19.164 ms
64 bytes from 57.144.230.1: icmp_seq=4 ttl=56 time=18.411 ms
^C
--- facebook.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 15.322/19.636/25.770/3.405 ms
john@iMac36 ~ %
Since 192.168.1.1 is almost certainly your router's address (perfectly ok, normally, since it simply forwards requests to your ISP rather than resolve them independently) the cause is certain to be some kind of DNS misconfiguration, either intentional or not.
There is no harm in temporarily changing it to a public DNS address such as 1.1.1.1 for troubleshooting purposes. If you are concerned anyway, you can create a new "network location" for that purpose. The previously selected networks settings will remain unchanged, so you can always revert back to them by selecting the previous "location".
Instructions: Manage network locations on Mac - Apple Support