@rubensan112
I'm pretty sure that IP, 192.168.1.1, is very close to you.
Like 3 foot away, the cable between pfSense and your ISP router.
The idea is that you use another, public, IP, one that is further down "the road", a gateway IP of your ISP.
If that one is to hard to find, you could use some other "nearby" IP, like 8.8.8.8.
I'm using the IP of one of my servers somewhere nearby the main 'ISP gateway' :
ececd44b-0e5d-4945-99ec-7b2f9438d480-image.png
Now I see :
8f8df7d3-43ff-4671-90b1-f7a38245e45a-image.png
Which means :
192.168.10.1 is the IP of the LAN of my ISP router, just 30 away from me and pfSense.
188.165.5x.87 is my server IP, and that one is just to 'test' my uplink.
The whole ieda of all this is : If I (pfSense) can reach (receive answers to my pings) from 188.165.5x.87, I know (and pfSEse) that my connection is ok.
Pinging your upstream router on your site/home makes no sense. That says nothing about the 'quality' of your uplink.
Test this yourself : remove the cable (phone/adsl/coax/satellite disk/fiber/whatever you use) from your ISP router : you will see no alerts in the pfSense GUI dashboard, as your 1921.168.1.1 is still answering, so pfSense thinks the connection is ok.
Well, it's not.