Question "Page could not be loaded" Error Message when trying to access SB

[BoltSnap]

I keep getting the error message in the attached picture frequently when trying to access SB. I have no issues with accessing other pages on the internet when this issue comes up with SB. I get the error message on my laptop as well as my phone using different internet providers and different web browsers. Other websites are accessible on all other browsers and internet services I use.

This issue started to occur over the last few months but is now happening more often and for longer duration. It happens several times during the day.

NOTE: I have done reboots and shutdowns but problem still persists.

 

[rhwestfall]

Yep, and really l-o-n-g (if successful at all thread page loads). Many times I stop the load, refresh the page ("whats new"), and hope for the best...

Windows 10/Chrome is my most frequent use.

 

[BoltSnap]

Doesn't seem to be a problem on Android, but Windows 10/Chrome has been quite bad.

It happens on all platforms for me; Android, Windows/Chrome/FireFox/Edge and other secure browsers.

 

[rhwestfall]

the red blinking loading bar on the right side of the screen is becoming quite a commonplace thing.

I've got over 300 down on my ISP, and other sites/pages appear not impaired.

 

[BoltSnap]

I've got over 300 down on my ISP

What do you mean by "300 down"?

 

[tridacna]

I get it so often that I don’t fight with it. I just shut it down and restart. All platforms.

 

[BoltSnap]

I just shut it down and restart

Does the restart help and the issue disappears after the restart?

 

[Ghost95]

I get the same thing if I type scubaboard.com in the address bar but if i go a Google search that links to something on scubaboard, i can get right on and then go to the home page. Weird.

 

[tridacna]

Does the restart help and the issue disappears after the restart?

Yes. I shut the app down on my iPhone and restart; Ditto with a browser. Seems to be a memory/cache issue. Pure guess.

 

[Miyaru]

I'm looking into this one. Problem is caused on the server, not your webbrowser.