Quick troubleshooting view
The origin responds to some tests while connections from Cloudflare time out.
- Cloudflare IP ranges filtered
- Intermittent saturation
- Asymmetric routing
- Correct only the component confirmed by the checks
- Retest the original symptom after the change
- Escalate with collected evidence when the cause remains unclear
Contextual technician plan
Perform this check and preserve the observed result before changing configuration.
“Check firewall logs at the 522 timestamp” should produce an observation that clearly confirms or rules out “Cloudflare IP ranges filtered”.
If the observation is normal, lower “Cloudflare IP ranges filtered” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Cloudflare IP ranges filtered” first. Related action: Correct only the component confirmed by the checks.
Perform this check and preserve the observed result before changing configuration.
“Measure load and connection counts” should produce an observation that clearly confirms or rules out “Intermittent saturation”.
If the observation is normal, lower “Intermittent saturation” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Intermittent saturation” first. Related action: Retest the original symptom after the change.
Perform this check and preserve the observed result before changing configuration.
The exact failing name should resolve through the expected DNS server to the expected record without timeout.
If the exact name resolves correctly, compare application cache, suffix/search domain and the client or network where the failure remains.
If resolution fails or returns the wrong record, keep the queried server and answer and correct the resolver, zone/record or DNS path that is actually wrong.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Escalate with the exact symptom, scope, timestamp and completed checks when the issue remains unresolved.
＋Open the complete detailed guideDetailed explanations and original troubleshooting content.
The origin responds to some tests while connections from Cloudflare time out.
Likely causes
- Cloudflare IP ranges filtered
- Intermittent saturation
- Asymmetric routing
- Connection limit reached
Checks in priority order
- Check firewall logs at the 522 timestamp
- Measure load and connection counts
- Verify origin DNS
- Compare direct access with Cloudflare access
When to escalate
Escalate when the failure affects multiple users, a production dependency is unavailable, or logs show a component outside your control. Include timestamps, scope, tests already performed, and the last known working state.