Internet Archive getting blocked by plusnet.

[#1]

Drat. It's back to :

"Hmm. We’re having trouble finding that site"

.... This evening.

It isn't as though I'm not reaching there...

Pinging archive.org [207.241.224.2] with 32 bytes of data:
Reply from 207.241.224.2: bytes=32 time=140ms TTL=46
Reply from 207.241.224.2: bytes=32 time=139ms TTL=46
Reply from 207.241.224.2: bytes=32 time=139ms TTL=46
Reply from 207.241.224.2: bytes=32 time=138ms TTL=46

Ping statistics for 207.241.224.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 138ms, Maximum = 140ms, Average = 139ms

[#2]

That error in your web browser might indicate that you are using Firefox.

If so, what are the settings for DNS resolution? Tools -> Settings -> Privacy and security. Then HTTPS-only mode and DNS over HTTPS

[#3]

My settings are -

Don’t enable HTTPS-Only Mode

DNS over HTTPS: off

[#4]

Dear Grumble: Thanks for taking an interest.

My setting is Firefox are mostly the same as yours except "Enable DNS over HTTPS using:".
I will try it "off" but for the following reasons I don't think that is the problem.

Archive.org is back available this morning without having to change anything.

When I can't get a response using Firefox, I can't get it using MS Edge either.

I can still resolve the IP when I ping, which suggests DNS is working

I was using Plusnet's DNS but I changed that to 8.8.8.8 to see if that helped, and it didn't

An additional data point, when Plusnet will not bring me archive.org and it "times out", my mobile data provider can on my phone, so I doubt that it is archive.org is generally busy, but I do wonder whether their service provider takes umbrage with incoming plusnet traffic at times? 

[#5]

For Info : No problem here. Win 10 & Edge browser. Plusnet connection using Plusnet's DNS settings.

Router is a Netgear D6400

Forgot to add IP address is 212.159.18.nnn

[#6]

Hi All

Still somewhat temperamental. I can get in one minute (uploading some files), then I cannot get in to test they have uploaded successfully! And then I can!! Everything was fine until last Sunday when I noticed it was going wrong. What has changed? The Windows update (Windows 11, version 25H2)?? This is beyond my technical ability so I would appreciate some help. Thanks

[#7]

I have "Get the latest updates as soon as they are available" disabled in WinUpdate (Win11). Sometimes stuff gets released a bit too early? I've been "bitten" by that feature when operating Win10.

[#8]

Doesn't explain why my work computer (working from home) can't get access from home, but can when on the company network.

Internet Archive is struggling again this evening

[#9]

Site access may be iffy, have a read here : https://downdetector.com/status/internetarchive/ 

[#10]

It still seems to be problem and I know since it was hacked site reliability seems to have been through the floor. It was working fine yesterday afternoon, and now this morning 6.29 on both opera, firefox on my pc and laptop no longer connectable. Its the full internet archive site I use to search for books. I use the wayback machine as well. On Firefox using max protection for dns over https. I think it was set to that years ago and there was never a problem. I changed my dns from google which has been ultra reliable to open dns, who are really reliable. I can't see it being that. I think its just the site. 

Bob.

[#11]

Well I tested on several phones in the house. Cant get to it from there. I think must be the site itself. Reliability is right down. It is odd for a web scale property. I thought it might have been that  AWS bug, but I'm sure it was flaky long before that. 

Bob

[#12]

I've ran an overnight ping test against archive.org, success=3426 Failed=10. Whatever is replying to the ping has a 99.71%  success rate which must be acceptable.

[#13]

"nich7503" Has a very good point. Same computer, different location & ISP, different result.

I happened to be around at 4am this morning and Plusnet (via WiFi) on my IPad was timing out - but when I switched it to using my mobile phone as a hotspot, there was a successful connection to archive.org

I also read down detector as "Champnet" has, but how many of those people reporting have tried a different internet connection?

It could yet be archive.org I suppose, where incoming traffic is dealt with differently depending on originating IP?

Champnet did what I did with Ping and I also get a positive result even when archive.org will not serve me any actual webpages.