Frequently incorrect highs/lows, hourly data and daily summaries missing

  • 8
  • Problem
  • Updated 5 months ago
I'm frequently seeing two different issues:
1) Wildly incorrect high/low temperatures (i.e. high of 72, low of 11)
2) Missing hourly data and daily summary text

If I try the request again, the issue is corrected. This has been happening for the past 3 or 4 days, and I've also gotten a bunch of reports from my users about this.

Any ETA on a fix? Thanks!
Photo of Brian Mueller

Brian Mueller

  • 2 Posts
  • 0 Reply Likes

Posted 8 months ago

  • 8
Photo of Brian Mueller

Brian Mueller

  • 2 Posts
  • 0 Reply Likes
Any progress on this issue? Still getting reports of this happening from users.

With the weird high/low temperatures, it looks like the incorrect low temp is a result of the Celsius temperature being returned for the Fahrenheit data point.
(Edited)
Photo of Thomas Fuchs

Thomas Fuchs

  • 41 Posts
  • 9 Reply Likes
Already posted this in https://apicommunity.wunderground.com/weatherapi/topics/api-servers-sending-bogus-data but this seems to be the exactly same issue.

I also experience this issue regularly with several different forecast requests. Here are some examples

http://api.wunderground.com/api/API_KEY/conditions/forecast/q/17201.json
http://api.wunderground.com/api/API_KEY/conditions/forecast/q/46074.json

It's not bogus data or mixed up Celsius/Fahrenheit in my case, but the forecast data actually comes from January this year.
Photo of Murphy

Murphy

  • 25 Posts
  • 12 Reply Likes
I've been seeing this same thing for about a month on some of our digital displays. The data is from January 3rd of this year. I'm getting numerous calls every day about it. It'd be real nice if WU could get around to fixing this.
Photo of Paul

Paul

  • 13 Posts
  • 1 Reply Like
Fix it on your end.  Check the response forecast date, if it is today cache the response and display it.  If the date is not today, display the cache.  I ask for a 10 day forecast every hour and always display my cached value reducing the number of requests I make to wu and hiding their issue of returning January 3 data. The forecast is advertised as updating every 3 hours but this is not always true
Photo of Murphy

Murphy

  • 25 Posts
  • 12 Reply Likes
Thanks, Paul.  This seems like an effective work around.  
(Edited)
Photo of Thomas Fuchs

Thomas Fuchs

  • 41 Posts
  • 9 Reply Likes
A workaround like this is OK for now, but our clients expect the weather to be correct and update in the interval that was promised. Sadly i still got no reply from help@wunderground.com (which is unusual, it mostly took some days at max), and as usual also no reply in this forum.
Photo of Murphy

Murphy

  • 25 Posts
  • 12 Reply Likes
100% correct, Thomas. We are preparing to migrate to a new weather service provider. I have been all over the forums, sent an email and submitted a support ticket. No answer, or even acknowledgement they received my inquiry. 

From the API section of the site today:

"To improve our services and enhance our relationship with our users, we will no longer provide free weather API keys as part of our program."

A: They could improve relations by responding to email and support tickets, or by having someone respond to forum users.
B: I'm paying for my API key, so what's the excuse for it being broken for a month?
The world's most accurate, precise and trusted weather data? Not quite.
Photo of Tim Roche

Tim Roche, Official Rep

  • 328 Posts
  • 35 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.
Photo of Murphy

Murphy

  • 25 Posts
  • 12 Reply Likes
I saw it once this morning. We have about a hundred presentations running, so I'm not gonna check them all, but I'll look through some of the usual suspects and see if any are experiencing the glitch.
Photo of Murphy

Murphy

  • 25 Posts
  • 12 Reply Likes
Yep, got at least one more showing the glitch right now.

api.wunderground.com/api/xxxxxxxxxxxxxxxx/forecast10day/conditions/satellite/bestfct:1/q/40.338227,-82.7946053.json 

Or it was until a minute ago.  Sigh. Intermittent problems are the best.
(Edited)
Photo of Tim Roche

Tim Roche, Official Rep

  • 328 Posts
  • 35 Reply Likes
yes, i have not been able to capture the issue in my testing.  Still trying to pin it down
Photo of Paul

Paul

  • 13 Posts
  • 1 Reply Like
Mon 05/14/18 24 requests 11 errors 45.83%
Tue 05/15/18 24 requests 11 errors 45.83%
Wed 05/16/18 24 requests 10 errors 41.66%
Thu 05/17/18 24 requests 7  errors 29.16%
Fri 05/18/18 24 requests 12 errors 50%
Sat 05/19/18 24 requests 9  errors 37.5%
Sun 05/20/18 24 requests 8  errors 33.33%
 
Photo of Thomas Fuchs

Thomas Fuchs

  • 41 Posts
  • 9 Reply Likes
Our clients are still experiencing this issue with January data. It's very intermittent but still exists. Any update on this?
Photo of moater11

moater11

  • 49 Posts
  • 8 Reply Likes
Hi there, any progress on solving this critical issue? We are still facing "Jan 3rd error" on lots of queries. this is very serious!
Photo of dakjr

dakjr

  • 5 Posts
  • 0 Reply Likes
Finally realized that I'm in this boat, too.  I thought there was a coding problem in the way we were handling the API results... turns out, the raw data is bad.  Continues to happen even after the fix was reported a week ago.  Any updates?
Photo of Thomas Fuchs

Thomas Fuchs

  • 41 Posts
  • 9 Reply Likes
Since help@wunderground.com seems to be dead, I had partial success by forwarding this issue to the parent company of WU. TWCDigitalSupport@us.ibm.com is the contact i used. They replied pretty quickly and had me confirm that the issue was already fixed. Sadly we still experience the same issue, so it's not fixed completely yet. They're aware of it. I will post any news I receive in here.
Photo of Roberto

Roberto

  • 28 Posts
  • 3 Reply Likes
Same for me  help@wunderground.com  is dead, and no response about the huge latencies of the API since few days ? with a TTFB (time to first byte) of more than 3 à 10 seconds and a lot of connections that fails