[Support] Apply 499 and origin timeout review replacements by dpolaske-cloudflare · Pull Request #34060 · cloudflare/cloudflare-docs

dpolaske-cloudflare · 2026-10-06T21:16:19Z

Summary

Follow-up to #33662, targeting its source branch so these edits can be incorporated into the existing change.

Separate the 499 rate denominator from completed-request timing comparisons and account for log sampling.
Use the published upstream timing definition without adding recording-lifecycle guarantees.
Clarify partial responses, transaction reconciliation, and application-specific idempotency behavior.
Use exact cache-status values and restore distinct streaming investigation steps.
Align the 522, 525, and Connection limits explanations for setup, reuse, and request acknowledgment.
Qualify origin allowlisting for standard connections and dedicated egress, and separate visitor geography from origin reachability.
Preserve the documented 19-second and 90-second TCP conditions and existing product-specific troubleshooting sections.

Validation

pnpm run check: passed, including Astro and Worker type checks.
pnpm run format: passed.
pnpm run build --silent: passed.
git diff --check: passed.

Integration

The base is support/499-troubleshooting-improvements, not production. Merge this follow-up into that branch to include the replacements in #33662.

cloudflare-docs-bot · 2026-10-06T21:16:43Z

AI Review

✅ Reviewed 3d9a42a · 0 findings · incremental

Commands

/review Run a review now.
/full-review Review the entire PR diff.
/disable-auto-review Stop automatic reviews.
/rebase Rebase against production.

stechedo

Verified against the current published docs and log schema before approving:

CacheCacheStatus values (hit, stale, miss, bypass) match the http_requests dataset enum, and dropping dynamic from the support trigger is right since it can mean a security block rather than an expected origin fetch.
OriginResponseDurationMs now matches the published definition (first datacenter, Argo Smart Routing and Tiered Cache included) without the unverified recording-lifecycle claim.
Instant Logs sampleInterval guidance matches the Instant Logs docs.
The 19s/90s conditions are preserved and consistent across connection-limits, 522, 499, and 525. #what-connection-means-here and #keep-alives anchors resolve, and the dedicated egress IPs and tunnel troubleshooting links are live.
Steps usage matches the component contract (wraps a markdown ordered list) and the repo-wide import pattern.
Everything raised in the #33662 review threads is reflected in the final text.

Approving from the support side. Three non-blocking comments below.

stechedo · 2026-10-06T22:06:19Z

+No single field identifies the cause. Correlate these fields with matched request populations and request-linked evidence:
+
+- **`OriginIP`** — identifies the origin IP recorded for the request. An absent value does not establish where the request stopped. A request served from cache may not require an origin fetch. An aborted or incompletely logged request may also lack an origin IP. Correlate this field with `CacheCacheStatus` and request-linked evidence.
+- **`CacheCacheStatus`** — records cache disposition in the [HTTP requests dataset](/logs/logpush/logpush-job/datasets/zone/http_requests/). Values such as `hit` or `stale` indicate a cache-served response, where an absent origin IP may be expected. Values such as `miss` or `bypass` help identify requests to investigate. They do not establish that an origin connection was attempted or where an aborted request stopped. Collect request-linked and origin-side evidence before attributing a cause.


Non-blocking: since dynamic is now excluded from the contact-support criteria, consider a half-line here noting that dynamic means the request is not eligible for cache (which can include security blocks), so readers understand why it is not treated like miss or bypass.

stechedo · 2026-10-06T22:06:19Z

- **`CacheCacheStatus`** — the log field name for cache disposition in the [HTTP requests dataset](/logs/logpush/logpush-job/datasets/zone/http_requests/). If `OriginIP` is absent and `CacheCacheStatus` is HIT or STALE, the request was served from cache — the missing origin IP is expected. If `OriginIP` is absent and `CacheCacheStatus` is MISS or BYPASS, the cache phase indicates an origin fetch was expected; however, an aborted request may lack phase fields. Treat this combination as an unresolved phase and collect request-linked and origin-side evidence before attributing a cause.
+No single field identifies the cause. Correlate these fields with matched request populations and request-linked evidence:
+
+- **`OriginIP`** — identifies the origin IP recorded for the request. An absent value does not establish where the request stopped. A request served from cache may not require an origin fetch. An aborted or incompletely logged request may also lack an origin IP. Correlate this field with `CacheCacheStatus` and request-linked evidence.


Small wording nit: identifies the origin IP recorded for the request reads a bit circular. The origin IP recorded for the request would be cleaner.

ngayerie · 2026-10-07T09:42:57Z

 ### Resolution

