Unknown location/Capacity limit reached — wttr.in will be back online at 0:00 UTC

[vzaliva]

From command lineL

$ curl -s 'wttr.in?format=3&m'
Unknown location; please try ~43.0833231,-73.8712155⏎      

[LaurentFough]

Thought I was the only one.
Even supplying the Airport code, or latlon coordinates, results in the same error.
It does return my actual latlon for the "please try ... " portion of the error msg, though

[chubin]

Fixed, please try again

[vzaliva]

seems to working for me now. Thanks

[LaurentFough]

Fixed, please try again

Fixed.
Cheers.

[e-alfred]

I am still getting this message:

curl -s 'wttr.in?format=3&m'
Unknown location; please try ~42.6545,15.64523

curl wttr.in
Follow @igor_chubin for wttr.in updates

[vzaliva]

yes, it re-appeared

[t89]

Having the same issue. Querying the coordinates doesn't work, also.

[ilbuonmarcio]

Same here unfortunately

[chubin]

Sorry guys it was down for a couple of hours two days ago again, but it should be working since that

[vzaliva]

working again

[t89]

Same error appearing again.

[chubin]

@t89 Thomas, thank you for the reporting.
It happens from time to time, but not too often (once a week, or a month, when the load is peaking). I work on stabilization of this part, and at some point the error should disappear completely

[jorge-barreto]

Hey @chubin

Sorry to comment on a closed issue, but I thought I should mention that the problem is happening again

Hope you are well!

[chubin]

@jorge-barreto Yes, we are experiencing an outage at the moment, many apologies. the service will be back online
in 10 hours.

[chubin]

It is fixed now

[t89]

It is fixed now

It's broken again. 😆

[chubin]

Yes, it happens from time to time, but I am working on this

[Gravifer]

Seems another outage?

[chubin]

Please try now

[Gravifer]

Working~ thx ;)

[abouteiller]

Again today, but probing with the location does work this time

[byteshiva]

failing out...

[WuerfelDev]

And again ^^
#638

[chubin]

Fixed; please test

[WuerfelDev]

working, thanks 👍

[Rergis]

...and again.

[chubin]

@Rergis It was a different problem, but it is fixed now. Please test it, and please execuse me for the inconvenience

[timothevs]

Hi, I set up fresh Monterey (macOS 12.0.1) on my new iMac.

curl https://wttr.in\?format\="%l:+%C+%t+(%f)+at+%T+%m\n"

leads to this error:-

Unknown location; please try ~<coordinates of my city>%

[chubin]

@timothevs I've just checked your command, and it works fine for me.

Let's try to debug it: what commands from the following list do work:

1. curl wttr.in
2. curl wttr.in/<Your-Location>
3. curl wttr.in/<Your-Location>?format=...

?

[timothevs]

@chubin , thanks for the quick follow up. VERY strange. Now the command curl https://wttr.in\?format\="%l:+%C+%t+(%f)+at+%T+%m\n" works as well, in addition to the three you mentioned.

[chubin]

Maybe it was a short outage of the data source; it happens from time to time, but not so often

[I-Pch]

I'm a bit sad this morning 😔 ...

I can only hope it will get better soon 😊 ...

[Gskartwii]

Oh, I wasn't aware 1M was the limit, I've been doing a request every minute for waybar, so 1.5K requests per day. Sorry about that, maybe I'm partially responsible! What would be a reasonable rate? And could this be helped with some caching?

[d4n13ls1104]

Having this issue this morning.

[br0ziliy]

doesn't work again...

[sssemil]

This issue is back.

[CheesyChocolate]

Oh, I wasn't aware 1M was the limit, I've been doing a request every minute for waybar, so 1.5K requests per day. Sorry about that, maybe I'm partially responsible! What would be a reasonable rate? And could this be helped with some caching?

I personally get weather information once every boot, store it in a txt file and use it in bar(get raw default data and get my needed data with tools like grep, sed, sort).if you want more accurate weather information, 3 times a day would be enough. believe me we can predict far more than 1 minute :p

[chubin]

@CheesyChocolate No, it is fine; we have some caching layers, so feel free to make more queries (as long as it is not 10 queries per second :)

[compuguy]

Looks like the service has hit the 1M requests limit again:

Sorry, we processed more than 1M requests today and we ran out of our datasource capacity.
We hope to solve the problem as soon as possible, so you can enjoy
your favourite weather service 24x365 even if it rains or snows.

[AkechiShiro]

Has the service hit again the 1M requests limit again ?

[abstrnoah]

Limit has been hit several days in a row. Should we reopen this issue / is this being handled by another issue of which I'm unaware? Can anything be done about this? I don't know exactly how wttr.in gets its data but is there anything that the community can do to increase the limit?