One of Windy's DevOps guys
Due to on our partner's discontinuation of data provisioning we are receiving no radar data for Mainland China and some parts of India. We are working on fixing this issue, but we currently have no timeframe for its resolution.
We are very sorry for any inconvenience this is causing you.
Hi, as for ECMWF, the 1800Z forecast was imported pretty much on time. The 0000Z forecast is expected to be available at the standard time of about 8:00 UTC. As for the Australian radar, we will take a look, thanks for bringing it to our attention!
Instead of map layers, some users of our Maps Forecast API might see fallback tiles with "No Data" text on them. We have identified the source of the issue and are working on fixing it.
We are on the path to fetching Chinese radar data from another source. It should be done within at most a few days, hopefully it could be in the next 24 hours.
If you read the discussions here, radar "forecasting" is a very controversial feature. That's due to it not really being a forecast. Instead, it's just an extrapolation, where we take the current images from a radar, calculate the movement vectors of different features and show how the situation could look if the features kept moving in the same direction and at the same speed during the next hour.
However - it will not show new phenomena that could emerge and it assumes that they will not disappear. It's a feature that is really popular in some regions, where it is a good predictor of rain or thunderstorms which are coming in the next hour. However, in other regions, with different geography, it can be less useful. For example, it's good for people who live in a single spot and know how storms tend to behave as they approach from different directions. However, without this local knowledge, you really cannot rely on it even within a 1h timeframe. A 3 hour radar extrapolation would basically be complete fiction.
We have switched our forecast serving to the functioning regions.
This should mitigate the issue for the majority of users, however, you may face increased loading times for the forecasts, as they are being served from USA and Asia, increasing the connection latencies.
Due to an outage on our provider's side, the data for Sea/Currents and Sea/Tidal Currents layers is outdated. We are currently serving data from June 13.
We are in contact with the provider to find out the reason why there is no new data available. We currently have no timeframe for resolution.
According to the information from our provider, the earliest time at which the issue could be fixed is 18:00 UTC today.
Due to on outage on our provider's side, satellite data from the GOESEAST and GOESWEST satellites, providing coverage over North and South America. We have no timefame for solution yet.
We are sorry for any inconvenience.
Hello, thanks a lot for letting us know! This was an issue related to some changes we were doing to routing requests from the API. The issue should now be fixed for all models globally. We're sorry for any inconvenience or delays this may have caused you.
Hello there! This is extremely weird - we don't use any Windy-wide blocking system where we could block your IP address. Furthermore, as far as I understand, Starlink addresses should be dynamic. Would you be able to let us know about the country you are accessing the system from and give us an example of your IP address, so that we can check internally?
Hello everyone, we are really sorry for the inconvenience you have faced. Our America-based users indeed had problems accessing the forecasts from models other than Meteoblue for the past few hours. It was due to an outage on our storage provider's side. While the problem is not yet fixed, we have redirected requests coming from America to other regions, so everything should work, albeit a little bit slower than you may be used to.
Due to on outage on our provider's side, satellite data from the GOESEAST and GOESWEST satellites, providing coverage over North and South America. We have no timefame for solution yet.
We are sorry for any inconvenience.
Hello, we are very sorry to hear this. We implement some limited workarounds for users who come from countries which suffer from internal and external restrictions. However, these are all on our side. If the app does not work for you, it already means they were ineffective.
We are very thankful to you for reporting this, since it's difficult for us to know if these workaround are working, due to the obvious problems we face trying to get a residential connection from Iran. At this point, I cannot recommend any way of accessing Windy from Iran apart from the filter blockers, etc. that you have described.
@dmbakker If you want to get air quality data for a specific location, I would recommend using our Point Forecast API and just fetching the data directly.
Hi, thanks for letting us know about this. Would you be able to tell us a bit more information please? It would be great to know:
Hello there :) Accessing Windy.com programmatically is not exactly a use case we are focusing on. However, we do have some options for developers that could make it easier for you. Could you please tell me more about your use case? I might be able to suggest some ways that would be better for you.
Hello there! We're really glad that you like our app. If you go to app settings (click on the menu button on the bottom right side of the app and pick Settings in the top row), you will see an "Animation of wind" option. If you switch it from "Normal" to "High," a set of sliders will appear. You can customize the size and contrast of the particles there.
Hi, we're sorry for the inconvenience, the issue should be fixed now.
Hi, we're sorry for the inconvenience, the issue should be fixed now.