Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- GA version 2026.8.2110.0 for Windows, macOS and Linux fixes repeated disconnects and reconnects when a hostname-based Split Tunnel configuration fails to apply.
- Earlier version 2026.8.2100.0 describes a separate issue: traffic to Split Tunnel excluded resources could be briefly blocked during reconnection.
- The current stable-download page lists 2026.8.2115.0 as the latest card for all three desktop platforms; 2026.8.2110.0 is in version history, so do not downgrade to it to match this historical fix.
- Record the actual client version, OS, mode, hostname-rule application evidence and time, then retest the same authorized request after an approved update.
Check whether the loop matches a hostname rule that failed to apply
If Cloudflare One Client keeps disconnecting and reconnecting on Windows, macOS or Linux, first check whether it uses a hostname-based Split Tunnel configuration and whether that rule failed to apply. Split Tunnel is a routing method that uses rules to decide which traffic goes through the tunnel and which traffic bypasses it. On October 12, 2026, Cloudflare published separate GA stable releases, version 2026.8.2110.0, for all three systems. Each says the release fixes repeated disconnects and reconnects when a Split Tunnel configuration with hostname-based entries fails to apply.
That fix has a specific trigger; it does not show that every reconnect loop has the same cause. The release notes do not give an affected-version range, an exact release time or time zone, or evidence that an organization’s devices received the update. Seeing repeated reconnects alone is not enough to identify the cause.
Separate it from brief blocking of excluded resources
The downloads page’s version history also lists the earlier 2026.8.2100.0 release. Its notes say traffic to Split Tunnel excluded resources could be briefly blocked while the client was connecting or reconnecting, and that the client now keeps its learned Split Tunnel configuration. This describes a brief interruption to target traffic during reconnection. It is different from the 2026.8.2110.0 note about the client repeatedly reconnecting after a hostname-based configuration fails to apply.
Record whether the observed symptom is a client reconnect loop or a particular request to an excluded resource pausing during reconnection. Then compare the notes for the operating system and version actually in use. Version order alone does not prove which fixes a particular installation contains, and it does not establish the affected-version range.
Choose a version through your organization’s approved stable-release process
Do not treat 2026.8.2110.0 as the latest stable version. On the official stable-download page checked for this guide, the latest stable cards for Windows, macOS and Linux all list 2026.8.2115.0, dated October 20, 2026, with a certificate-chain build fix. Version 2026.8.2110.0 appears in previous-version history. Do not downgrade from a higher version just because the 2110.0 announcement mentions reconnecting.
Ask an authorized organization administrator to confirm the approved release track and package, then follow the organization’s existing update process. The sequence of version numbers, the certificate-chain note for 2115.0 and the reconnect note for 2110.0 do not establish a particular account’s rollout status or resolve every connectivity problem.
Collect evidence around the same authorized request
Record the client version actually running, OS version, connection mode, time and time zone, and verifiable evidence of whether the hostname rule exists and was applied. Also note the affected authorized target, the error observed and the network state. Remove credentials and unrelated customer information from screenshots or support records. Do not change organization policy just to test this article.
After an organization-approved update, retry the same authorized target under conditions that are as similar as practical. Keep the before-and-after errors and results. A client showing “Connected” does not prove that an application request has recovered. This guide summarizes public release notes; no client was installed and no connection was tested. If the request still fails, give the redacted record to your organization administrator to check the configuration and other possible causes.
Check platform requirements and keep unknowns open
Before choosing a package, check the current download page for the OS, architecture and distribution. Its Windows table lists supported editions such as Windows 10 LTSC; that does not mean every Windows 10 edition. The macOS table lists Sequoia 15.1+ and explicitly excludes 15.0.x. Linux packages must match a distribution and architecture in the current table. Check the current official stable-download page listed under Sources for the full platform and resource requirements.
The three October 12 announcements state the fix condition but do not list every affected version or say when each organization will receive an update. If the rule appears to be applied, or the same request still fails after an update, ask an organization administrator to investigate under the existing process. Do not disable protections or change Split Tunnel policy based on this release note.
Sources
Frequently Asked Questions
Should I switch to a higher-numbered beta release to troubleshoot?
Do not choose a release track by version number alone. The official stable-download page recommends stable releases for production and describes beta as a track for testing unstable new features. Have an administrator confirm the approved track and test arrangements; a higher beta version number does not establish that it is suitable for production.
Do the 2026.8.2110.0 announcements also cover iOS, Android or ChromeOS?
The three GA announcements reviewed here are for Windows, macOS and Linux. They do not establish that iOS, Android or ChromeOS received the same version or fix. Users on mobile devices or Chromebooks should check the current official notes for their platform.