# Runtime is more than HTTP 200

KF01 · Descriptive case report · 2026-10-05

A status service returned valid JSON while three external sources were missing. The browser and worker paths told different stories.

## Question

What does a successful HTTP response establish about an AI status service’s actual function?

## Method

A retrospective single case based on retained delivery logs and a browser report. The case was selected because transport checks, source data and browser interaction were documented separately. Selection was retrospective rather than random.

The worker response was read for HTTP status, content type and the three service result fields. An earlier browser report was placed alongside it without merging the timestamps or execution paths.

## Results

At 09:18 UTC on 5 October, /api/status returned HTTP 200 and application/json. All three providers still had unavailable / unknown results with source_read_failed. The delivery log’s outer passed value therefore did not establish successful retrieval of all provider reports.

The separate 09:28 UTC snapshot still returned HTTP 200. All three providers now had fetch_redirect_rejected. These fields alone do not establish the cause.

The earlier browser report recorded at 00:06 UTC showed three available reports and a working native refresh. It concerns the browser’s public CORS fallback and does not verify the worker path checked later.

The local correction record documents a native fetch bridge, bounded failure categories and passing focused fixtures. Its handoff explicitly calls actual r2 provider retrieval unknown. A passing fixture remains separate from the real runtime.

## What others can put into practice.

Check useful payload content as well as HTTP status: expected, present, fresh and usable?

Retain failed responses and verify fallback paths individually. A browser fallback should not erase a failing server path from the record.

Write separate acceptance statements: transport works; source retrieval works; the interface displays the supported state.

## Limits

One service with several dated execution paths. No claim about AI systems in general, today’s provider status or the final worker failure cause. No physical phone coverage or revenue evidence.

## Sources

- status-r1: cloudflare-ai-delivery-r1.json; SHA-256 2ccbfd544bf553a8b40faf6c3cf422bb95853d7750d94b0bc464897f51339e20; https://ki-forschungsportal.pages.dev/data/status-r1.json
- status-r2: cloudflare-ai-delivery-r2.json; SHA-256 1cd64421a4e6484c1298a4620d4edf1b4bd6042ee947cfd3761fc680baf8b6c0; https://ki-forschungsportal.pages.dev/data/status-r2.json
- status-browser: ai-status-final-browser-review.json; SHA-256 a8c5526f1c1fd43b600e5a1ddba3bc6e8a4f244abca2fc82af9e9dd8ce760330; https://ki-forschungsportal.pages.dev/data/status-browser.json
- status-correction: runtime-correction2-evidence.json; SHA-256 93e167320600250759a43c1028265ab6b921add51a25276b71763c999591358b; https://ki-forschungsportal.pages.dev/data/status-correction.json

Conflict of interest: The operator reports on owned projects. Selection is retrospective; no external peer review or sponsor-directed findings.

https://ki-forschungsportal.pages.dev/en/fallberichte/laufzeit-http-200/