Pibor fire, 4 January 2026 Pibor
The fire started on 4 January 2026 in Pibor, South Sudan, and satellites saw it burning for 11 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,077 hectares from heat detections, spread across a single municipality.
It is the 298th largest in Jonglei since 2016 (of 427 with a page). Number 124 in South Sudan in 2026, of 182.
The power measured by the satellite is low (22.5 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 6,077ha
- GWIS perimeter (Copernicus)
- Duration
- 11days
- 4 Jan 2026 – 14 Jan 2026
- Municipalities hit
- 1
- counties
- Started on
- 4 Jan
- 2026
- Heat detections
- 157
- in a single hotspot: 23 MW
- Danger at start
- 34
- High · FWI index
- Energy released
- 900MW
- sum of detected power
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 11 days without rain (1 mm or more) when it started.
This area had burned before
91% of the perimeter overlaps earlier fires recorded since 2016: 1,894 ha in 2016, 1,886 ha in 2018, 510 ha in 2019, 119 ha in 2020, 2,193 ha in 2021, 1,053 ha in 2022, 4,243 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 5,500 ha that had burned before.
What happened to each town
-
Pibor where it started6,118 ha reached on 4 Jan0.2 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre 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) |
|---|---|---|---|---|---|
| 4 Jan | 36.7 °C | 20 % | 17 km/h | 0.0 mm | High 34 |
| 5 Jan | 36.4 °C | 23 % | 19 km/h | 0.0 mm | High 36 |
| 6 Jan | 36.8 °C | 19 % | 34 km/h | 0.0 mm | Very high 42 |
| 7 Jan | 37.6 °C | 19 % | 32 km/h | 0.0 mm | Very high 41 |
| 8 Jan | 37.1 °C | 22 % | 17 km/h | 0.0 mm | High 38 |
| 9 Jan | 37.3 °C | 20 % | 39 km/h | 0.0 mm | Very high 48 |
| 10 Jan | 36.2 °C | 20 % | 20 km/h | 0.0 mm | Very high 38 |
| 11 Jan | 36.6 °C | 24 % | 24 km/h | 0.0 mm | High 38 |
| 12 Jan | 36.7 °C | 24 % | 18 km/h | 0.0 mm | Very high 39 |
| 13 Jan | 37.3 °C | 22 % | 32 km/h | 0.0 mm | Very high 43 |
| 14 Jan | 36.0 °C | 23 % | 28 km/h | 0.0 mm | Very high 41 |
| 15 Jan after | 36.0 °C | 22 % | 25 km/h | 0.0 mm | Very high 41 |
| 16 Jan after | 34.9 °C | 23 % | 24 km/h | 0.0 mm | Very high 42 |
| 17 Jan after | 36.7 °C | 20 % | 22 km/h | 0.0 mm | Very high 43 |
| 18 Jan after | 37.1 °C | 25 % | 25 km/h | 0.0 mm | Very high 40 |
| 19 Jan after | 36.7 °C | 23 % | 29 km/h | 0.0 mm | Very high 43 |
| 20 Jan after | 37.7 °C | 29 % | 24 km/h | 0.1 mm | High 37 |
| 21 Jan after | 38.8 °C | 24 % | 43 km/h | 0.0 mm | Extreme 50 |
| 22 Jan after | 38.9 °C | 19 % | 41 km/h | 0.0 mm | Extreme 51 |
| 23 Jan after | 38.1 °C | 19 % | 34 km/h | 0.0 mm | Very high 47 |
| 24 Jan after | 39.6 °C | 19 % | 44 km/h | 0.0 mm | Extreme 54 |
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 11 January 2026 the air beside the fire reached 94 µg/m³ of PM2.5. That day averaged 61: 4.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 · 157Every 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 Pibor fire last?
- GWIS (Copernicus) dates it between 4 January 2026 and 14 January 2026: 11 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 6,077 hectares (60.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Pibor (6,118 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 37.6 °C, humidity dropped to 19 % and gusts hit 39 km/h. The fire danger index (FWI) reached 48, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of South Sudan (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.
Satellite cross-check
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
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.