Why does local power outage effect some websites but not others

[sofasurfer]

We had a power outage today from the big storms. Our power is back on now but many, many local areas are not back on. I am on line posting this and I am able to view an assortment of other sites. There are many other sites that I can not connect with. Since I am able to view some sites my server is obviously operating but then why are other sites not obtainable? Does this indicate that the questionable website are in areas that are having an outage also?
Just asking because I have never had this situation before. Its always been either the whole internet works or the whole internet does not work.

 

[osprey]

We had a power outage today from the big storms. Our power is back on now but many, many local areas are not back on. I am on line posting this and I am able to view an assortment of other sites. There are many other sites that I can not connect with. Since I am able to view some sites my server is obviously operating but then why are other sites not obtainable? Does this indicate that the questionable website are in areas that are having an outage also?
Just asking because I have never had this situation before. Its always been either the whole internet works or the whole internet does not work.

If you run traceroute to website hosts it may be possible to see where the stoppages are happening, if they are when tracing the pathway to the host. Here's an example tracing the route from a machine here to google:

[tom@min ~]$ traceroute www.google.com
traceroute to www.google.com (142.250.66.228), 30 hops max, 60 byte packets
 1  mymodem (192.168.0.1)  0.404 ms  0.289 ms  0.293 ms
 2  gateway.nb12.sydney.asp.telstra.net (58.162.26.76)  16.815 ms  16.822 ms  16.847 ms
 3  ae10.chw-ice301.sydney.telstra.net (203.50.61.65)  18.507 ms ae10.ken-ice301.sydney.telstra.net (203.50.61.81)  16.645 ms  16.658 ms
 4  bundle-ether25.stl-core30.sydney.telstra.net (203.50.61.64)  17.384 ms bundle-ether25.hay-core30.sydney.telstra.net (203.50.61.80)  19.602 ms  19.552 ms
 5  bundle-ether1.ken-edge903.sydney.telstra.net (203.50.11.173)  17.938 ms  18.035 ms  17.971 ms
 6  goo2503144.lnk.telstra.net (58.163.91.202)  36.520 ms goo2503069.lnk.telstra.net (58.163.91.194)  16.556 ms goo2503144.lnk.telstra.net (58.163.91.202)  17.497 ms
 7  192.178.98.27 (192.178.98.27)  16.755 ms 192.178.97.93 (192.178.97.93)  18.037 ms 192.178.97.87 (192.178.97.87)  18.457 ms
 8  142.250.224.191 (142.250.224.191)  17.360 ms  18.359 ms 142.250.224.189 (142.250.224.189)  18.489 ms
 9  syd15s15-in-f4.1e100.net (142.250.66.228)  18.614 ms  18.449 ms  18.574 ms

Then when checking the host, the result shows that it is in fact google:

[tom@min ~]$ whois 142.250.224.191
<snip>
NetRange:       142.250.0.0 - 142.251.255.255
CIDR:           142.250.0.0/15
NetName:        GOOGLE
<snip>

If traceroute can't get through, it should provide some sort of info, but I can't show it at the moment since my internet connection is working.

 

[sofasurfer]

www.thegatewaypundit.com works and content is up to date, however...

$ traceroute thegatewaypundit.com
traceroute to thegatewaypundit.com (172.67.41.88), 30 hops max, 60 byte packets
connect: Network is unreachable

Tried using ip address also...

$ traceroute 172.67.41.88
traceroute to 172.67.41.88 (172.67.41.88), 30 hops max, 60 byte packets
connect: Network is unreachable

I would guess that I am doing something wrong but googling
the error shows that many people have the same issue.

 

[osprey]

www.thegatewaypundit.com works and content is up to date, however...

$ traceroute thegatewaypundit.com
traceroute to thegatewaypundit.com (172.67.41.88), 30 hops max, 60 byte packets
connect: Network is unreachable

Tried using ip address also...

$ traceroute 172.67.41.88
traceroute to 172.67.41.88 (172.67.41.88), 30 hops max, 60 byte packets
connect: Network is unreachable

I would guess that I am doing something wrong but googling
the error shows that many people have the same issue.

That website you mentioned, thegatewaypundit, was reachable from here, as expected.

The message "Network is unreachable" often means that the configuration on the machine which reports it and/or the associated gateway/router is the problem. The next step that may be useful is to do a full rundown of the network configuration with whichever network managing tool you have. That would include the lot, connectivity with ping, dns, routing, gateway, dhcp/static addresses, firewall etc.

It may be of interest to check some stats with:

ip -s a

to see what the network is reporting in relation to packets moved, the errors, what's been dropped and missed, after both a failed connection, and a successful one.

 

[CaffeineAddict]

connect: Network is unreachable

Could also mean that this host is dropping or intentionally not responding to pings, so you can try with hping3 and do TCP or UDP test to confirm this.
The end result should be the same as visiting the site, meaning it's online but dropping pings.

 

[merrycorsten]

The debugger has a layer to swirl the rapid-spinner, of that classifies, to read the system in a block-motoric. The sense of using testing does a abortion in linking the ports rapidly with the session, as it overflows, the networking blocks the monitor to the coordinations, because it has a double-wired platform to link the session all over again.

 

[APTI]

The debugger has a layer to swirl the rapid-spinner, of that classifies, to read the system in a block-motoric. The sense of using testing does a abortion in linking the ports rapidly with the session, as it overflows, the networking blocks the monitor to the coordinations, because it has a double-wired platform to link the session all over again.

whatever you tried to say just hurt my head. Maybe try different translate software because what you used is pretty bad. It means nothing to me.
As for not getting some sites, I would think that your ISP has some things down due to power outage also. So the path to your web site or even the location of the website may be affected by the power outage. Contrary to popular belief, the internet can go down. or even partially down.

 

[Larrysmith09]

It seems like there could be multiple factors at play, from power outages affecting specific areas to potential routing issues or configurations on your local machine or network. As others have mentioned, running a traceroute or using tools like ping or hping3 can help identify where the problem lies. It might also be worth reaching out to your ISP to check if there are any ongoing issues on their end, especially following the recent storms. Sometimes, even after power is restored, network routes and services can take a bit longer to stabilize.