forecast10day returning wrong date | The WeatherAPI Community Customer Community

forecast10day api call returning forecast for 10 days starting date 3rd January, 2018 for some zipcodes on some days.

Dishi baruah

1 Post
0 Reply Likes
anxious

Posted 2 years ago

2 years ago

Masaru Kitajima

2 Posts
0 Reply Likes

I also have a similar problem. In my case, I use geolocations.

Comment

2 years ago

Dan

11 Posts
2 Reply Likes

I have been seeing this randomly for a while now, and just finally captured the bad data. I retrieve forecast data for several dozen communities and it occurs randomly - it doesn't seem to affect any specific zipcode more than others. It makes my service look rather pathetic posting totally bad forecast data. At least now I'm identifying the bad data and not using it, however I'm sure it still counts again the API usage limits (so I can't just retry immediately).

However, since I visited the forums to check on this issue, and found they are discontinuing this service in the near future, I don't guess there's any point in following up on this.

Comment

2 years ago

Murphy

25 Posts
12 Reply Likes

This is not the first or second thread I've seen on this topic. It's been happening for about a month for our users, and we are quite frustrated. Yesterday, I finally got through to a real person about this.
https://business.weather.com/contact
On the bottom of the page are a few different numbers to call for support. It's the parent company, but it's at least somewhere to start.

Comment

2 years ago

Tim Roche, Official Rep

337 Posts
44 Reply Likes

Hi Folks, sorry for the lack of response, we're are really small team and when we're working on trying to fix things, sometimes we can't respond. We made a fix yesterday that we hope resolved the Jan 3 issue. Please let us know if the issue continues.

Comment

2018-05-18T18:39:13+00:00

Dan

11 Posts
2 Reply Likes

This manifested at least 4 times this morning.

05-18-2018 06:34:01 EST
http://api.wunderground.com/api/XXX/hourly/q/28681.json

05-18-2018 06:58:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24983.json

05-18-2018 07:02:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24315.json

I can provide the JSON response if you want it.

2018-05-19T01:15:42+00:00

Nichcagey

14 Posts
0 Reply Likes

Like Dan, still seeing the issue.

2018-05-19T12:45:40+00:00

Dan

11 Posts
2 Reply Likes

It's still manifesting this morning. These all had the bad data.

05-19-2018 06:44:01 EST
http://api.wunderground.com/api/XXX/hourly/q/25523.json

05-19-2018 06:47:01 EST
http://api.wunderground.com/api/XXX/hourly/q/25601.json

05-19-2018 06:48:02 EST
http://api.wunderground.com/api/XXX/hourly/q/25130.json

05-19-2018 06:52:01 EST
http://api.wunderground.com/api/XXX/hourly/q/27017.json

I can provide JSON if you need it, but it's the "11:00 AM EST on January 03, 2018" issue.

This one was a 404, which I also see from time to time.
05-19-2018 08:30:02 EST
http://api.wunderground.com/api/XXX/hourly/q/24382.json

2 years ago

Tim Roche, Official Rep

337 Posts
44 Reply Likes

Hi all, I put in another fix for the cache servers today, and from my monitoring, it seems like the errors have stopped and I have not been able to pull an old forecast since the fix went in.

Please let me know if you continue to see errors.

Comment

2018-05-21T11:33:29+00:00

Dan

11 Posts
2 Reply Likes

Sorry, still manifesting this morning. Some forecasts are still from Jan 3, 2018.

05-21-2018 07:26:02 EST
http://api.wunderground.com/api/XXX/hourly/q/24112.json

05-21-2018 07:27:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24171.json

2018-05-22T12:25:56+00:00

Dan

11 Posts
2 Reply Likes

It is manifesting this morning too still.

05-22-2018 07:13:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24343.json

05-22-2018 07:23:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24226.json

05-22-2018 07:25:02 EST
http://api.wunderground.com/api/XXX/hourly/q/24266.json

2018-05-22T13:25:18+00:00

Murphy

25 Posts
12 Reply Likes

Still seeing it this morning.

Edit: To add to this, I've seen it in 3 locations today (I have only checked 5). However, when I do the API calls manually, I'm getting back accurate information. This may be due to a quick correction on WU's part to fix erroneous calls. However, I am still facing a bunch of places showing incorrect forecasts for an hour at a time, until the next API call. I really need this fixed.

(Edited)

2018-05-23T12:00:35+00:00

Dan

11 Posts
2 Reply Likes

Still manifesting.
05-23-2018 07:24:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24614.json

05-23-2018 07:30:01 EST
http://api.wunderground.com/api/XXX/hourly/q/24382.json

2 years ago

Dan

11 Posts
2 Reply Likes

