WeatherKit always returns 404 at specific lat/lon within US

We grid our service area with 6000 points across the US. There is 1 point in Missouri that fails forecast and anything historical (currentWeather, forecastHourly, and forecastDaily) with a 404 error:

latitude = 37.06089340391355
longitude = -93.00383141966712

This works:

latitude = 37.06089340391355
longitude = -93.006

This does NOT work:

latitude = 37.06089340391355
longitude = -93.005

Even though all of the other points seem to be working, I have lack in trust for this API for returning unexpected results.

Can someone please provide an explanation or resolution?

We are seeing a similar issue that started on January 2nd around 7:28 PM Central. We are getting a 404 back for forecast on a small amount of locations.

Experiencing the same here, started ~2 days ago

Thanks for reporting this. The engineering team is investigating the example locations you have provided.

Will we receive an update of the resolution here? How long will this take a resolve?

We are still receiving an error at this location. It has been well over a week. Will we receive a resolution here?

Is there a faster way to receive support here? This does not seem to be helpful.

It looks like the problem of certain locations not returning data has been fixed. I tried each of locations cited here

latitude = 37.06089340391355
longitude = -93.00383141966712

and

latitude = 37.06089340391355
longitude = -93.005

and I get a valid Weather response back from WeatherKit.

I am still seeing a 404 error for specific lat/long/dates. I made a separate post here

WeatherKit always returns 404 at specific lat/lon within US
 
 
Q