WXforum.net
Web Weather => Weather Website PHP/AJAX scripting => Topic started by: daneast on January 01, 2019, 08:26:22 AM
-
I'm getting 502 Bad Gateway when attempting to access anything at api.weather.gov.
I'm not sure if this was because of changes set to take affect Jan 1 with the API, or because of the partial government shutdown. It appeared to start at exactly 04:00 EST, so it has been down for 4.5 hours now.
When I pull up a community at forecast.weather.gov all the forecast data appears to be there as normal, so this looks like purely an API related thing (IE they are still making forecasts).
Anyone know what is going on?
-
Seems to be consistently giving 502s. I sent a tweet to my local office - they are usually pretty responsive. If / when I hear back I'll let you know.
-
Just getting this.
Sorry.. the forecast for Valentine is not available at this time.
NWS server https://api.weather.gov/zones/JSON-LD/NEZ005/forecast has an error.
Getting BAD GATEWAY
-
Looks like both are now working and server back up....This version is working.........$Version = 'advforecast-json.php (multi) - V5.00 (beta)- 21-Jan-2017';
This version will not get the 502 error...$Version = 'advforecast2.php (JSON) - V5.09 - 26-May-2018';
-
It's working for me now as well. Came back up just after 8:55 EST time. So it was down from 04:00 - 08:55 EST.
The timing with it being a new year, and the partial government shutdown was interesting. I have a hunch it was some kind of year rollover bug. It happened at 01:00 GMT.
-
I am getting this 502 Bad Gateway error at https://api.weather.gov/zones/forecast/MIZ018/forecast (https://api.weather.gov/zones/forecast/MIZ018/forecast). Friom the history on this thread, it seems to be a recurring thing.
Anyone else getting this for the NWS forecasts currently?
Greg H.
-
Never mind. As soon as I posted this, I tried again and it was working. Figures....
Greg H.
-
I was about to ask the same question, Greg. Mine just started working again as well.
-
It's intermittent, and still happening for me. Some calls fail, others are processed.
The NWS had a major outage a couple weeks ago. Cooling systems went out at a data center in CO, and HTTP errors started happening intermittently as their capacity to handle volume decreased. Eventually the new API went down completely. Apparently their fallover systems did not work correctly to transfer processing to other centers. Then the new API didn't come back online like it should. Any existing weather alerts that occurred during the outage were not in the API data when it came back online. Only new alerts from that point forward came through.
So they have some serious deficiencies for sure in their redundancy and ability to handle outages at key data centers. I'm not sure what these current failures are about.
-
Appears to have almost completely gone down again. Timeouts, 502 errors....
They do know about it.
-
Just noticed my forecast from NWS down as well. Thanks for posting the info that y’all have come across so far.
-
Same here. Changing to other version didn't help for long.
-
Both old/new are back for my area. I noticed the issues earlier this morning.. I think it was due to back-end data porting from the models to the database for the API. Sadly, those issues seem to continue happening with the NWS servers.
-
Mail thread I have says they've moved the API services from College Park to Boulder (if I'm reading it right) and they are testing a fix there, but I'm still getting a slew of 502 errors as of a few minutes ago.
-
Latest from where I'm at: Still seeing a lot of timeouts and stale data. No 502 errors anymore though.
One case that had me banging my head on the desk for a while... My site is showing stale data but if I fetch the URL from my browser, it's current. Tracked it down to different DNS resolutions for api.weather.gov - so not all of the caches are in sync. Sigh.
I reported the latter problem.
-
Well, it's kinda a tortuous path from api.weather.gov to the Akamai services proxying the actual NWS services providing the data. Here's the dig traces
02/07/20 12:44:29 dig api.weather.gov @ 208.67.222.222
Dig api.weather.gov@208.67.222.222 ...
Non-authoritative answer
Recursive queries supported by this server
Query for api.weather.gov type=255 class=1
api.weather.gov CNAME (Canonical Name) sancert.weather.gov.edgekey.net <=== first redirect
02/07/20 12:44:43 dig sancert.weather.gov.edgekey.net @ 208.67.222.222
Dig sancert.weather.gov.edgekey.net@208.67.222.222 ...
Non-authoritative answer
Recursive queries supported by this server
Query for sancert.weather.gov.edgekey.net type=255 class=1
sancert.weather.gov.edgekey.net CNAME (Canonical Name) e278.dscg.akamaiedge.net <=== second redirect
02/07/20 12:44:55 dig e278.dscg.akamaiedge.net @ 208.67.222.222
Dig e278.dscg.akamaiedge.net@208.67.222.222 ...
Non-authoritative answer
Recursive queries supported by this server
Query for e278.dscg.akamaiedge.net type=255 class=1
e278.dscg.akamaiedge.net A (Address) 104.84.224.50 <=== ahh.. IP addresses at last
e278.dscg.akamaiedge.net AAAA (IPv6 Address) 2600:1406:1400:589:0:0:0:116
e278.dscg.akamaiedge.net AAAA (IPv6 Address) 2600:1406:1400:584:0:0:0:116
02/07/20 12:46:16 dig dscg.akamaiedge.net @ 208.67.222.222
Dig dscg.akamaiedge.net@208.67.222.222 ...
Non-authoritative answer
Recursive queries supported by this server
Query for dscg.akamaiedge.net type=255 class=1
dscg.akamaiedge.net SOA (Zone of Authority)
Primary NS: n0dscg.akamaiedge.net
Responsible person: hostmaster@akamai.com
serial:1581108097
refresh:1000s (160 minutes) <=== reasonably speedy timeouts so changes should be propagated fairly quickly.
retry:1000s (160 minutes)
expire:1000s (160 minutes)
minimum-ttl:1800s (30 minutes)
-
Via email this morning:
Due to a planned upgrade last week there were unintended consequences to the API and it was down for several days. We restored services to 100% yesterday. I'll request that if you are still seeing any issues to notify Tech Control, but at this point I'll close this specific ticket since we have restored services. We apologize for the inconvenience this caused.