How to Switch Static IP Proxy Providers Safely
Move your outbound traffic with a practical plan for allowlists, application testing, connection draining and rollback.
Changing proxy providers is easier when you separate the migration into decisions you can verify: which workloads need the new route, which destinations must accept it, how you will test it, and when the old route can be retired.
The aim is to keep your application working while you change how it connects. Prepare the new path alongside the old one, prove it with representative operations, and move traffic in controlled stages instead of treating a new proxy URL as a finished migration.
This guide covers switching outbound proxy providers, including a move to QuotaGuard. Inbound reverse-proxy migration requires a separate plan. It does not assume that another provider's IP addresses transfer to your new subscription. Plan for a new egress identity unless the providers explicitly confirm otherwise.
The migration at a glance
Inventory → Prepare → Allowlist → Test → Cut over → Observe → Retire
Keep the old route available for the agreed overlap period. Add the new addresses before moving traffic. Decide what success and rollback look like before changing production.
Choose the right migration path
- Changing outbound proxy providers: use the sequence below.
- Moving from shared to dedicated QuotaGuard service: follow the shared-to-dedicated guide. Support provisions a new IP pair and connection URL, and the old access is available for an agreed transition period. Confirm its end date and request any extension before it expires.
- Moving an existing QuotaGuard subscription from Heroku to direct billing: use the Heroku migration guide. That supported subscription transfer can preserve your existing connection identity. It is not the same operation as replacing one proxy provider with another.
- Switching between QuotaGuard Static and Shield: the products use different address pools, so your IPs change. Arrange the transition, add both new IPs at every affected destination, and keep the old service available until the new route is verified.
1. Inventory the connections, not just the application
Start with a small migration worksheet. For each workload, record:
- Runtime and owner: web service, worker, scheduled job, serverless function or administrative tool.
- Destination hostname, port and protocol.
- Current proxy integration and where its configuration is stored, including explicit client settings and bypass rules such as
NO_PROXY. - Who controls the destination's allowlist and how long changes take.
- Whether the destination permits shared source IPs or requires exclusive or separately registered addresses.
- Any allowlist capacity, source-IP rate limits or provider-range restrictions that could affect the new route.
- A representative operation that will demonstrate success.
- Whether the workload holds connections open or creates them for each operation.
- The previous configuration and the steps needed to restore it.
A web application and its overnight export may share a repository without sharing proxy settings. A successful browser-facing request does not prove that the export worker has migrated.
Record a baseline before changing anything: normal completion rates, connection errors, latency, queue depth and job duration. Choose measurements that reveal a problem in your application, rather than collecting every available metric.
2. Match the integration to the traffic
A replacement proxy must work with your actual client and protocol. Do not assume that replacing the hostname in an old URL preserves the scheme, port, authentication method or TLS behavior.
Keep the change limited to the traffic that needs the new identity, and preserve the required bypasses for local and private-network destinations.
For HTTP and HTTPS APIs, an HTTP proxy is often the straightforward choice. Database connections, SFTP and other non-HTTP TCP traffic need an appropriate SOCKS or tunnel integration. QuotaGuard's HTTP versus SOCKS guide explains that distinction.
QuotaGuard Static offers HTTP and SOCKS5; QuotaGuard Shield adds TLS to the proxy through HTTPS proxying and SOCKS over TLS. A client that supports HTTPS destinations does not necessarily support an HTTPS proxy, and ordinary SOCKS5 support does not establish SOCKS-over-TLS compatibility. Verify your actual library and version, destination ports, capacity and timeout requirements. Do not infer UDP or QUIC support from documented TCP use cases.
If you use QGTunnel, review the SOCKS quick start against your deployment. Check the startup command, destination mappings and any local configuration file, not only an environment variable. A configuration change is useful only if the process handling the traffic actually loads it.
Also check:
- Network reachability: the destination must be reachable from the new proxy path. A static public egress address does not itself provide access to a private network or private DNS zone.
- Application support: confirm that your client uses the selected proxy configuration. A proxy variable is not a universal instruction understood by every library.
- TLS: retain certificate and hostname verification. An HTTPS destination accessed through an HTTP CONNECT proxy can still have end-to-end application TLS; that is separate from encryption of the client-to-proxy connection and its authentication exchange. See the Static setup guide's HTTPS explanation.
- Security boundaries: Static HTTP CONNECT does not encrypt the initial proxy authentication exchange or CONNECT target. Shield protects the client-to-proxy hop, but a plaintext destination protocol remains plaintext beyond the proxy unless you separately configure end-to-end encryption. Keep destination authentication and TLS verification intact, and preserve SSH host-key verification for SFTP.
- Secrets: keep proxy credentials in your approved secret store. Redact full connection URLs from screenshots, tickets and logs.
Use the complete connection details supplied for the new service. Avoid guessing credentials or building a new URL by copying pieces from the old provider. For QuotaGuard, obtain the protocol-specific URLs and assigned IPs from Setup → Outbound. The proxy connection host is not interchangeable with the source IPs a destination sees.
3. Prepare an overlap period and update allowlists
Agree how long both services will remain usable, who pays for the overlap, and the deadline for cancellation or retirement. A new-provider trial is not a promise that the previous provider will keep your old route active. Cross-provider overlap depends on both services and your subscriptions.
Ask destination owners to add the new addresses while retaining the old entries for the migration. Confirm that the rules are active, not merely that someone submitted a change request.
These are the destination's inbound source-IP rules. Separately check that your application's own network permits outbound connections to the new proxy host and port.
QuotaGuard provides two assigned static IP addresses for its normal high-availability setup. Allowlist both: traffic can use either address. Seeing one address in a brief check does not establish that all subsequent connections will use that address. See why QuotaGuard provides two IPs.
If a partner cannot permit old and new addresses together, agree a coordinated change window and rollback procedure before proceeding. Do not describe that situation as a routine zero-downtime cutover.