209.197.123.153 Down

Replies are listed 'Best First'.
Re: 209.197.123.153 Down by Bod (Parson) on Jan 23, 2024 at 23:19 UTC
I have just tried pinging 209.197.123.153 and it seems to be down for me too... However, https://www.perlmonks.org and https://perlmonks.org (the URL I usually use) are both working fine for me.	[reply]
Re: 209.197.123.153 Down by jo37 (Deacon) on Jan 23, 2024 at 20:09 UTC
Same behaviour for me. Greetings, -jo `$gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$`	[reply]
Re: 209.197.123.153 Down - pm-monitor.pl by Discipulus (Canon) on Jan 24, 2024 at 13:31 UTC
The same here, a crude attempt the get rust out of my brain Read more... (5 kB) that gives for this thread: perl pm-mon01.pl -t 3 -n 11157192 -c 2 -s 1 Wed Jan 24 14:29:24 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 209.197.123.153 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl?node_id=11157192 + 200 OK 22.5518 Kb (23093 bytes) in 2.349543 seconds 9.5984 Kb/s perlmonks.org @ https://216.92.34.251/index.pl?node_id=11157192 + 200 OK 22.5518 Kb (23093 bytes) in 2.314545 seconds 9.7435 Kb/s perlmonks.org @ https://209.197.123.153/index.pl?node_id=11157192 + 500 Can't connect to 209.197.123.153:443 took 3.025284 seconds (tim +eout 3 seconds) -------------------------------------------------------------------- Wed Jan 24 14:29:31 2024 checking perlmonks.org at 66.39.54.27 216.92. +34.251 209.197.123.153 -------------------------------------------------------------------- perlmonks.org @ https://66.39.54.27/index.pl?node_id=11157192 + 200 OK 22.1104 Kb (22641 bytes) in 2.834606 seconds 7.8001 Kb/s perlmonks.org @ https://216.92.34.251/index.pl?node_id=11157192 + 200 OK 22.0928 Kb (22623 bytes) in 2.9505 seconds 7.4878 Kb/s perlmonks.org @ https://209.197.123.153/index.pl?node_id=11157192 + 500 Can't connect to 209.197.123.153:443 took 3.027898 seconds (tim +eout 3 seconds) [download] L* There are no rules, there are no thumbs.. Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.	[reply] [d/l] [select]
Re: 209.197.123.153 Down by pryrt (Abbot) on Jan 29, 2024 at 14:20 UTC
I realized this morning that I hadn't been seeing timeouts anymore, so I checked: I see that the offending server is no longer in the list of IP from the nameserver. Thank the gods for getting that sorted out. $ dig perlmonks.org @ns1.us.bitnames.com ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9 <<>> perlmonks.org @n +s1.us.bitnames.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27062 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;perlmonks.org. IN A ;; ANSWER SECTION: perlmonks.org. 7200 IN A 216.92.34.251 perlmonks.org. 7200 IN A 66.39.54.27 ;; Query time: 21 msec ;; SERVER: 178.128.191.122#53(178.128.191.122) ;; WHEN: Mon Jan 29 07:12:41 MST 2024 ;; MSG SIZE rcvd: 74 [download]	[reply] [d/l]
Re^2: 209.197.123.153 Down by LanX (Saint) on Jan 29, 2024 at 15:33 UTC
Unfortunately it's still slow and buggy. Probably because of timeouts Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]
Re: 209.197.123.153 Down by kcott (Archbishop) on Jan 24, 2024 at 14:56 UTC
About 18 hours after your OP ... I logged into `www.perlmonks.org` (my usual URL) without any problems; no discernible slowness apparent. I ran a `ping` on that and arbitrarily killed it (Ctrl-C) midway through the 10th packet (causing received packet loss). $ ping www.perlmonks.org PING perlmonks.org (216.92.34.251): 56 data bytes 64 bytes from 216.92.34.251: icmp_seq=0 ttl=53 time=212.209 ms 64 bytes from 216.92.34.251: icmp_seq=1 ttl=53 time=212.273 ms 64 bytes from 216.92.34.251: icmp_seq=2 ttl=53 time=212.477 ms 64 bytes from 216.92.34.251: icmp_seq=3 ttl=53 time=212.021 ms 64 bytes from 216.92.34.251: icmp_seq=4 ttl=53 time=211.900 ms 64 bytes from 216.92.34.251: icmp_seq=5 ttl=53 time=212.400 ms 64 bytes from 216.92.34.251: icmp_seq=6 ttl=53 time=212.252 ms 64 bytes from 216.92.34.251: icmp_seq=7 ttl=53 time=212.024 ms 64 bytes from 216.92.34.251: icmp_seq=8 ttl=53 time=211.775 ms --- perlmonks.org ping statistics --- 10 packets transmitted, 9 packets received, 10% packet loss round-trip min/avg/max/stddev = 211.775/212.148/212.477/0.220 ms [download] `209.197.123.153` still down: `$ ping 209.197.123.153 PING 209.197.123.153 (209.197.123.153): 56 data bytes --- 209.197.123.153 ping statistics --- 34 packets transmitted, 0 packets received, 100% packet loss` [download] `66.39.54.27` seems fine, as you noted: $ ping 66.39.54.27 PING 66.39.54.27 (66.39.54.27): 56 data bytes 64 bytes from 66.39.54.27: icmp_seq=0 ttl=53 time=212.172 ms 64 bytes from 66.39.54.27: icmp_seq=1 ttl=53 time=212.808 ms 64 bytes from 66.39.54.27: icmp_seq=2 ttl=53 time=212.115 ms 64 bytes from 66.39.54.27: icmp_seq=3 ttl=53 time=211.972 ms 64 bytes from 66.39.54.27: icmp_seq=4 ttl=53 time=212.381 ms 64 bytes from 66.39.54.27: icmp_seq=5 ttl=53 time=214.007 ms 64 bytes from 66.39.54.27: icmp_seq=6 ttl=53 time=213.073 ms --- 66.39.54.27 ping statistics --- 7 packets transmitted, 7 packets received, 0% packet loss round-trip min/avg/max/stddev = 211.972/212.647/214.007/0.665 ms [download] Again, killed this with Ctrl-C but with better timing in this instance. — Ken	[reply] [d/l] [select]
Re^2: 209.197.123.153 Down by hippo (Bishop) on Jan 24, 2024 at 15:01 UTC
I ran a ping on that and arbitrarily killed it (Ctrl-C) midway through the 10th packet (causing received packet loss). Most (all?) variants of `ping` take the `-c` flag which lets you specify in advance how many packets to send. Adjust the value to suit your own patience level. eg: $ ping -n -c 5 66.39.54.27 PING 66.39.54.27 (66.39.54.27) 56(84) bytes of data. 64 bytes from 66.39.54.27: icmp_seq=1 ttl=57 time=92.0 ms 64 bytes from 66.39.54.27: icmp_seq=2 ttl=57 time=92.5 ms 64 bytes from 66.39.54.27: icmp_seq=3 ttl=57 time=92.8 ms 64 bytes from 66.39.54.27: icmp_seq=4 ttl=57 time=91.5 ms 64 bytes from 66.39.54.27: icmp_seq=5 ttl=57 time=91.8 ms --- 66.39.54.27 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 91.522/92.123/92.783/0.465 ms $ [download] 🦛	[reply] [d/l] [select]
Re^3: 209.197.123.153 Down by kcott (Archbishop) on Jan 24, 2024 at 15:18 UTC
++ Thanks. I was aware that such a flag existed but couldn't remember what it was. At 2am I was too lazy to type `man ping` for what was intended as a quick check. As is often the case, this short-cut became a long-cut: typing an explanation for Ctrl-C turned out to be more work. `😳` — Ken	[reply] [d/l]
Re: 209.197.123.153 Down by Anonymous Monk on Jan 24, 2024 at 21:50 UTC
Cannot reach here from, in USA, Spectrum cable connection with Windows 10 host or via AT&T cellular connection (LTE) with iOS 15; but can via T-Mobile cellular connection (�5G�) with iOS 17: https:// hachyderm.io/@anubhav/111812684247994095 (got �Tough beans�, so URL is now non-clicky).	[reply]
Re^2: 209.197.123.153 Down by Anonymous Monk on Jan 25, 2024 at 20:31 UTC
The situation persists. Oh well🤷😒	[reply]
Re^3: 209.197.123.153 Down by marto (Cardinal) on Jan 26, 2024 at 08:29 UTC
Indeed, .com works from here .org doesn't.	[reply]
Re^4: 209.197.123.153 Down by LanX (Saint) on Jan 26, 2024 at 13:38 UTC
Re^5: 209.197.123.153 Down by choroba (Cardinal) on Jan 26, 2024 at 13:44 UTC
Some notes below your chosen depth have not been shown here
Re^3: 209.197.123.153 Down by Anonymous Monk on Jan 31, 2024 at 09:51 UTC
I can now access the website normally (from Windows over Spectrum network).	[reply]


Perl Monk, Perl Meditation
	PerlMonks