LOOK>>> BigDave, Dire Straights, please help <<<<LOOK

[BigDave]

My Internet is FUBAR my friends, some websites load fast like normal, most others time out.
I've checked Windows, my router, my cables. I released my WAN lease and shut off my router
for three hours+ today. When I turned it back on, it was given the same WAN IP address, wtf!
From my Windows 10 desktop, it pings like this. Take a look, it's like nothing I've ever seen

Code:

C:\WINDOWS\system32>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=5ms TTL=58
Reply from 8.8.8.8: bytes=32 time=3ms TTL=58
Reply from 8.8.8.8: bytes=32 time=5ms TTL=58
Reply from 8.8.8.8: bytes=32 time=4ms TTL=58
Ping statistics for 8.8.8.8:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping 8.8.8.4
Pinging 8.8.8.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 8.8.8.4:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

C:\WINDOWS\system32>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.1:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping 74.40.74.40
Pinging 74.40.74.40 with 32 bytes of data:
Reply from 74.40.74.40: bytes=32 time=3ms TTL=249
Reply from 74.40.74.40: bytes=32 time=3ms TTL=249
Reply from 74.40.74.40: bytes=32 time=5ms TTL=249
Reply from 74.40.74.40: bytes=32 time=4ms TTL=249
Ping statistics for 74.40.74.40:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping 74.40.74.41
Pinging 74.40.74.41 with 32 bytes of data:
Reply from 74.40.74.41: bytes=32 time=39ms TTL=245
Reply from 74.40.74.41: bytes=32 time=39ms TTL=245
Reply from 74.40.74.41: bytes=32 time=38ms TTL=245
Reply from 74.40.74.41: bytes=32 time=40ms TTL=245
Ping statistics for 74.40.74.41:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping netflix.com
Pinging netflix.com [52.22.152.138] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 52.22.152.138:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

C:\WINDOWS\system32>ping google.com
Pinging google.com [216.58.194.142] with 32 bytes of data:
Reply from 216.58.194.142: bytes=32 time=6ms TTL=55
Reply from 216.58.194.142: bytes=32 time=7ms TTL=55
Reply from 216.58.194.142: bytes=32 time=7ms TTL=55
Reply from 216.58.194.142: bytes=32 time=6ms TTL=55
Ping statistics for 216.58.194.142:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping msn.com
Pinging msn.com [13.82.28.61] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 13.82.28.61:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>ping forums.freenas.org
Pinging forums.freenas.org [64.62.136.54] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 64.62.136.54:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>ping mlb.com
Pinging mlb.com [209.102.213.14] with 32 bytes of data:
Reply from 209.102.213.14: bytes=32 time=7ms TTL=242
Reply from 209.102.213.14: bytes=32 time=8ms TTL=242
Reply from 209.102.213.14: bytes=32 time=7ms TTL=242
Reply from 209.102.213.14: bytes=32 time=7ms TTL=242
Ping statistics for 209.102.213.14:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping nfl.com
Pinging nfl.com [104.89.69.34] with 32 bytes of data:
Reply from 104.89.69.34: bytes=32 time=29ms TTL=49
Reply from 104.89.69.34: bytes=32 time=29ms TTL=49
Reply from 104.89.69.34: bytes=32 time=30ms TTL=49
Reply from 104.89.69.34: bytes=32 time=28ms TTL=49
Ping statistics for 104.89.69.34:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping bestbuy.com
Pinging bestbuy.com [184.87.148.116] with 32 bytes of data:
Reply from 184.87.148.116: bytes=32 time=46ms TTL=54
Reply from 184.87.148.116: bytes=32 time=46ms TTL=54
Reply from 184.87.148.116: bytes=32 time=46ms TTL=54
Reply from 184.87.148.116: bytes=32 time=48ms TTL=54
Ping statistics for 184.87.148.116:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\WINDOWS\system32>ping dell.com
Pinging dell.com [143.166.147.101] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 143.166.147.101:
	Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

From the router (pfSense version 2.4.2-RELEASE-p1) I pinged the exact same IP addresses
and came up with matching results.

My sense is that there is a major issue outside my home, but can't confirm
this because I can't connect to any of the "service out" type websites.

The big thing is I can't watch Netflix! it's one of the sites that wont load
AND IT'S PISSIN' ME OFF!

Edit: from https://www.speakeasy.net/speedtest/

 

[nightshade00013]

I would guess your ISP is having an issue. But First thing I would do is remove the pfSense box and connect direct to just double check.

After that a phone call will generally tell you if something is going on. Not knowing you ISP we can't even attempt to check for you.

 

[BigDave]

But First thing I would do is remove the pfSense box and connect direct to just double check.

Can't do that, the pfSense box is THE router at my home.

Not knowing you ISP we can't even attempt to check for you.

Sorry!
Frontier Communications now, formerly Verizon FIOS, here's the story about the sell off.
arstechnica.com/ is one of the sites that works

 

[Jailer]

Had similar results a while back with a website I host. It was a DNS propagation issue that resolved itself after a couple days.

I'm on a local WISP for my internet connection. I've gotten used to frequent outages but usually it's all or nothing. Contact your ISP and have them investigate the issue.

 

[Jurgen Segaert]

Note that Google's DNS servers are 8.8.8.8 and 8.8.4.4.
The IP 8.8.8.4 that you were pinging is not a valid Google Public DNS Address. Was that a typo?

 

[JJT211]

Can't do that, the pfSense box is THE router at my home.

Connect your computer directly to your modem (you may need to power cycle modem to get an IP) and check it from there. This rules out any pfSense related issues and directly tests your internet connection from your ISP.

 

[jgreco]

Connect your computer directly to your modem (you may need to power cycle modem to get an IP) and check it from there. This rules out any pfSense related issues and directly tests your internet connection from your ISP.

This. Without confirmation that your upstream is working, you are left not understanding where to look for the problem. If it's upstream, you need to get on the horn with those guys. If it is in-house, that's a totally different matter.

 

[nightshade00013]

Yep, like I said. Just because the pfSense box is your router it doesn't mean you can't hook a single computer up directly. It removes any possible problems the router can possibly be creating. Just generally have to power off the modem and then power it back on with the computer connected so it can get an IP address as a lot of devices lock to the MAC they had connected to them without a power cycle.

If you are unable or unwilling to do this you may as well either wait or fork over cash for a diagnostic fee.

 

[BigDave]

If you are unable or unwilling to do this you may as well either wait or fork over cash for a diagnostic fee.

I have a third option...
Yell at the wife because she forgot to pay the bill...
I wasted a lot of time checking out all my stuff

A hearty thanks to all who attempted to help, I appreciate all of you.

Dave

 

[jgreco]

https://memegenerator.net/img/instances/500x/38331123/dont-feel-sheepish-baaaaaaahhhhhhhh.jpg

 

[nightshade00013]

Yell at the wife because she forgot to pay the bill...
I wasted a lot of time checking out all my stuff

This reminds me of working at a WISP years ago.... Long story short internet was not working, our equipment was just fine and I was able to log in from the office. Turns out the wife unplugged the router while gone for a weekend to "save money" on electricity. Guy called in multiple times over at least 6 hours and I had specifically asked about a router among other things. Seems he thought he was smarter than me and didn't need to bother with it. Ockham's razor at work...