Statizoid Global 'Dead-End' Public API Health Check Ratio

🖧 Technology & Internet

Global 'Dead-End' Public API Health Check Ratio

The share of public APIs that fail basic health checks over time.

Observations
8
Tracking since
Last updated

Global 'Dead-End' Public API Health Check Ratio

The share of public APIs that fail basic health checks (HTTP HEAD returning 2xx within 5 seconds)

4 observations · measured in %

30.0%
Global 'Dead-End' Public API Health Check Ratio
▬ 0.0% vs previous
13 Aug 2026 07:00
Global 'Dead-End' Public API Health Check Ratio (%) — summary, last 30 days.
0.0%20.0%40.0%60.0%06:4206:5107:00Global 'Dead-End' Public API Health Check Ratio: 60.0% — 13 Aug 2026 06:42Global 'Dead-End' Public API Health Check Ratio: 60.0% — 13 Aug 2026 06:45Global 'Dead-End' Public API Health Check Ratio: 30.0% — 13 Aug 2026 06:52Global 'Dead-End' Public API Health Check Ratio: 30.0% — 13 Aug 2026 07:00
Global 'Dead-End' Public API Health Check Ratio (%) — line, last 30 days.
0.0%20.0%40.0%60.0%06:4206:5107:00Global 'Dead-End' Public API Health Check Ratio: 60.0% — 13 Aug 2026 06:42Global 'Dead-End' Public API Health Check Ratio: 60.0% — 13 Aug 2026 06:45Global 'Dead-End' Public API Health Check Ratio: 30.0% — 13 Aug 2026 06:52Global 'Dead-End' Public API Health Check Ratio: 30.0% — 13 Aug 2026 07:00
Global 'Dead-End' Public API Health Check Ratio (%) — area, last 30 days.
061218
13 Aug

Darker = higher global 'dead-end' public api health check ratio. Empty cells are hours with no collection.

Global 'Dead-End' Public API Health Check Ratio (%) — heatmap, last 30 days.
WhenGlobal 'Dead-End' Public API Health Check Ratio
30.0%
30.0%
60.0%
60.0%
Global 'Dead-End' Public API Health Check Ratio (%) — table, last 30 days.

Unhealthy Public API Endpoint Count

The number of public APIs that fail basic health checks (HTTP HEAD returning non-2xx or timeout within 5 seconds)

4 observations · measured in count

7 count
Unhealthy Public API Endpoint Count
▬ 0.0% vs previous
13 Aug 2026 07:00
Unhealthy Public API Endpoint Count (count) — summary, last 30 days.
23456706:4206:5107:00Unhealthy Public API Endpoint Count: 2 count — 13 Aug 2026 06:42Unhealthy Public API Endpoint Count: 2 count — 13 Aug 2026 06:45Unhealthy Public API Endpoint Count: 7 count — 13 Aug 2026 06:52Unhealthy Public API Endpoint Count: 7 count — 13 Aug 2026 07:00
Unhealthy Public API Endpoint Count (count) — line, last 30 days.
23456706:4206:5107:00Unhealthy Public API Endpoint Count: 2 count — 13 Aug 2026 06:42Unhealthy Public API Endpoint Count: 2 count — 13 Aug 2026 06:45Unhealthy Public API Endpoint Count: 7 count — 13 Aug 2026 06:52Unhealthy Public API Endpoint Count: 7 count — 13 Aug 2026 07:00
Unhealthy Public API Endpoint Count (count) — area, last 30 days.
061218
13 Aug

Darker = higher unhealthy public api endpoint count. Empty cells are hours with no collection.

Unhealthy Public API Endpoint Count (count) — heatmap, last 30 days.
WhenUnhealthy Public API Endpoint Count
7 count
7 count
2 count
2 count
Unhealthy Public API Endpoint Count (count) — table, last 30 days.

About this data

This page tracks the ratio of public APIs that respond to simple HTTP HEAD requests, exposing how many endpoints are effectively abandoned. The data comes from automated, repeated checks on a curated list of open endpoints—no private information is involved, just basic connectivity tests. The metric reveals systemic neglect in digital infrastructure, where documentation exists but operational health is ignored.

Sources

Every figure on this page was read from these pages.

Why this isn't published anywhere else

No live dashboard, recurring report, or public dataset tracks the specific 'Global Dead-End Public API Health Check Ratio' metric (ratio of public APIs failing HTTP HEAD requests over time). Broader API health tools exist but do not aggregate this global ratio.

Uniqueness score 1.00 — assessed against live web search results when this subject was created.