From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM, NORMAL_HTTP_TO_IP,NUMERIC_HTTP_ADDR autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:5309:: with SMTP id n9mr12364495itb.11.1556356052473; Sat, 27 Apr 2019 02:07:32 -0700 (PDT) X-Received: by 2002:aca:b757:: with SMTP id h84mr9388902oif.78.1556356052123; Sat, 27 Apr 2019 02:07:32 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!b2no307451itd.0!news-out.google.com!w17ni267itb.0!nntp.google.com!136no307003itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 27 Apr 2019 02:07:31 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=93.41.2.250; posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99 NNTP-Posting-Host: 93.41.2.250 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: gnoga.com down? From: mockturtle Injection-Date: Sat, 27 Apr 2019 09:07:32 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader01.eternal-september.org comp.lang.ada:56195 Date: 2019-04-27T02:07:31-07:00 List-Id: It seems that gnoga.com is down, I am posting this here since maybe the maintainer is not aware of this. Since few days I am getting "connection timeout" when I try to connect, last time (several weeks ago) everything worked fine (same browser, PC, ...). I tried also with curl curl -H "Host: gnoga.org" http://50.192.131.236/ curl: (7) Failed to connect to 50.192.131.236 port 80: Connection timed out and also going very low-level with Ruby irb(main):001:0> require 'socket' => true irb(main):002:0> s=TCPSocket.new('50.192.131.236', 80) Errno::ETIMEDOUT: Connection timed out - connect(2) for "50.192.131.236" port 80 Therefore, it is not an issue of the specific browser nor, I guess, of the specific OS. I got the IP address 50.192.131.236 from nslookup and it is also the same address reported in an old post (February 2019, if I am right) Riccardo