Enterprise Reliability Without Enterprise Complexity
Uptime is not a feature. It is a prerequisite. Every minute of proxy downtime translates directly to missed data, failed automations, and lost revenue. Hex Proxies treats reliability as the foundational layer upon which every other feature is built, and we build toward a 99.9% uptime target, with live status and incident history published on our status page.
What 99.9% Actually Means
A 99.9% monthly uptime target allows for a maximum of approximately 43 minutes of downtime per month. We engineer toward that target through redundancy at every layer of the stack, and we publish live status and incident history on our status page so you can verify our performance at any time.
Infrastructure Redundancy
Our gateway servers run in active-active pairs in geographically separated data centers. Each pair shares session state through a distributed cache, so if one gateway fails, the surviving gateway serves all traffic without session loss. There is no primary or secondary distinction; both gateways handle production traffic simultaneously.
The routing layer uses a consensus-based distributed system. Routing decisions are made by a quorum of nodes, and the system tolerates the failure of any single routing node without degradation. Session affinity data is replicated across multiple routing nodes at all times.
Egress nodes (the IPs that carry your requests to their destination) are monitored individually. Each egress node is health-checked every minute with a synthetic request that validates connectivity, latency, and response correctness. Nodes that fail health checks are removed from the active pool immediately and only re-added after passing consecutive healthy checks.
Incident Response
Automated monitoring runs around the clock, probing every service every 60 seconds. Alerts fire when any metric crosses predefined thresholds, including latency spikes, error rate increases, and individual node failures. Incidents are declared and tracked on our public status page, where the full incident history is available.
Maintenance
Infrastructure changes are deployed using blue-green or canary deployment patterns designed to minimize downtime. When we need to replace hardware, we provision new capacity first, migrate traffic gradually, and then decommission the old hardware. Any maintenance expected to affect service is announced in advance on our status page.
Verifiable Uptime
We are built for 99.9% uptime, and we publish live status and complete incident history on our status page so customers can verify our performance independently. Health checks run every minute across all monitored services. If an incident affects your workloads, contact support and our team will review it with you directly.
Disaster Recovery
Our disaster recovery plan covers scenarios from individual server failures to complete data center outages. For single-server failures, failover is automatic. For data center-level events, we maintain standby capacity in alternative facilities that can absorb production traffic. We test disaster recovery procedures regularly.
Monitoring Stack
We use a multi-layer monitoring approach. Network-level monitoring tracks BGP announcements, link utilization, and packet loss. Application-level monitoring tracks request success rates, latency distributions, and error classifications. Business-level monitoring tracks customer impact metrics like active sessions, requests per second, and uptime-target compliance in real time. Live service status is published for everyone on our public status page.
Track Record
We publish our reliability record in the open. Live status and the complete incident history are available on our status page, with health checks running every minute across all monitored services, so you can audit our performance directly rather than taking our word for it.