Symptoms
- The site works from one network or region but times out from another.
- Users report DNS errors, connection resets, TLS warnings, redirect loops, or incomplete assets.
- WordPress administration loads inconsistently while the public site remains available.
Likely causes
Possible causes include recursive-DNS differences, stale records, IPv6 routing, CDN or firewall rules, hosting-provider policy, TLS/SNI compatibility, certificate-chain problems, blocked third-party assets, WordPress URL configuration, or a local network issue. Geography alone does not establish the cause.
Diagnostic steps
- Record the exact URL, time, network, browser error, and whether the failure affects all users.
- Compare authoritative and recursive DNS answers, including A, AAAA, and CNAME records.
- Test IPv4 and IPv6 separately from permitted observation points.
- Inspect the TLS certificate chain, hostname, expiry, SNI behavior, and HTTP redirect sequence.
- Review CDN, web-application firewall, origin, and hosting logs for the affected time without assuming absence of a log proves blocking.
- Check WordPress Site URL and Home URL, mixed content, and third-party assets.
Resolution steps
Apply the smallest evidence-backed correction: repair DNS, remove an invalid AAAA record, install the full certificate chain, correct redirect or URL settings, adjust an unintended firewall rule, or replace an inaccessible dependency. Do not advise bypassing legal restrictions or security controls.
Escalation conditions
Escalate to the DNS, CDN, hosting, or network provider with timestamps, sanitized request IDs, resolver results, traceroute or TLS observations where lawful, and a clear comparison between working and failing paths.
Customer-safe explanation
“The symptom appears to depend on the connection path rather than the WordPress content alone. We are comparing DNS, certificate, and server observations from the affected path before recommending a change.”