Skip to content
worldfires
PE · Peru · →

Chumbivilcas fire, 24 September 2026 Chumbivilcas

Out · last detection 25 Sept 2026, 06:10 UTC

The fire started on 24 September 2026 in Chumbivilcas, Peru, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,056 hectares from heat detections, spread across a single municipality.

It is the 57th largest in Cusco since 2016 (of 60 with a page). Number 83 in Peru in 2026, of 90.

Compare with…
Burnt area
1,056ha
GWIS perimeter (Copernicus)
Duration
2days
24 Sept 2026 – 25 Sept 2026
Municipalities hit
1
provinces
Started on
24 Sept
2026
Heat detections
10
in a single hotspot: 32 MW
Danger at start
39
Very high · FWI index
Average daily power
68MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 24 Sept25 Sept
25 Sept 2026

How it evolved, day by day

24 Sept 2026 · 131 MW · 9 25 Sept 2026 · 5 MW · 1
24 Sept 25 Sept

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

21°high
60km/h · peak gust
10%lowest humidity

It had gone 5 days without rain (1 mm or more) when it started. Rain came after the fire: 6.9 mm on 29 Sept.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 0.7% of the area of London (11 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Chumbivilcas 7,200 inhabitants where it started
    1,062 ha reached on 24 Sept
    0.2 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

People and buildings inside the perimeter

GHSL 2025
Built-up area0.19 ha
Residents< 20

Inside the perimeter there were about 0.19 hectares of built-up land and almost nobody lived there (GHSL 2025, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

The weather day by day

ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.

Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

Day High Min. humidity Peak gust Rain Danger (FWI)
24 Sept 20.8 °C 10 % 60 km/h 0.0 mm Very high 39
25 Sept 20.5 °C 13 % 46 km/h 0.0 mm Very high 38
26 Sept after 20.6 °C 9 % 48 km/h 0.0 mm Very high 40
27 Sept after 16.0 °C 24 % 32 km/h 0.0 mm High 29
28 Sept after 16.6 °C 25 % 45 km/h 0.0 mm High 32
29 Sept after 14.5 °C 30 % 49 km/h 6.9 mm Very low 4

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 17 Sept 2026
After · 2 Oct 2026

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 28 September 2026 the air beside the fire reached 18 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak18 µg/m³
Days over the guideline0 days
PM1025 µg/m³
Optical depth0.35
22232425262728
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Detections table · 10Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Peru ›

Frequently asked questions

How long did the Chumbivilcas fire last?
GWIS (Copernicus) dates it between 24 September 2026 and 25 September 2026: 2 days between the first and last heat detection of the perimeter.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,056 hectares (10.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Chumbivilcas (1,062 ha, 0.2 %).
Is the Chumbivilcas fire still active?
No fire detections since 25 Sept 2026, 06:10 UTC. A lack of detections is not an official extinction.
What was the weather like?
During the fire the temperature reached 20.8 °C, humidity dropped to 10 % and gusts hit 60 km/h. The fire danger index (FWI) reached 39, class Very high.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Peru (geoBoundaries). It is not an official report.

Where to verify it

A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.

Emergency number: 116 · 105 · Emergency number and official warnings ›

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

No changes since 24 October 2026.

RSS Changes to this page

Does something look wrong on this page?

This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.

Report an error
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 116 · 105.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 10 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology ›

Where this data comes from

The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.