My daughter is going frantic because she can’t get onto Facebook ::). It suddenly stopped connecting around 6 this evening, it was fine before.
Laptop is Linux, phones and tablet are android and we normally use Chrome. Have tried on Firefox and that won’t connect either. I’ve done the usual clear history/cache and still nothing. I’ve checked if there’s a problem with the site via a couple of Is it down sites, they say it’s running okay.
The page doesn’t open at all Mark. After about 30 seconds of just the little circle going round I get the following:
This web page is not available
Google Chrome could not load the web page because www.facebook.com took too long to respond. The website may be down or you may be experiencing issues with your Internet connection.
Check your Internet connection
Check any cables and reboot any routers, modems or other network devices you may be using.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a programme that is allowed to access the network, try removing it from the list and adding it again.
If you use a proxy server…
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don’t believe you should be using a proxy server: Go to the Chrome menu > Settings > + Show advanced settings > Change proxy settings… and make sure your configuration is set to “no proxy” or “direct.”
ping -c 5 18.104.22.168
PING 22.214.171.124 (126.96.36.199) 56(84) bytes of data.
64 bytes from 188.8.131.52: icmp_req=1 ttl=90 time=20.8 ms
64 bytes from 184.108.40.206: icmp_req=2 ttl=90 time=21.1 ms
64 bytes from 220.127.116.11: icmp_req=3 ttl=90 time=20.6 ms
64 bytes from 18.104.22.168: icmp_req=4 ttl=90 time=20.1 ms
64 bytes from 22.214.171.124: icmp_req=5 ttl=90 time=19.7 ms
— 126.96.36.199 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 19.786/20.528/21.120/0.513 ms
Nope that’s the very definition of a DNS issue … able to connect via IP but not via domain name means there’s a problem with name resolution
(in the browser it appears that it still attempts to resolve the IP to a domain name and fails)