KeystoneMeeker, Rio Blanco, Colorado | 2026

Retained report · Exact WFIGS/NIFC source record · More reports in Colorado

View fire map Official resources
Share & export
Export reports CSV
Share

At a glance

The last saved WFIGS/NIFC record for Keystone in Meeker, Rio Blanco, Colorado reports 3,042 acres and 100% containment.

Reported area3,042acres / 1,231.1 hectares
Reported containment100%
Discovery dateJul 21, 2026Reported discovery, not verified ignition time
Reported locationMeeker, Rio Blanco, ColoradoAgency location record
100%

Containment does not tell you whether the fire is out.

Agency record updated
Retrieved by WildfireSignal

Recent saved changes

  1. Left the observed source feedSaved observations: Nov 16, 2026, 8:52 AM ET → Nov 16, 2026, 11:15 AM ET
    Latest agency update: Nov 2, 2026, 10:49 AM ET

Observed source changes do not establish ignition or extinguishment. Reported acreage can be revised after mapping corrections. View saved report history →

Keystone map

The fire pin and blue ring mark this incident's reported point. They are not a fire boundary or evacuation zone.

Colorado overview →
Filters
Time Window
Heat Intensity
Very strong>330 K
Strong300-330 K
Satellite heat Map layer loading…
Wildfire Overview
Current map view
Heat detections --
Very strong --
Last update --
Layers
Official fire Perimeter Strong heat Very strong
Reported incident locationSatellite heat, not attributed to this fireAgency perimeter when available via Layers

About Keystone

The agency recorded discovery on Jul 21, 2026, 1:22 PM ET. The reported cause is listed as "Natural".

The agency describes the location or incident as: “45 Miles NW from Meeker, CO”.

The available agency report lists 42 personnel. Jurisdiction is listed as BLM. Reported fire behavior: Minimal.

Discovery
Jul 21, 2026
Reported cause
Natural
Personnel
42
Agency
BLM

Source: facts and saved reports from WFIGS/NIFC agency records. Check the report date for the timing of these details. How we use this data.

Saved report history for Keystone

Saved WFIGS/NIFC observations show how the agency-reported area and containment have changed. WildfireSignal does not estimate values between reports.

Saved interval: 27h 42m
Reported areaNo reported change
ContainmentNo reported change

Reference lookback: 24 hours. Nearest available earlier report; this is not an exact rolling-window measurement.

Saved observations: Nov 15, 2026, 7:32 AM ET → Nov 16, 2026, 11:15 AM ET

Saved interval: 170h 44m
Reported areaNo reported change
ContainmentNo reported change

Reference lookback: 7 days. Nearest available earlier report; this is not an exact rolling-window measurement.

Saved observations: Nov 9, 2026, 8:31 AM ET → Nov 16, 2026, 11:15 AM ET

First saved by WildfireSignalNov 4, 2026, 5:49 PM ET
Latest meaningful saved changeNov 16, 2026, 11:15 AM ET

Since the previous saved report

Reported areaNo reported changeCompared with reports saved Nov 16, 8:52 AM ET and Nov 16, 11:15 AM ET
Reported containmentNo reported changeCompared with reports saved Nov 16, 8:52 AM ET and Nov 16, 11:15 AM ET

These figures compare agency reports saved at different times; they are not a measured spread rate. Acreage can change after mapping corrections, and unchanged values do not mean conditions on the ground are unchanged.

Seven-day report progression

One latest saved observation is shown for each day with history available.

Recent daily saved reports for Keystone
DateReported acresContainmentAgency updated
Nov 16, 2026 ET3,042100%
Nov 15, 2026 ET3,042100%
Nov 14, 2026 ET3,042100%
Nov 13, 2026 ET3,042100%
Nov 12, 2026 ET3,042100%
Nov 11, 2026 ET3,042100%
Nov 10, 2026 ET3,042100%
View all saved agency reports (48)

WildfireSignal begins saving agency reports when it first observes a fire. Up to 48 recent observations are kept for 35 days. A compact incident identity and latest sourced summary are retained for up to five years so stable citations can outlast the detailed snapshot window; earlier detailed reports are not reconstructed.

Observed report snapshots for Keystone
Saved by WildfireSignalAgency record updatedReported acresContainmentFeed presence
3,042100%Not in observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed
3,042100%In observed feed

Fire details

Reported location
Meeker, Rio Blanco, Colorado
Discovery
Reported cause
Natural
Personnel reported
42
Primary fuel / fuel model
Brush (2 feet)
Secondary fuel / fuel model
Timber (Litter and Understory)
Reported fire behavior
Minimal
Behavior detail
Creeping
Behavior detail
Smoldering
Behavior detail
Creeping
Jurisdictional agency
BLM
Management organization
Type 4 IC
Incident complexity
Type 3 Incident
Incident identifier
2026-COWRD-000957
Situation report date
Reported coordinates
40.2205, -108.1781

Optional facts appear only when present in the feed. Agency abbreviations and fuel-model labels are shown as reported, without guessing missing details.

Questions about Keystone

Where is Keystone?

The official incident record places it in Meeker, Rio Blanco, Colorado. The map pin is a reported location, not the full fire boundary.

How large is Keystone?

The retained record reports 3,042 acres (approximately 1,231.1 hectares). This is reported incident size, not a measurement of current flames, and agencies can revise it.

How contained is Keystone?

The retained record reports 100% containment. Containment describes control work intended to stop spread. It is not the percentage extinguished or an all-clear for nearby communities.

When was Keystone discovered?

The reported discovery date is Jul 21, 2026, 1:22 PM ET. Discovery time may differ from ignition time; elapsed time does not establish continuous burning.

Where should I check evacuation orders and road closures?

Use local emergency management, the sheriff or other law enforcement, and official fire-agency updates. WildfireSignal does not verify evacuation zones, open roads, or safe travel routes. The official-information section provides starting points; it does not establish that orders are present or absent.

Why can the map and the incident report differ?

Agency records, mapped perimeters and NASA satellite detections are updated on different schedules. Satellite heat near a fire is not automatically attributed to that incident. Older or unavailable data does not establish that an area is safe.

Source details & methodologyHow this page uses agency, satellite and map data

This page combines agency incident reporting with separate satellite and map layers. They can update at different times and answer different questions.

Agency report

WFIGS / NIFC

Use this for the reported fire name, acreage, containment, incident location and agency update time shown on this page.

Satellite observations

NASA FIRMS

Heat detections can show recent thermal activity, but they are not an official acreage or containment figure and are not automatically attributed to this incident.

Boundary context

Agency perimeter layer

When a perimeter is available in the map layers, it may have a different timestamp from the incident report. The fire pin itself is only a reported location.