I bet you have a CDN endpoint out there somewhere that didn't update and still has old content. Or perhaps a load balancer is directing to an out of date server instance. That would explain the random nature of this.

Comment

1 person likes this

2 years ago

Andrew Mackay

1 Post
0 Reply Likes

Hello, I came on the forums to report this problem and am 'happy' to see that I am not alone. It continues to be an issue for us to the point I am considering switching provider. I had to modify my application to check for 'January 3' forecasts and ignore if returned. I love WU so hope it gets resolved soon!

Comment

2 years ago

Dan

1 Post
0 Reply Likes

Hello, I continue to see this issue as well. Today I saw it returned for multiple locations. I re-ran my script to try and see if it had to do with the time I ran the script and so far it still returns incorrect values.

Comment

2 years ago

Dan

11 Posts
2 Reply Likes

Just pointing out that there hasn't been a morning yet without at least a few of these bad forecasts. It's interesting to me that it is so consistent. It's maybe 4-5 out of 70 forecast requests each morning, and just a handful of them randomly.

Also this morning one request resulted in a HTTP 500 Internal Server Error:
05-27-2018 07:22:01 EST
http://api.wunderground.com/api/XXX/forecast/q/24251.json

Comment

1 person likes this

2 years ago

jaclerigo

1 Post
0 Reply Likes

I have the exact same problem.
http://api.wunderground.com/api/xxx/geolookup/conditions/forecast/lang:BR/q/39.7569,-8.9039.xml

Comment

2 years ago

Murphy

25 Posts
12 Reply Likes

Still seeing this glitch. I believe there have been some patches, but I'm not seeing a big decrease in the number of returns in the number of bad forecasts.

Comment

2 years ago

Chris

1 Post
0 Reply Likes

Same issue here.

http://api.wunderground.com/api/xxx/forecast10day/q/zmw:00000.25.16362.json

Comment

2 years ago

Ambrose

3 Posts
0 Reply Likes

I am having the same issue too. I have a script that I load a CSV file and it returns some wrong data with date as: January 3rd 2018

Comment

2 years ago

Dev Tsmedia

2 Posts
0 Reply Likes

I'm also seeing this issue for some time now. It's very frustrating answering our users that see incorrect data.

Comment

2018-05-30T06:59:41+00:00

Ambrose

3 Posts
0 Reply Likes

What is the solution to it?

2018-05-31T23:04:19+00:00

James Mowal

4 Posts
0 Reply Likes

www.aerisweather.com Has been more than supportive in helping my switch from WU

(Edited)

2 years ago

Marco Tresch

2 Posts
0 Reply Likes

We''ve been getting reports from our users as well: affected locations seem to be distributed randomly, with data being returned for january 3rd as well (similar to what has been reported above, however we're using the /forecast endpoint, not /forecast10days).

An example of a location that has been affected by this: /forecast/q/54.1494679,12.17270100000018.json

Comment

2018-05-30T08:12:12+00:00

Marco Tresch

2 Posts
0 Reply Likes

Adding to the above, I've investigated further and can confirm that we have had this issue occur for thousands of different geo locations over the last 7 days

2 years ago

Dan

11 Posts
2 Reply Likes

I haven't seen any bad forecast data since June 6, 07:30 EST. So there's been a few days without any bad data now.

Comment

2018-06-11T00:19:41+00:00

Calsy

8 Posts
2 Reply Likes

I average about 30,000 requests per day, and this issue is still occurring over 100 times a day.

2018-06-11T18:20:59+00:00

Sabrina Ambler

1 Post
0 Reply Likes

At 11:13AM June 11, 2018 At least four cities with Jan 3rd info. Still a widespread issue. What service are they discontinuing per Dan 4weeks ago?

2018-06-11T23:41:12+00:00

Calsy

8 Posts
2 Reply Likes

He maybe referring to WU discontinuing free access to their API for people who provide weather data via a PWS.

1 year ago

Dan

11 Posts
2 Reply Likes

I haven't seen bad data since June 19, 2018.

Comment

1 year ago

Kris Persson

2 Posts
0 Reply Likes

I monitor and have setup my api collection application to report and discard the data and I still see it even today. It is ongoing, though I will either get it for one of my cities or all of my cities within a 60 second run, never just 2 or 3 always either 1 city or all of them.

Comment

2018-07-10T13:06:32+00:00

Tim Roche, Official Rep

337 Posts
44 Reply Likes

Can you send detailed information? Our monitoring indicates this problem has been 100% resolved.

2018-07-11T22:23:33+00:00

Kris Persson

2 Posts
0 Reply Likes

@Tim Roche, thank you, I have been waiting to respond to gather some detailed information but since I posted the above I can confirm I have not had a single incorrect forecast in my cities feeds. :-D Excellent Work to you and your team.