Skip to content
worldfires
SS · South Sudan · →

Pibor fire, 5 January 2026 Pibor

Out · last detection 9 Jan 2026, 11:11 UTC

The fire started on 5 January 2026 in Pibor, South Sudan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,269 hectares from heat detections, spread across a single municipality.

It is the 390th largest in Jonglei since 2016 (of 427 with a page). Number 161 in South Sudan in 2026, of 182.

Burnt area
5,269ha
GWIS perimeter (Copernicus)
Duration
4days
5 Jan 2026 – 8 Jan 2026
Municipalities hit
1
counties
Started on
5 Jan
2026
Heat detections
77
in a single hotspot: 220 MW
Danger at start
34
High · FWI index
Energy released
2.6GW
sum of detected power

Where it burned

9 Jan 2026
HOTSPOTS BY DAY 5 Jan8 Jan

How it evolved, day by day

56789

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

The weather it burned in

37°high
46km/h · peak gust
18%lowest humidity

It had gone 13 days without rain (1 mm or more) when it started.

This area had burned before

64% of the perimeter overlaps earlier fires recorded since 2016: 261 ha in 2016, 830 ha in 2018, 2,217 ha in 2019, 2,399 ha in 2020, 407 ha in 2022, 1,202 ha in 2024, 135 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 3,388 ha that had burned before.

What happened to each town

  1. Pibor where it started
    5,301 ha reached on 5 Jan
    0.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)
5 Jan 35.5 °C 27 % 23 km/h 0.0 mm High 34
6 Jan 37.3 °C 18 % 37 km/h 0.0 mm Very high 47
7 Jan 37.4 °C 20 % 46 km/h 0.0 mm Extreme 53
8 Jan 36.4 °C 24 % 20 km/h 0.0 mm Very high 40
9 Jan after 37.4 °C 19 % 37 km/h 0.0 mm Very high 48
10 Jan after 36.5 °C 19 % 36 km/h 0.0 mm Very high 50
11 Jan after 36.8 °C 25 % 34 km/h 0.0 mm Very high 46
12 Jan after 36.1 °C 26 % 21 km/h 0.0 mm Very high 38
13 Jan after 37.7 °C 21 % 38 km/h 0.0 mm Very high 48
14 Jan after 36.4 °C 21 % 36 km/h 0.0 mm Very high 46
15 Jan after 36.2 °C 23 % 26 km/h 0.0 mm Very high 41
16 Jan after 34.7 °C 24 % 28 km/h 0.0 mm Very high 42
17 Jan after 36.5 °C 20 % 22 km/h 0.0 mm Very high 40
18 Jan after 36.9 °C 27 % 26 km/h 0.0 mm Very high 41

Before and after, from space

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

Before · 29 Dec 2025
After · 15 Jan 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 11 January 2026 the air beside the fire reached 93 µg/m³ of PM2.5. That day averaged 54: 3.6 times the WHO daily guideline (15).

PM2.5 peak93 µg/m³
Days over the guideline9 days
PM1094 µg/m³
Optical depth0.78
34567891011
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 · 77Every 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 South Sudan ›

Frequently asked questions

How long did the Pibor fire last?
GWIS (Copernicus) dates it between 5 January 2026 and 8 January 2026: 4 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 5,269 hectares (52.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Pibor (5,301 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 37.4 °C, humidity dropped to 18 % and gusts hit 46 km/h. The fire danger index (FWI) reached 53, class Extreme.
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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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.