Source health.
Which feeds are working, and how fresh is the data?
Checks sample Minneapolis forecasts, Minnesota radar, 18 airports, road cameras and NOAA buoy feeds. Normal requests also update these results. This checks Carr Weather’s connections, not worldwide provider uptime.
No sweep has completed in this server process yet. Refreshes every minute while open; source caches still apply.
Checking weather data connections…
Airport reporting coverage 0 stations checked
Age is measured from the station observation, not the API request. NWS fallbacks are labeled separately.
| Airport | Report age | Source | Freshness |
|---|
How to read this dashboard
Working means usable data
Checks inspect the returned weather data, not just an HTTP status. A valid empty alert feed is working; an empty airport feed means reports are missing. A model’s native short forecast or an unsupported measurement is expected, not an outage.
Checks, data time, and caches
Last completed check changes only when the server actually tries the source. Reading a cache does not create a new success or faster provider latency. Check duration includes that source’s request chain and validation. Forecast valid times, model initialization, observation times and radar timestamps have different meanings and are labeled separately.
Setup and external services
WeatherNext 3 stays neutral until approved access is configured. Its health comes from normal forecast requests, never extra Google queries from this dashboard. MnDOT directory and sampled image delivery are checked separately; a successful JPEG does not establish capture time or every camera’s health. FAA, DNR and local provider viewers are external and are not automatically tested.
A current view, not a historical uptime report
Results and last-success records belong to this serving process and reset when it restarts. Other workers or hosts can have different results. No historical uptime percentage is claimed. The app’s deployment readiness check remains independent of weather providers.