Add Spectrum troubleshooting docs for top support case drivers#30683
Open
stechedo wants to merge 3 commits intocloudflare:productionfrom
Open
Add Spectrum troubleshooting docs for top support case drivers#30683stechedo wants to merge 3 commits intocloudflare:productionfrom
stechedo wants to merge 3 commits intocloudflare:productionfrom
Conversation
Updating process for reporting an incorrect IP address
…se drivers Based on analysis of April 2026 Network SBR cases, add documentation to address the top 3 case-generating Spectrum issues: 1. IP Access Rules + Health Checks interaction: Customers enable IP Access Rules on Spectrum apps, then Cloudflare health checks fail because probe IPs are blocked. Added warnings to configuration-options and load-balancing/spectrum pages. 2. Same hostname for WAF + Spectrum: Customers attempt to use the same hostname for HTTP (WAF) and TCP (Spectrum) on different ports. This is a platform limitation. Added new section to limitations page and cross-reference on DNS troubleshooting page. 3. Edge TLS / Protocol mismatch: Customers configure HTTP edge ports expecting HTTPS to origin. Spectrum does not upgrade protocols. Added warnings to Edge TLS Termination section. Also: - Created new /spectrum/reference/troubleshooting/ page with structured symptom/cause/solution sections for all three issues plus error 525 and common status code patterns - Added note to /spectrum/reference/logs/ clarifying that Spectrum status codes are distinct from HTTP status codes
github-actions
Bot
added
product:load-balancing
Replace stale email address (ip-corrections@cloudflare.com) with the data correction form link and add 48-hour SLA language, matching the currently published version at developers.cloudflare.com.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new Spectrum Troubleshooting page and improves existing Spectrum documentation to address the top 3 case-generating issues identified in the April 2026 Network Support-by-Request (SBR) case review (~190 cases analyzed).
Estimated case deflection: 9-13 cases/month across these 3 issues.
Changes
New page
/spectrum/reference/troubleshooting/— New troubleshooting page with structured symptom/cause/solution sections covering:Modified pages (5)
/spectrum/reference/configuration-options/— Added warnings about IP Access Rules blocking health checks, Custom Rules not working with Spectrum, protocol upgrade not being supported, and double-proxy chains causing 525 errors. Expanded intro paragraph to clarify Spectrum's L4 pass-through behavior./spectrum/reference/limitations/— Added new "IP access control" section and "Using the same hostname for HTTP proxy and Spectrum" section documenting the platform limitation and recommending split-hostname architecture (with Citrix Gateway use case)./spectrum/reference/logs/— Added note clarifying that Spectrum status codes are distinct from HTTP status codes, with cross-link to troubleshooting page./load-balancing/additional-options/spectrum/— Added caution callout in the Monitors setup step warning about IP Access Rules blocking health checks./dns/manage-dns-records/troubleshooting/records-with-same-name/— Added note explaining that DNS record conflicts also apply to Spectrum applications, with cross-link to Spectrum limitations.Motivation
These documentation gaps were identified by reviewing all April 2026 Network SBR cases. The top case-generating patterns were:
Content area
Spectrum, Load Balancing, DNS