We build credibility through transparency. This page tells you where our coverage is thin, what data lags, and when you should absolutely verify independently.
PeakScout aggregates data from third-party sources that update on their own schedules — from every 15 minutes (fires, road closures) to once per day (avalanche forecasts). We do not have sensors on any trail. During a rapid weather change, an avalanche event, or a road washout, our data can be outdated by the time you read it.
The single most reliable source for current trail and road conditions is the managing agency's direct line. USFS ranger stations, BLM field offices, NPS visitor centers, and county road departments often have information that never makes it into a public API. We cannot verify every data point independently.
PeakScout does not guarantee the accuracy of any data point. We aggregate from government sources and display what they give us. When those sources are wrong or outdated, the error propagates to PeakScout. We are not liable for decisions made based on PeakScout data.
PeakScout is optimized for the Mountain West. Coverage for Colorado and Montana is deepest. States like Washington, Oregon, Nevada, and New Mexico have more limited trail condition coverage. Outside the West, coverage drops significantly. The homepage covers all 50 states for basic information, but data completeness varies.
PeakScout does not have real-time sensors. Every data point on this platform has some lag between when the source updates and when it appears here. Here are the typical refresh rates by data type:
| Data type | Typical refresh | During active events |
|---|---|---|
| Wildfire perimeters | 15–30 min | 15 min; InciWeb faster |
| NWS alerts / warnings | 2–5 min | Real-time via NWS CAP |
| Road closures (CDOT/MDT) | 5–15 min | May lag during emergencies |
| Avalanche forecasts | 1–6 hours (daily AM) | Centers may update more often |
| Weather forecast | 1–2 hours (Open-Meteo) | NWS WFO grid 1–2x/day |
| Air quality (AQI) | 30–60 min | AirNow updates ~1hr; fires = faster |
| Campsite availability | 15–60 min (rec.gov) | No change during high demand |
| Trail community reports | User-submitted, variable | Reports older than 72h decay |
During fast-moving events — a new fire start, an avalanche, a flash flood — our data may lag the reality by more than our typical refresh window. If you see a fire on local news that is not yet on PeakScout, check InciWeb directly. Always cross-reference with official agency channels during active emergencies.
"Always verify with the managing agency before your trip" is not a legal disclaimer cop-out — it is the practical reality of outdoor recreation. Government agencies have the boots on the ground. We have their data feeds. Here is how to verify:
When you report an inaccurate data point, we investigate within 24 hours and correct within 48 hours for confirmed errors. Corrections propagate to the relevant trail cards, briefing page, and any active alerts immediately upon confirmation. We do not always proactively catch errors — our correction speed depends on reports from users like you.
To report an error: email support@polsia.app with the trail name, state, and what you observed. For safety-critical errors, put "URGENT" in the subject line.
When corrections are made, affected users who have subscribed to alerts for that trail or area are not automatically notified — the corrected data simply appears on the relevant page. Check back after reporting an error to see the fix.
PeakScout runs a nightly data source health scan. Degraded or broken sources are patched automatically and we are alerted to investigate manually. If a data source goes down, the relevant widget shows "Source unavailable" rather than stale data. Trust the freshness indicator on each widget — if it shows a stale/outdated badge, that data should not be used for trip decisions.
Some features on PeakScout are marked Experimental — this means they have higher uncertainty and may have edge cases where the output is incorrect or unexpected. Experimental features should not be your only source for trip decisions. All Experimental features are candidates for promotion to production-grade once we have sufficient real-world validation.
Current Experimental features on PeakScout (as of May 23, 2026):
If you encounter an incorrect Experimental output, report it to support@polsia.app. Your report helps us calibrate and promote features to production-grade.