Nigeria infrastructure, explained

A read-only public window into Nigeria’s infrastructure signals.

Infrastructure.civic.ng starts with verified Data Civic feeds, then turns those records into a public product that stays plain about what is known, what is missing, and where every number came from.

State pages wait for state-backed rows from Data Civic.0 of 4 sectors currently have state-backed data.No ingestion or storage duplicated here

Source layer status

Healthunavailable
Datasets0
Indicators0

Planned from source layer

Some upstream reads failed

The app still renders whatever Data Civic returned, but it will not fill gaps with guessed content. health: [data-civic] Request failed with status 403 for /api/health. datasets: [data-civic] Request failed with status 403 for /api/datasets. indicators: [data-civic] Request failed with status 403 for /api/indicators. power records: [data-civic] Request failed with status 403 for /api/records. mobile records: [data-civic] Request failed with status 403 for /api/records. internet records: [data-civic] Request failed with status 403 for /api/records. road length records: [data-civic] Request failed with status 403 for /api/records.

Access to electricityUnavailable

No live records

This MVP only reports verified records that are currently exposed by Data Civic.

Source: Data Civic public API

Mobile cellular subscriptionsUnavailable

No live records

This MVP only reports verified records that are currently exposed by Data Civic.

Source: Data Civic public API

Individuals using the InternetUnavailable

No live records

This MVP only reports verified records that are currently exposed by Data Civic.

Source: Data Civic public API

State pages live

0

Individual state pages now open directly from the returned roads comparison feed.

Sectors with state-backed data

0

Roads are the first live state-backed sector in this app.

National-only sectors

4

Power, telecom, and water remain public national summaries until upstream state rows exist.

National versus state visibility

The app explains infrastructure by separating national signals from real state-backed views.

Infrastructure.civic.ng only consumes Data Civic APIs. It does not create a second registry, a second database, or a second ingestion pipeline. National sector pages stay strict about country-level scope, while the new states surface activates only where verified state rows already exist.

State coverage by sector

What can be understood by state right now

This matrix is data-driven. It reflects only the sectors that returned verified state rows during the request and leaves the rest as national-only summaries.

Power

Power currently remains national-level only in infrastructure.civic.ng.

National-level only

Roads

Roads currently remains national-level only in infrastructure.civic.ng.

National-level only

Telecom

Telecom currently remains national-level only in infrastructure.civic.ng.

National-level only

Water

Water currently remains national-level only in infrastructure.civic.ng.

National-level only

Data limitations

  • The home page only reflects the category-filtered datasets, indicators, and verified infrastructure record filters returned by Data Civic during the request.
  • Water now has verified national records, while roads currently add one CivicNG-derived state-level estimate series; broader state-level coverage remains limited.
  • This app does not store, transform, or backfill infrastructure data locally. If the upstream feed changes, the rendered view changes with it.

Infrastructure datasets

Current upstream sources exposed by Data Civic

Planned from source layer

No infrastructure datasets returned

The home page will stay sparse until Data Civic returns infrastructure datasets again.

Infrastructure indicators

What the shared data layer says it can measure today

Planned from source layer

No infrastructure indicators returned

This view does not infer indicators from records. It waits for the category-filtered upstream indicator registry.