Gogo fire, January 2026 Gogo, Téhini
The fire started on 17 January 2026 in Gogo, Côte d’Ivoire, and satellites saw it burning for 16 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,619 hectares from heat detections, spread across 2 municipalities.
It is the 99th largest in Zanzan since 2016 (of 774 with a page). Number 12 in Côte d’Ivoire in 2026, of 136.
Compare with…
Suggestions: Djigouè · 2024Ouô · 2025Ouô · 2026Loropéni · 2024
- Burnt area
- 3,619ha
- GWIS perimeter (Copernicus)
- Duration
- 16days
- 17 Jan 2026 – 1 Feb 2026
- Municipalities hit
- 2
- sub-prefectures
- Started on
- 17 Jan
- 2026
- Heat detections
- 55
- in a single hotspot: 33 MW
- Danger at start
- 41
- Very high · FWI index
- Average daily power
- 36MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 33 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Gogo where it started1,867 ha reached on 19 Jan2.7 %
-
975 ha reached on 22 Jan1.0 %
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.
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) |
|---|---|---|---|---|---|
| 17 Jan | 33.8 °C | 17 % | 30 km/h | 0.0 mm | Very high 41 |
| 18 Jan | 35.3 °C | 14 % | 26 km/h | 0.0 mm | Very high 40 |
| 19 Jan | 34.7 °C | 18 % | 17 km/h | 0.0 mm | Very high 39 |
| 20 Jan | 33.4 °C | 18 % | 30 km/h | 0.0 mm | Very high 43 |
| 21 Jan | 32.3 °C | 22 % | 34 km/h | 0.0 mm | Very high 44 |
| 22 Jan | 32.3 °C | 16 % | 34 km/h | 0.0 mm | Very high 44 |
| 23 Jan | 32.5 °C | 14 % | 36 km/h | 0.0 mm | Very high 44 |
| 24 Jan | 34.6 °C | 12 % | 28 km/h | 0.0 mm | Very high 43 |
| 25 Jan | 34.0 °C | 9 % | 43 km/h | 0.0 mm | Extreme 55 |
| 26 Jan | 34.2 °C | 12 % | 40 km/h | 0.0 mm | Extreme 54 |
| 27 Jan | 34.9 °C | 11 % | 34 km/h | 0.0 mm | Extreme 51 |
| 28 Jan | 35.5 °C | 10 % | 33 km/h | 0.0 mm | Very high 50 |
| 29 Jan | 35.1 °C | 9 % | 28 km/h | 0.0 mm | Very high 48 |
| 30 Jan | 36.5 °C | 11 % | 26 km/h | 0.0 mm | Very high 47 |
| 31 Jan | 36.6 °C | 13 % | 25 km/h | 0.0 mm | Very high 47 |
| 1 Feb | 36.3 °C | 20 % | 23 km/h | 0.0 mm | Very high 42 |
| 2 Feb after | 36.9 °C | 21 % | 24 km/h | 0.0 mm | Very high 43 |
| 3 Feb after | 31.1 °C | 36 % | 26 km/h | 0.0 mm | High 34 |
| 4 Feb after | 36.3 °C | 22 % | 26 km/h | 0.0 mm | High 37 |
| 5 Feb after | 37.5 °C | 13 % | 34 km/h | 0.0 mm | Very high 48 |
| 6 Feb after | 36.9 °C | 15 % | 20 km/h | 0.0 mm | Very high 44 |
| 7 Feb after | 36.6 °C | 19 % | 25 km/h | 0.0 mm | Very high 45 |
| 8 Feb after | 37.0 °C | 13 % | 21 km/h | 0.0 mm | Very high 44 |
| 9 Feb after | 37.0 °C | 14 % | 24 km/h | 0.0 mm | Very high 47 |
| 10 Feb after | 35.1 °C | 17 % | 24 km/h | 0.0 mm | Very high 46 |
| 11 Feb after | 35.6 °C | 25 % | 28 km/h | 0.0 mm | Very high 43 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · CopernicusOn 28 January 2026 the air beside the fire reached 52 µg/m³ of PM2.5. That day averaged 47: 3.1 times the WHO daily guideline (15).
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 · 55Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Gogo fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 17 January 2026 to 1 February 2026 (16 days). The perimeter dates it from 22 January 2026 to 1 February 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 3,619 hectares (36.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Gogo (1,867 ha, 2.7 %); Téhini (975 ha, 1.0 %).
- What was the weather like?
- During the fire the temperature reached 36.6 °C, humidity dropped to 9 % and gusts hit 43 km/h. The fire danger index (FWI) reached 55, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Côte d’Ivoire (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: 180 · 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.
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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 22 January 2026 to 1 February 2026. 55 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.
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 ADM3 (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.