Future InTech
Language · English

Log queries and report integrity · FIELD GUIDE

Compare edge and origin status codes in crawler investigations

Locate the response layer behind an error trend, including cases where a Worker changes the response returned to the client.

By Future InTech · Published
Evidence cutoff: 2026-11-02T20:30:57.067733+00:00 · UTC

What the evidence can establish

Cloudflare documents origin and edge status as useful comparison points. Its Workers analytics guide also explains that a Worker can receive a 500 from a subrequest and return a 200 to the client, with the client-facing status appearing in zone analytics. The practical implication is to preserve both observations when available. A successful delivered response does not by itself demonstrate a healthy origin fetch, and an origin failure does not always describe what the client ultimately received.

Hypothetical example: a Worker serves an approved fallback after an origin error. The client-facing chart shows 200 while the subrequest record shows 500. Report both facts and identify the fallback behavior. Do not hide the origin error, but also do not tell readers that every affected client received a 500. Whether the fallback was useful requires examining the returned content and the intended behavior.

Origin or subrequest status; Worker or proxy response decision; Client-facing edge status; Content correctness check
Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.

The saved evidence used here

This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.

c1 · Explanation and verification steps
Comparing origin and edge statuses helps investigate the response layer. Source 1
c2 · Explanation and verification steps
A Worker can receive a subrequest error and return a different client-facing status reflected in zone analytics. Source 2

The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.

AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.

What to do next

  1. Pick a narrow incident interval and affected public path. Record the client-facing status, origin or subrequest status, and any reliable correlation identifier available in your authorized records.
  2. Inspect the delivery logic for caching, fallback or response rewriting. Use the deployed configuration or code to support the explanation rather than guessing from two totals.
  3. Check one controlled response body or version marker to verify what was delivered. Remove private data before sharing the observation.
  4. Create separate alert conditions for origin health and delivered-response correctness. After a fix, repeat both checks and retain the original incident window.

How to check the result

The report identifies which layer produced each status and whether the delivered representation met its intended contract. A healthy client response no longer erases a recorded upstream problem.

Limits of this conclusion

Not every dataset exposes both statuses or a reliable join. When correlation is unavailable, report parallel aggregates with that limitation instead of presenting a request-level causal chain.

This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.

Sources and publication checks

Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.

Status codes

Obtained: 2026-11-02T21:00:56.984397+00:00
Location: Status codes / b3

Saved source fingerprint0f6c60b5bb0bf32d83684e215132fed5272c16c9580b8b3a448d89f260d61c82
Cloudflare analytics with Workers

Obtained: 2026-11-02T20:30:57.067733+00:00
Location: Zone analytics / b4

Saved source fingerprintaedf0360198f7989182e841ebdcfeb33168ae807423038f8e8ca3e2b02d537c4

Download this edition's evidence and action record (JSON)