Skip to content
SpillFlareOil spills · Gas flares
Explore NigeriaOil spillsGas flaresPlacesData & methodsAbout
SearchLatest dataHelp
SpillFlare

Clear, source-backed public access to Nigeria's oil spill and gas flare records.

ExploreOil spillsSpill analyticsGas flaresHistorical company flaringPlaces
UnderstandData & methodsAboutHelp
Open access · Nigeria onlyData belongs to the cited public sources.Copyright © 2026 Dairus
Transparency

Data, definitions & methods

What the product reads, what it calculates, what it does not claim and how missing values are handled.

16/16 source endpoints healthy at snapshotRetrieved: 3 Sept 2026

The two core datasets

Oil spill records come from the NOSDRA Oil Spill Monitor. The two published spill URLs return the same dataset in the captured snapshot, so records are deduplicated rather than counted twice.

Gas flare values and geographic layers come from the Nigeria Gas Flare Tracker. State, LGA, cluster, block, company and onshore/offshore aggregations are presented independently.

Time means two different things

Observation date is the incident date or flare month in a source row. Retrieval date is when this product fetched the endpoint. A successful fetch today does not make an older observation current.

Missing values

A missing spill quantity is displayed as “not supplied,” because the exact quantity cannot always be ascertained. It is never converted to zero.

For gas flaring, a covered state or LGA with no row in a successfully retrieved period is described as “no flaring detected by the tracker for this period.” This wording fits both non-producing areas and areas where the tracker did not detect flaring; it does not make a broader geological claim.

Offshore locations

Coordinates outside Nigeria's land boundary can still be valid offshore incidents or flare sites. The map is designed to show the adjacent Gulf of Guinea rather than rejecting such records.

Block name matching

The flare time series and polygon layer sometimes use different names. A historical prospecting licence may later become a mining lease, while polygons may use lettered subdivisions or field names. We show verified lineage, but do not pretend those labels define identical boundaries. Unconfirmed joins are labelled location not matched.

Company history

Company flare data is included through October 2020—the final supplied month. It remains useful historically, but is never presented as a current company ranking.

Population layer

Where shown, the label is estimated population living within 2 km of flare locations and the value is reproduced from the tracker layer. The product does not convert it into an “affected population” estimate.

What this product does not do

  • No predictive model, risk score or AI-generated environmental conclusion.
  • No penalties, emissions conversions or health-impact calculations without a verified source and method.
  • No authentication, private workspaces or user-uploaded evidence.

Source health snapshot

SourceStatusRows/featuresLatest observationEndpoint
spillsPrimaryhealthy21,161Aug 2026Open
spillsMirrorhealthy21,161Aug 2026Open
flareStatehealthy1,333May 2026Open
flareLgahealthy6,683May 2026Open
flareClusterhealthy21,662May 2026Open
flareBlockhealthy10,118May 2026Open
flareOnshoreOffshorehealthy342May 2026Open
Snapshot fallback: If a live source temporarily fails, the product can keep serving the last validated snapshot and marks the source as degraded rather than silently returning an empty dataset.
flareCompanyhealthy2,479Oct 2020Open
geoStateshealthy37Geographic layerOpen
geoLgashealthy774Geographic layerOpen
geoBlockshealthy287Geographic layerOpen
geoClustershealthy260Geographic layerOpen
geoOnshoreOffshorehealthy2Geographic layerOpen
geoLocationshealthy203Geographic layerOpen
geoPopulationhealthy119Geographic layerOpen
geoOilfieldshealthy397Geographic layerOpen