Wunderground crocked?

[watsonm]

Overnight it seemed to take one of my postings every hour according to today's weather direction page. CMX is configured for every 5 minutes!

[water01]

Yes mine seems to be the same so they have partially fixed it. Should be updating every 5 minutes but currently 30 mins and counting.

[watsonm]

What I find puzzling is that a couple of "local to me" stations seem to be working fine!!!

[water01]

Looks like it is intermittent, just got a MX alarm about uploads to it and it is now saying again I am offline!!

[AndyKF650]

Yes I noticed that other stations in Jersey appear to be working online but have random timing issues.

[Nottub]

It's a pity that WU Support Announcements don't include as standard a date, or date and time for each of the announcements.

That way we could at least tie the incident with any upload errors.

Martyn

[HansR]

Tbh... I've had it with WU. I switched it off.

[Nottub]

Looks like we’re up and running again.

Martyn

[AndyKF650]

Yes, from 3pm my site is uploading every 15mins as requested. Looks like their IT support only works 9 to 5 weekdays so a breakdown mid morning on a saturday causes us a problem. The support message has changed to the following:

Alert
Weather Station Partial Outage
angle
Status: Current
We are experiencing an issue with weather station uploads, starting on January 21, 2023. UPDATE: Jan 23, 2023, 3:04 pm UTC -- system has recovered on our end. Reboot your station and you should start seeing data flowing through within 1 hour.

[ConligWX]

Alert
Weather Station Partial Outage
angle
Status: Current
We are experiencing an issue with weather station uploads, starting on January 21, 2023. UPDATE: Jan 23, 2023, 3:04 pm UTC -- system has recovered on our end. Reboot your station and you should start seeing data flowing through within 1 hour.

they forgot to add - "Until the next time"

[GlueGuy2]

We've been experiencing upload issues since Saturday January 21. That day, we kept getting 502, 503, & 504 errors. Starting Sunday, we started getting errors like this in the log file:

Code: Select all

2023-01-24 07:52:00.591 Wunderground: URL = http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCALAHON9&PASSWORD=********&dateutc=2023-01-24+15%3A52%3A00&winddir=15&windspeedmph=5.0&windgustmph=8.0&windspdmph_avg2m=5.0&winddir_avg2m=15&humidity=54&tempf=46.3&rainin=0.00&dailyrainin=0.00&baromin=30.334&dewptf=30.5&softwaretype=Cumulus%20v3.14.0&action=updateraw

2023-01-24 07:52:00.593 Wunderground: ERROR - No such host is known

I've submitted three trouble reports, and get a nice "we're working on it" type of automated reply, but so far, no joy in Mudville.

[GlueGuy2]

The solution is to use your API key and not your password. Having done that my data is now uploading.

is that different from the "Key" shown on the landing page? I've been using the "Key" in place of the password for as long as I can remember.

[SamiS]

2023-01-24 07:52:00.593 Wunderground: ERROR - No such host is known

I've submitted three trouble reports, and get a nice "we're working on it" type of automated reply, but so far, no joy in Mudville.

The error suggests that your computer or dns server can’t resolve ip address of weatherstation.wunderground.com. This can be caused by a malfunctioning router on your own network if it works as a dns server for clients, or the issue can also be on your service provider’s upstream server. You could try to configure your system to use some public dns like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1 to get around the problem.

If the issue would be on wunderground’s servers, then it would affect all users, so not very likely to get help from their support.

—
Sami

[GlueGuy2]

2023-01-24 07:52:00.593 Wunderground: ERROR - No such host is known

I've submitted three trouble reports, and get a nice "we're working on it" type of automated reply, but so far, no joy in Mudville.

The error suggests that your computer or dns server can’t resolve ip address of weatherstation.wunderground.com. This can be caused by a malfunctioning router on your own network if it works as a dns server for clients, or the issue can also be on your service provider’s upstream server. You could try to configure your system to use some public dns like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1 to get around the problem.

If the issue would be on wunderground’s servers, then it would affect all users, so not very likely to get help from their support.

—
Sami

DNS is working as far as I can tell. We use 8.8.8.8 as a tertiary DNS server, and when I lookup wunderground.com or weatherstation.wunderground.com, I get what looks like a normal response (both of those URLs go to the AWS cloud BTW).

[GlueGuy2]

I did a little more looking, and I am getting kind of strange results WRT the URL. See these results from ping and nslookup:

Code: Select all

>ping weatherstation.wunderground.com

Pinging a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com [34.232.250.77] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 34.232.250.77:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>nslookup
Default Server:  dns.google
Address:  8.8.8.8

> weatherstation.wunderground.com
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com
Addresses:  52.22.134.222
          54.159.105.134
          34.232.250.77
Aliases:  weatherstation.wunderground.com
          rtupdate.wunderground.com
          pws-ingest-use1-01.sun.weather.com

I don't know how to interpret those results.