Very intermittent server responses

[gnickoloff]

Sometimes it works as expected, most times it does not.

Troubleshooting:

`$ curl -v wttr.in

• Trying 5.9.243.187:80...
• Connected to wttr.in (5.9.243.187) port 80 (#0)
• GET / HTTP/1.1
• Host: wttr.in
• User-Agent: curl/7.88.1
• Accept: /
• Empty reply from server
• Closing connection 0
  curl: (52) Empty reply from server`

[sergiorgiraldo]

still down
https://downforeveryoneorjustme.com/wttr.in

[chubin]

It should work now; please verify.

The issue is that the current architecture cannot manage the volume of traffic
we are experiencing at the moment, leading to these instability problems.

I am truly sorry for this.

I am completely rewriting it from scratch right now, and I hope to roll out the
entirely new version soon. If my calculations are accurate, it will handle at
least ten times more traffic than we currently have, without any noticeable
performance degradation.

Once again, I apologize for the inconvenience caused by the service
instability, and I sincerely hope we will find a definitive solution to the
issue soon.

[Cougar16]

It should work now; please verify.

The issue is that the current architecture cannot manage the volume of traffic we are experiencing at the moment, leading to these instability problems.

I am truly sorry for this.

I am completely rewriting it from scratch right now, and I hope to roll out the entirely new version soon. If my calculations are accurate, it will handle at least ten times more traffic than we currently have, without any noticeable performance degradation.

Once again, I apologize for the inconvenience caused by the service instability, and I sincerely hope we will find a definitive solution to the issue soon.

Thank you so much for your time ! we appreciate that

[gnickoloff]

It should work now; please verify.

Once again, I apologize for the inconvenience caused by the service instability, and I sincerely hope we will find a definitive solution to the issue soon.

It seems to be working at the moment.

Thank you. I appreciate your effort.

[delaosa]

Currently down

[Cougar16]

It should work now; please verify.

Once again, I apologize for the inconvenience caused by the service instability, and I sincerely hope we will find a definitive solution to the issue soon.

It seems to be working at the moment.

Thank you. I appreciate your effort.

Down again

[grous0]

It should work now; please verify.

The issue is that the current architecture cannot manage the volume of traffic we are experiencing at the moment, leading to these instability problems.

I am truly sorry for this.

I am completely rewriting it from scratch right now, and I hope to roll out the entirely new version soon. If my calculations are accurate, it will handle at least ten times more traffic than we currently have, without any noticeable performance degradation.

Once again, I apologize for the inconvenience caused by the service instability, and I sincerely hope we will find a definitive solution to the issue soon.

So this is a code problem rather than infrastructure? If so, is the new codebase private, can i/we help somehow?

[arteily]

Any news? Miss wttr.in very much.

[chubin]

I tried to avoid this until the very last moment, but I believe that, under the current circumstances, it is the best solution until the new server with the improved architecture is rolled out:

wttr.in now automatically blocks the most active clients (top-N, where N dynamically changes depending on the load).

There’s no need to worry for legitimate and moderate users; this really only affects those who make hundreds of hits per second. (I’m not entirely sure why they do this, especially when they are querying the same location repeatedly.)

Anyway, the updated service will likely be able to handle even such highly active clients. :) For now, however, they will be automatically blocked. So, please check your scripts and ensure that you do not issue more than a dozen requests per second.

[stefexec]

My script is fine, I even cache in /tmp/, something must be borked?

[Anagastes]

I now seem to be blocked as well, and my script was last set to query every 6 hours.

Is there any way I can send you an IP address (perhaps via private message)? I don't rule out the possibility that I wasn't moderate enough.

But I tested it again from a different IP address and it's still not accessible. 🥹🫣

[JanGamesHD]

The script we use here accesses wttr.in every 15 minutes.
In the morning it seems like its working perfectly fine, but going into noon & afternoon, requests seem to time out (CET time zone)

About a week ago, everything was still working OK (normal typical response time)
Same thing is happening with other external IPs as well

[bytech-ca]

I'm hitting wttr.in manually from command line, and do so a couple times every few days. Today I tried a few times, with each getting a curl: (52) Empty reply from server. Thank you for the excellent service, hope this helps, and looking forward to using it again in the future.