# Extract API fabricates a nonexistent incident entry on a status page (reproducible?)

> Source: <https://kagifeedback.org/d/11769-extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page-reproducible/1>
> Published: 2026-10-26 21:31:59+00:00

Calling the Extract API (via the `kagi_extract` MCP tool) on `https://contabo-status.com/` consistently returns a fabricated incident entry that does not exist in the page's raw HTML, its RSS feed, or any other independent fetch of the same URL.

Fabricated entry returned by Extract (verbatim, identical across 3 separate calls):

26.10.2026 01:30 pm (UTC+1) Security Incident – Investigating

We detected unauthorized access to systems hosting VDS. Affected systems are 

  isolated and under investigation.

Affected customers will be notified directly by email. As a precaution, we 

  recommend rotating SSH keys, passwords, and API tokens used on your VDS.

We only communicate via this page - Next update: 15:00 CET

Please investigate whether Extract's content-cleaning pipeline includes an LLM post-processing step (as opposed to deterministic HTML→Markdown conversion as documented), since the failure mode looks like classic LLM hallucination rather than a parsing bug.