- Contact your hosting provider and share the [error details](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to assist in troubleshooting these common causes:
+If you own the website, use these general checks:


I think it's safe to assume it's website owners that will land on this documentation. I would just remove this statement

ngayerie · 2026-10-07T09:47:57Z

-  - Packets were dropped at your origin web server.
+- Verify the configured origin address and port. Confirm the service is running and accepting connections. Review its capacity and logs for overload or connection limits, and review its [HTTP keep-alive settings](/fundamentals/reference/connection-limits/#keep-alives).
+- Review firewall, security, rate-limiting, and network settings for your connection path. For standard proxied origin connections, check [Cloudflare's published IP ranges](https://www.cloudflare.com/ips/). For [Dedicated CDN Egress IPs](/smart-shield/configuration/dedicated-egress-ips/), check the addresses assigned to your setup.
+- If geographic restrictions are configured, review the origin's permitted connection sources separately from [visitor-country WAF rules](/waf/custom-rules/use-cases/block-by-geographical-location/). Visitor filtering and origin reachability are different checks.


I feel this statement might be confusing. I'm not sure it helps to mention geographic restritction in its own bullet: the issue we see with that is that customers are restricting IPs connecting to their origin. So this check falls into the second point here.

Yep, agreed. Let's take it out.

ngayerie

See comments from myself and Stephen

Apply changes from PR #34060 (dpolaske-cloudflare) into this branch. error-499.mdx: - Use <Steps> component for numbered investigation steps - Fix Logpush guidance: export full population, not 499-filtered only - Add sampleInterval note for Instant Logs rate calculation - Correct CacheCacheStatus value casing (miss/bypass, not MISS/BYPASS) - Soften 'Possible edge or network issue' table row - Clarify OriginResponseDurationMs measures time at first CF data center - Warn: do not infer failed phase from timing on 499 entries alone - Fix body bytes wording: zero bytes does not confirm pre-first-byte disconnect - Improve idempotency keys guidance - Update contact-support section with matched-cohort language connection-limits.mdx: - Add 'What connection means here' section clarifying TCP vs HTTPS setup - Rename 'Complete TCP Connection' to 'TCP connection establishment' - Rename 'TCP ACK Timeout' to 'TCP request acknowledgment timeout' - Note 19s/90s are not a universal TCP+TLS budget

[Support] Clarify 499 and origin connection timeout guidance

53180bb

dpolaske-cloudflare requested review from a team, AdamBouhmad, Sahidya, jhutchings1, krys-cf, ngayerie, stechedo and zeinjaber as code owners October 6, 2026 21:16

github-actions Bot added product:fundamentals product:support size/m labels Oct 6, 2026

stechedo approved these changes Oct 6, 2026

View reviewed changes

ngayerie reviewed Oct 7, 2026

View reviewed changes

ngayerie requested changes Oct 7, 2026

View reviewed changes

dpolaske-cloudflare added 2 commits October 7, 2026 11:55

[Support] Apply 522 resolution review feedback

b44e81b

[Support] Address remaining 499 and 522 review feedback

3d9a42a

ngayerie closed this Oct 21, 2026

Navigation Menu

Repository navigation

[Support] Apply 499 and origin timeout review replacements - #34060

[Support] Apply 499 and origin timeout review replacements#34060
dpolaske-cloudflare wants to merge 3 commits into
cloudflare:support/499-troubleshooting-improvementsfrom
dpolaske-cloudflare:support/499-origin-timeout-review-fixes

dpolaske-cloudflare commented Oct 6, 2026

Uh oh!

cloudflare-docs-bot Bot commented Oct 6, 2026 •

edited

Loading

Uh oh!

stechedo left a comment

Uh oh!

Uh oh!

stechedo Oct 6, 2026

Uh oh!

stechedo Oct 6, 2026

Uh oh!

ngayerie Oct 7, 2026

Uh oh!

dpolaske-cloudflare Oct 7, 2026

Uh oh!

ngayerie Oct 7, 2026

Uh oh!

dpolaske-cloudflare Oct 7, 2026

Uh oh!

ngayerie left a comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

dpolaske-cloudflare commented Oct 6, 2026

Summary

Validation

Integration

Uh oh!

cloudflare-docs-bot Bot commented Oct 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

AI Review

Uh oh!

stechedo left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

stechedo Oct 6, 2026

Choose a reason for hiding this comment

Uh oh!

stechedo Oct 6, 2026

Choose a reason for hiding this comment

Uh oh!

ngayerie Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

dpolaske-cloudflare Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

ngayerie Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

dpolaske-cloudflare Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

ngayerie left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

cloudflare-docs-bot Bot commented Oct 6, 2026 •

edited

Loading