No DevOps. No complex config. Copy one endpoint and you're live.
1
Create Your Free Account
Sign up in 60 seconds, verify your email, and add a card to unlock 1 GB of residential traffic free for 7 days. We don't charge you until the trial ends. Cancel any time before then to avoid any charge.
2
Configure Your Endpoint
Pick your proxy type, target country, session mode, and protocol in the dashboard. We generate a single endpoint string: that's your complete configuration, nothing else needed.
3
Plug In and Go
Drop the endpoint into any automation tool, bot, browser framework, or app. Real IPs, instant activation, 24/7 uptime monitoring. You're fully operational in seconds.
Simple, Transparent Pricing
Simple per-proxy pricing. Same dedicated IP for entire subscription.
A static proxy provides you with a dedicated IP address that remains the same for your entire subscription period. Unlike rotating proxies, your IP never changes automatically.
What's the difference between ISP and Datacenter static proxies?
+
ISP static proxies have IPs usually registered to telecom and ISP networks rather than cloud hosts, so many sites treat them more like home or business connections. Datacenter static proxies are faster and cheaper but may be detected as datacenter IPs by some sites.
Can I whitelist my IP for authentication?
+
Not on static proxies. ISP and datacenter proxies authenticate with the username and password shown for each proxy in your dashboard. IP whitelisting is available on residential and unlimited residential proxies.
How long do I keep the same IP?
+
You keep the same dedicated IP for your entire subscription period. When you renew, you can choose to keep the same IP or request a new one.
Compare providers for your project
Review current product differences, purchasing terms and a practical switching plan.
Refund for Service FaultsIf the service is inactive or defective in its first 24 hours because of a problem on our side that we don't fix promptly, you can get a refund.
24/7 Expert SupportEngineers available around the clock via live chat. Average first response under 3 minutes.
Zero CommitmentAdd funds from $5, then review the selected product, quantity and billing period before you pay.
Start Using Static Proxies Today
Choose a plan, configure your connection and test it with the pages your application needs.
Find connection settings, plan comparisons and checks you can run with your own pages before a larger order. Open the guide to choose a topic or follow the setup steps.
Read moreRead lessin this guide
Before and after: a saved proxy setup
These examples show which settings and checks to keep when you want to use the same setup again.
What to save
Before
After
Settings
An endpoint is pasted without notes.
Save the country, protocol and session settings with the application.
Page check
Only the connection status is checked.
Open the page and check its location and required fields.
Errors
The full page list is rerun after an error.
Save failed URLs and retry the ones that need another attempt.
How do you keep the same proxy IP between visits?
Use a static ISP or datacenter allocation when a service needs a fixed outbound IP. This can be useful for an IP allowlist, a business account you manage regularly or a scheduled job that should keep the same connection settings. Both products provide static addresses, with different network origins. ISP proxies use ISP-registered addresses, while datacenter proxies use server networks. Check the destination with the product you intend to order.
After ordering, save the assigned address and connection details in the relevant browser profile or application. Record the renewal date where your team tracks subscriptions. If the destination has an IP allowlist, add the assigned address before running the job and test that access works. Keep the same browser profile for returning account visits, because cookies and login state are stored by the browser. A static IP does not preserve those settings when you switch profiles or clear storage. If you replace an address, update every application and allowlist that uses it, then run a short connection check. This is particularly useful when several scheduled jobs share one configuration.
Keep the assigned IP, browser profile and account settings together for returning visits.
Can you order an IP in a particular city?
For static ISP and datacenter proxies, choose from the stock shown in the order form. A city choice is available only when that allocation is offered. If your project specifically needs a city, check the order form before setting a deadline or adding that city to a scheduled report. A location page can help you understand the possible uses, while the order form gives the current purchase options.
Decide which part of the location you need to keep. An account allowlist may simply need one fixed IP in the country. A local delivery check may require a particular city as well as a delivery postcode on the website. If the city is unavailable, standard residential targeting may suit the latter test, while a country-level static allocation may suit the allowlist. Check both against your actual requirements. For repeat work, record the assigned IP, purchased location and renewal date. When replacing an allocation, update saved profiles, scheduled jobs and destination allowlists together. Ask support about the location before ordering if the available label is unclear or the project depends on a specific allocation.
The order form shows the countries and city allocations available for static proxy orders.
How do you organize proxies for business accounts?
Create a separate browser profile for each business account you are authorized to manage. Name the profile so the team can recognize the company and purpose before signing in. Save its proxy settings in that profile and keep the account's cookies and browser storage there. A static ISP allocation can be useful when the same account needs a consistent IP over several days; a sticky residential session suits a shorter connected visit.
Set up one profile at a time and check the displayed account name before making changes. Keep multifactor authentication enabled and make sure the account owner can use the normal recovery process. If the platform asks for verification, complete it through the supported process. For a team, note who can use each profile and review that access when an agency contract ends or a colleague leaves. Store credentials in protected settings and avoid copying complete proxy URLs into account notes. If an assigned IP is replaced, update the relevant profiles and any IP allowlists together. Follow the platform's account and automation rules when planning the setup, including any restrictions on how many accounts your organization may operate.
Give each business account a clearly named browser profile and keep its connection settings with it.
Where should you store your proxy username and password?
Save your proxy username and password in the application's protected settings, an environment configuration or your team's password manager. Keep them out of public repositories and shared reports. If a tool stores a full proxy URL, remember that the URL may contain the password. Check screenshots and copied error messages before sharing them, especially when they show the endpoint generator or a browser's proxy settings.
To help someone reproduce a connection problem, send the client name and version, selected protocol, proxy host and port, approximate time with timezone, and the error message. Replace the password with a clear placeholder. A simple IP-check request is often enough to show an authentication or connection error without sharing customer data. If credentials were exposed, change them through the supported account controls and update every application that uses them. Test one connection before restarting a queue of jobs. For a shared setup, record who maintains it and where the current credentials are stored. That lets another teammate make a planned change without searching through chat messages or copying an outdated password from an old script.
Keep working credentials private and remove the password from screenshots and support examples.
Should you use HTTP, HTTPS or SOCKS5?
Fusion Proxy supports HTTP, HTTPS and SOCKS5 connections. For a browser or web request library, start with the proxy type supported in that application's settings. HTTPS websites can be reached through an HTTP proxy using an HTTPS tunnel. SOCKS5 is useful when the application has a SOCKS5 option. Copy the host and port for that protocol from the dashboard; changing the protocol without updating the port can leave you with a connection that fails.
Check the format expected by the client. Some tools ask for the proxy server and credentials separately, while others accept one connection URL. Keep HTTPS certificate verification enabled. If the client reports a proxy authentication error, recheck the username and password; if it times out, confirm the host, port and network access. Fusion Proxy carries TCP traffic and does not relay UDP. That distinction matters for games and other applications whose website uses HTTPS but whose live connection uses UDP. Test the exact application you want to route. A successful IP check in a browser confirms the browser configuration and gives you a useful starting point for checking another client.
Use the protocol and port shown for your selected endpoint and supported by your application.
Which pages should you test before a larger order?
Choose a short list of pages that reflects your project. For a shopping-site check, include a category page, a product with several variants and a product that is unavailable. For a localized website, include the homepage and a page where language or delivery options change. If you need several countries, run the same checks in each one. These examples show whether the setup handles the parts of the site your project actually uses.
Write down the fields you expect before running the test. Open a few results manually and compare them with the values saved by the script. Look for missing prices, unexpected currencies, duplicate products and pages that show a login prompt. Repeat a small part of the test after changing just one setting, such as the requested city or session type, so you can see its effect. Save the working endpoint configuration with the password removed. Also try a deliberately unavailable page to check that your application records the error and moves on. Once the sample works, use its traffic consumption and completion time to estimate the size and schedule of the full run.
Include the kinds of pages your application will visit, including one that shows how it handles an error.
Before and after: save a setup you can use again
Before saving a setup, a team may paste a proxy into a browser, open a page and leave the settings in that one window. The next person then has to find the endpoint, choose a location and repeat the checks. A saved setup is easier to use again: give the profile a clear name, keep the credentials in protected settings and record the country, session type and test page beside it.
For example, a shop team checking its German catalogue could save a German residential endpoint, a browser profile with German language settings and a delivery postcode used for the test. Keep a product URL and the fields to check, such as price, currency and stock status. On the next visit, open that profile and repeat the same check before starting the full product list. If a result differs, you can inspect the saved settings and the page instead of guessing which connection was used. Update the notes when the shop changes its page layout or the team changes its test location. This also gives a colleague enough information to continue while the original operator is away.
Save the settings with a tested page so your next run starts from a configuration you already know.
How can you tell whether a scheduled job is still working?
For a scheduled collection job, keep a short summary of each run: pages attempted, pages completed, errors and the fields that were missing. A price-monitoring script should tell you when it saved a product without a price or currency. A localized website check should report an unexpected country or language. These checks catch problems such as a changed page layout that can leave the network connection working while the saved data becomes incomplete.
Keep the application version and selected location with the run summary. When a result changes, compare it with a recent run using the same page list and settings. If the new run includes many more pages, allow for that difference before treating a longer completion time as a problem. Choose alerts that tell someone what to do next: update expired credentials, inspect a changed product page or pause a queue that is repeatedly receiving rate limits. Keep a few redacted error examples to help with diagnosis. Review the dashboard's traffic usage alongside the completed page count, especially after changing retries or adding browser resources. A sudden increase can reveal repeated downloads that deserve attention.
Watch for missing fields and unexpected pages as well as connection errors.
Which proxy type should you choose?
Residential proxies provide household IPs with rotating connections or sticky sessions. Fusion Proxy's standard residential product supports country, state and city targeting and is billed by traffic used. Static ISP proxies provide assigned ISP-registered addresses, while datacenter proxies provide assigned server-network addresses. For both static products, check the countries and any city options currently offered in the order form.
Start with the requirement that would be hardest to change. For an IP allowlist, that is usually the fixed address. For a regional website test, it may be the country or city. For a large collection job, traffic usage and the site's response to the chosen IP type matter. Test a small set of actual target pages with the options that meet those requirements. Check the content returned, session behavior and cost for the expected run. Compare current plan duration and stock before ordering. If you need steady high-volume residential traffic with country targeting, also look at the unlimited speed-tier plans. Keep product differences visible in the comparison so you can see which setup the monthly price would actually provide.
Choose rotating residential access for changing household IPs, or a static allocation when the IP needs to stay assigned.
What information helps support fix a connection problem?
Send support the application name and version, proxy type, protocol, selected location and the approximate time of the problem with timezone. Include the exact error message and say whether it happens on every request or only on one website. Remove the password from connection URLs, screenshots and logs. If a simple IP-check request fails too, mention that result; it helps distinguish a connection problem from a page-specific issue.
Describe what changed before the failure. Common examples include a client update, a new proxy password, a different city selection or a change to the destination page. Keep one small example that reproduces the error and one recent working example if available. Avoid sending a whole customer dataset when a single redacted request is enough. For ongoing team use, keep the tested settings, subscription renewal date and responsible person in the place where you maintain the application. Add the test page and the result you expect. A colleague can then check the connection after an update or take over a scheduled job without copying unknown settings from an old browser window.
Include one failing request, the time and the client version, with the password removed.
Need help choosing or connecting?
Check current plans and available locations before ordering. For setup help, use the connection documentation or tell support which application and website you want to connect. Include any error message and the selected protocol, with the password removed.
