Shared relay infrastructure can create correlated outages: when an intermediate server or route becomes unavailable, many users may lose connectivity at the same time. Possible causes include hosting changes, maintenance, routing failures, network filtering, or provider action. Without independently verifiable evidence, this article does not attribute a specific outage to a particular authority or event.
Review RelyVPN's network architecture and supported platforms. Availability depends on current network conditions and local rules.
Understanding Correlated Relay Outages
A correlated outage does not by itself establish a single cause. When many users depend on the same relay or upstream route, one infrastructure change can affect them at the same time. Common causes include:
- Hosting changes — maintenance, suspension, hardware failure, or a provider policy change can make an intermediate server unavailable.
- Routing failures — an upstream network or route change can interrupt access even when the relay server itself is operating.
- Capacity or configuration issues — overload, software errors, or incorrect configuration can affect many users behind the same relay.
- Provider or lawful service action — service availability can also change when a provider responds to its terms, legal obligations, or a valid authority request.
Without independently verifiable evidence, this article does not attribute a specific outage to a particular authority, date, location, or investigative method.
Relay Architecture and Single-Point Risks
To understand the reliability risk, consider how some relay-based proxy services are built:
A typical relay model: user → shared intermediate relay → exit node → requested destination. An intermediate relay can change route length and operating cost, but actual speed, latency, and cost depend on the provider, capacity, route, location, and current network conditions.
The reliability risk: A shared intermediate server or route can become a single point of failure. If it becomes unavailable, multiple users may lose connectivity at the same time, depending on the provider's routing and backup capacity.
The following comparison highlights factors to verify for each architecture:
| Architecture | Speed | Cost | Potential reliability consideration |
|---|---|---|---|
| Shared relay | Network-dependent | Provider-dependent | Higher dependency on shared intermediate infrastructure |
| Dedicated route | Network-dependent | Provider-dependent | Depends on provider and route availability |
| Direct route | Network-dependent | Provider-dependent | Depends on route and server availability |
A shared relay can become a single point of failure. An outage may affect multiple users, while recovery time depends on the cause, provider response, and available alternative routes.
Traffic Analysis and Changing Network Conditions
Public research has documented traffic-analysis methods such as statistical classification and active probing. Their effectiveness varies by protocol, implementation, network, and time. This article does not claim a universal detection rate or compare named providers without current independent test data.
Legal and Privacy Considerations
VPN rules vary by jurisdiction and use case. Users are responsible for following applicable law. RelyVPN's data practices are described in its Privacy Policy. Using a VPN does not guarantee anonymity, prevent identification, or provide an exemption from legal process.
RelyVPN Transport and Fallback Design
Relay infrastructure
RelyVPN does not rely on domestic relay nodes. Service availability still varies by network, region, server status, and time, and uninterrupted connectivity is not guaranteed.
Transport compatibility
RelyVPN uses QUIC/HTTP/3 and TLS 1.3-based transport, with TCP/HTTP/2 fallback when supported. These technologies are intended to improve compatibility across changing network conditions. They do not make traffic undetectable and do not guarantee a connection. For more technical information, see our protocol architecture article.
TCP/HTTP2 fallback
RelyVPN supports TCP/HTTP2 fallback when UDP connectivity is unavailable. A mode change may require reconnection, and successful fallback depends on the network, server, and client version.
BBR Max congestion control
Packet loss, latency, and jitter can result from distance, congestion, routing, radio conditions, or network-management policies. Congestion-control algorithms respond to those conditions differently, so results vary by implementation and route.
RelyVPN uses BBR Max, a congestion-control implementation based on BBR with product-specific tuning:
- Bandwidth probing intended to help the connection adapt after packet-loss events
- Rate-estimation safeguards intended to reduce abrupt estimate changes
- Integration with plan rate limits for resource allocation
RelyVPN uses BBR Max congestion control designed for high-latency links. Streaming, calls, and interactive services depend on the user's network, selected server, device, and the third-party service. No resolution, speed, or latency is guaranteed.
Mobile reconnection behavior
Network changes are constant on mobile: switching between Wi-Fi and cellular, entering elevators, moving between cell towers. Each change can break a VPN connection. RelyVPN's architecture handles this at the system level:
- Each reconnection creates a fresh UDP socket to reduce issues caused by stale NAT mappings
- Screen-aware reconnection may retry after screen unlock while limiting retries during sleep
- Cluster-level routing can use an alternative server node when supported; timing and availability vary
Account and privacy information
RelyVPN does not require an account to start. The data RelyVPN processes, retains, and does not collect is described in its Privacy Policy. Device, diagnostic, transaction, and website data should be understood according to that policy.
How to Evaluate a VPN Service
Use the following checks when evaluating a service:
- Review the provider's privacy policy and security documentation.
- Install software only from official sources.
- Keep a lawful backup communication option for travel or work.
- Keep the app updated.
- Check local laws and third-party platform terms before use.
Frequently Asked Questions
What can cause a correlated outage in relay-based services?
Shared relay infrastructure can create correlated outages: when an intermediate server or route becomes unavailable, many users may lose connectivity at the same time. Possible causes include hosting changes, maintenance, routing failures, network filtering, or provider action. Without independently verifiable evidence, this article does not attribute a specific outage to a particular authority or event.
Why can shared relay infrastructure affect multiple users?
A shared relay can become a single point of failure. An outage may affect multiple users, while recovery time depends on the cause, provider response, and available alternative routes.
How can traffic analysis affect protocol reliability?
Public research has documented traffic-analysis methods such as statistical classification and active probing. Their effectiveness varies by protocol, implementation, network, and time. This article does not claim a universal detection rate or compare named providers without current independent test data.
What transport and fallback features does RelyVPN support?
RelyVPN uses QUIC/HTTP/3 and TLS 1.3-based transport, with TCP/HTTP/2 fallback when supported. These technologies are intended to improve compatibility across changing network conditions. They do not make traffic undetectable and do not guarantee a connection. RelyVPN does not rely on domestic relay nodes. Service availability still varies by network, region, server status, and time, and uninterrupted connectivity is not guaranteed. RelyVPN supports TCP/HTTP2 fallback when UDP connectivity is unavailable. A mode change may require reconnection, and successful fallback depends on the network, server, and client version.
What legal and privacy considerations should users review?
VPN rules vary by jurisdiction and use case. Users are responsible for following applicable law. RelyVPN's data practices are described in its Privacy Policy. Using a VPN does not guarantee anonymity, prevent identification, or provide an exemption from legal process. RelyVPN does not require an account to start. The data RelyVPN processes, retains, and does not collect is described in its Privacy Policy. Device, diagnostic, transaction, and website data should be understood according to that policy.