Can you move from shared to dedicated proxies and keep your IP?

Dedicated Datacenter on Node4 is a new plan with a fresh IP; your shared plan keeps its address until its paid period ends.

No, not on every provider, and not on Node4. Upgrading from a shared proxy to a dedicated one usually means a brand-new address from the dedicated pool, not a conversion of the one you were already using. On Node4, a Shared Datacenter plan and a Dedicated (Premium) Datacenter plan draw from separate pools: buying dedicated starts a new plan with a fresh IP. Your shared plan is a separate subscription, so its address stays on your account for as long as that plan is paid. Canceling it only stops the next renewal: the shared address keeps working to the end of the period you already paid for, and is released after that.

TL;DR

  • Upgrading from shared to dedicated usually provisions a new address; it does not convert the one you already have.
  • A dedicated allocation changes who can use an address, not its history or a target site's rules.
  • curl can verify the exit address you are using, but it cannot prove exclusivity by itself.
  • Keep the existing configuration live until the new address passes the same checks the old one did.

Moving to dedicated always provisions a new address

On Node4, yes, always. Shared and Dedicated Datacenter are different products drawing from different pools, so there is no "convert this specific IP" option: buying dedicated allocates a new address under its own subscription. The shared plan keeps running alongside it. Its address goes back to the shared pool only once that plan's paid period is over: when the period ends if you canceled it, or 14 days after the renewal date if the renewal is left unpaid. If address continuity matters more than exclusivity, that is worth knowing before you buy, not after.

Other providers run their allocation differently, so if you are migrating elsewhere, ask directly:

  1. Record the public exit IP your application actually uses today.
  2. Ask the provider in writing whether that exact address can become dedicated to your account, or whether the upgrade always issues a new one.
  3. If a conversion is offered, confirm when access by other customers on that address ends.
  4. Establish whether credentials, endpoints, or active connections change during the cutover.
  5. Test the new allocation before moving the production workload onto it.

Your proxy hostname is not necessarily your public exit address. A gateway can accept connections at one address and send traffic through another, so copying the old hostname into a new configuration proves nothing about exit retention.

If exclusivity is the reason for switching, separate that requirement from IP continuity. The guide to whether a dedicated proxy is worth paying extra over a shared IP addresses the allocation decision; the checks below cover verifying whatever address you end up with.

What an unchanged address would and would not prove

An unchanged exit IP preserves one observable part of your application's network identity. It does not preserve every part of a session: cookies, authentication tokens, connection state, and the destination's own security controls remain separate concerns.

The reverse matters too. An unchanged login session is not evidence that you retained the exit IP, because applications differ in how they handle address changes. Verify the address directly instead of inferring it from a successful login.

Before cutover, define success: the expected exit address (new or retained), the exclusivity you need, and the application checks that must pass before you retire the old configuration.

New allocation versus a same-address conversion

These are different migration paths, and on Node4 only the first exists. Choose your expectations accordingly.

Migration pathWhat it isMain benefitMain limitation
New dedicated allocationA fresh IP from the dedicated pool, as on Node4Simple, exclusive from day one, old plan keeps working to the end of its paid periodYour public exit address changes
Same-address conversionThe existing shared address becomes exclusive to youPreserves the address, where a provider actually offers itNot offered by every provider; IP history remains either way
Keep the shared allocationNo migration at allAvoids any changeOther authorized customers continue sharing the address

If a same-address conversion is a hard requirement, confirm in writing that your specific provider offers it before you buy. Do not accept a new address as an equivalent outcome when continuity was the point of asking.

Choosing a new dedicated allocation is the right call when exclusivity matters but address continuity does not. Update any IP-based access rules you control before cutover, and test the destination workflow using the new address.

Keeping the shared allocation remains a valid choice when you have no demonstrated need for exclusive use. It does not solve interference from other users of the same address, but it avoids changing a working configuration without a clear requirement.

Why allocation behavior varies by provider

Address retention depends on how a provider's pools are organized, not simply on whether it sells both shared and dedicated proxies. If continuity matters, get answers to these questions before buying:

  • Allocation support: Does the provider ever convert a specific shared address, or does every upgrade issue a new one, as on Node4?
  • Shared access: What happens to other customers currently authorized to use the old address?
  • Exit routing: Does the endpoint map to a fixed exit, or can it select different addresses?
  • Authentication: Will the current credentials and source-IP authorization remain valid?
  • Connection handling: Does the cutover preserve established connections, drain them, or terminate them?
  • Replacement rules: Under what documented conditions can the dedicated address later change?

Ask for the answers against the actual exit address, not just the product name. A general statement that dedicated proxies are static does not tell you whether a specific shared IP will be retained.

What to confirm before you buy

Send the observed exit address through the provider's support channel if continuity matters, and ask directly whether an upgrade preserves it or replaces it. Also ask for the effective cutover time and a rollback procedure. Do not interpret a successful subscription change as confirmation that routing and exclusivity changed the way you expected.

An infrastructure ownership claim is not a migration commitment. Owning IP blocks (which Node4 does, in the United States, Italy and Spain) tells you nothing about whether a specific upgrade keeps your address; ask that separately.

Verify the exit before and after migration

Use an IP-check endpoint you control or trust that returns only the request's public IP address as plain text. Test with a non-sensitive request; do not send application credentials or session cookies to an IP-check service.

The following Bash script uses curl and writes an observation to a file. Set PROXY_URL to your configured proxy endpoint and IP_CHECK_URL to your chosen plain-text IP-check endpoint. Supply credentials through your approved secret-management method rather than placing them in shell history.

#!/usr/bin/env bash
set -euo pipefail

: "${PROXY_URL:?Set PROXY_URL to your configured proxy endpoint}"
: "${IP_CHECK_URL:?Set IP_CHECK_URL to a plain-text IP-check endpoint}"
: "${PHASE:?Set PHASE to before or after}"

case "$PHASE" in
  before|after) ;;
  *) printf 'PHASE must be before or after\n' >&2; exit 1 ;;
esac

exit_ip="$(curl -q \
  --silent \
  --show-error \
  --fail \
  --connect-timeout 10 \
  --max-time 30 \
  --noproxy "" \
  --proxy "$PROXY_URL" \
  "$IP_CHECK_URL")"

if [[ -z "$exit_ip" || "$exit_ip" == *$'\n'* ]]; then
  printf 'Expected one nonempty line containing the exit IP\n' >&2
  exit 1
fi

printf '%s\n' "$exit_ip" > "exit-${PHASE}.txt"
printf 'Recorded %s exit: %s\n' "$PHASE" "$exit_ip"

if [[ "$PHASE" == after && -f exit-before.txt ]]; then
  if cmp -s exit-before.txt exit-after.txt; then
    printf 'Address unchanged across the migration\n'
  else
    printf 'Address changed, as expected on a new allocation\n'
  fi
fi

Save the script locally. Run it with PHASE=before before the plan change, then with PHASE=after once the new plan is active. If your endpoint or authentication changes, update that configuration before the second run.

The example uses a 10-second connection timeout and a 30-second total request timeout. Those are selected test limits, not provider performance specifications.

The script compares returned text; it does not validate that the response is a syntactically correct IP address. Inspect the response and make sure your endpoint reports the exit address in the same format on both runs.

Keep the baseline and result files with your change record, alongside the plan configuration identifier. Exclude passwords, tokens, and credential-bearing URLs from anything you store.

What the exit check proves, and what it does not

A matching (or changed) result proves what the IP-check endpoint observed for those specific requests. It does not prove that every destination receives traffic from that address, or, where an address is retained, that no other customer can use it.

Exclusivity requires an allocation commitment from the provider, not just a matching IP-check result. If you control a destination server, inspect its access logs as an additional check that your actual application traffic arrives from the expected address.

A gateway with destination-dependent routing needs particular attention. Test the destinations relevant to your workload rather than assuming a check against one endpoint establishes all routing behavior.

Move the workload without confusing IP and session state

Pause new work before replacing proxy configuration. Let existing work complete where the application permits it, then reconnect using the new or confirmed dedicated allocation.

Keep the application-side variables stable during the network test. Do not simultaneously replace cookies, change browser profiles, upgrade the HTTP client, and alter request scheduling. Multiple changes at once make a failure harder to diagnose.

Use this cutover checklist:

  • Record: Save the old exit address and current configuration securely.
  • Pause: Stop scheduling new jobs while handling in-flight work deliberately.
  • Change: Apply only the confirmed proxy and authentication changes.
  • Verify: Check the new exit and run an authorized application request against it.
  • Resume: Restart normal scheduling only after the acceptance checks pass.

For the application check, select a read-only action your account is authorized to perform. Avoid using a purchase, message, or other irreversible action as a connectivity test.

If you operate several workers, check that each worker received the intended configuration. A successful check from your laptop does not establish that background jobs, containers, or scheduled tasks use the same proxy settings.

Keep the old configuration available for investigation, but do not assume its credentials remain usable after the plan changes. A rollback that depends on restoring the shared allocation needs the provider's agreement, not just a saved configuration file.

Does a new dedicated address inherit the old one's reputation?

No. A new allocation is a new address, with its own history, not the shared one's. That cuts both ways: you leave behind whatever a previous neighbor did on the shared address, but you also start without any history of your own on the new one.

Where a provider does offer same-address conversion, keeping the address keeps the same history too. Dedicated allocation changes who is authorized to use the address; it does not remove a destination's existing records or restrictions associated with it.

If the migration is meant to resolve blocking, test the relevant destination on the new address rather than assuming a fresh IP clears every problem by default.

Will existing logins survive the upgrade?

A changed exit IP does not end a session by itself, but it is not a safe assumption either way. A connection can close during a configuration change, and a destination can require re-authentication independently of the source address.

Preserve authorized session state, reconnect deliberately, and test a read-only authenticated action. Plan for a session to need re-establishing rather than assuming continuity.

Is a sticky session the same as a dedicated IP?

No, they answer different questions. A sticky session pins one exit on a shared or rotating gateway for a bounded window; a dedicated allocation is a separate, exclusive IP you hold as long as the plan is active. Stickiness describes temporary exit persistence; dedication describes ownership of the address itself.

Do not substitute a sticky-session identifier for an actual dedicated allocation when continuity across sessions, not just within one, is what you need.

FAQ

Can I upgrade from shared to dedicated without changing my IP address?

On Node4, no: the upgrade always provisions a new address from the dedicated pool. Some other providers offer an explicit same-address conversion; confirm that in writing before assuming it applies to you.

Does buying a dedicated proxy automatically reserve my current shared IP?

No. A dedicated plan allocates its own address. If a provider does not explicitly advertise same-address conversion, assume it does not exist.

How do I check whether my proxy IP changed after an upgrade?

Compare the public source address reported through the proxy before and after the change, using the same IP-check endpoint both times.

Can curl prove that nobody else uses my dedicated proxy IP?

No. curl can show the exit address a destination observes, but exclusivity is a fact about the provider's allocation, not something a single request can confirm.

Will a dedicated upgrade remove a website's block on my old IP?

Only in the sense that you are no longer using the old address. A new dedicated IP starts with its own history, which is usually clean but is not a guarantee against every target.

Do I need to update my own IP-based access rules after the upgrade?

Yes, if the address changes, which it does on Node4. Update anything that whitelists your old shared address to the new dedicated one, then verify the rule still matches your application traffic.

Should I cancel the shared plan before testing the dedicated allocation?

Do not cancel a plan you still need for validation or rollback. Keep both active until the new dedicated address has passed your checks.

What verifying the exit actually settles

An unchanged proxy hostname is not proof of an unchanged public IP, and a changed hostname does not prove the address changed either. A gateway hostname can stay identical while its exit routing changes, and a new hostname can route to the same exit.

Compare the destination-observed address before and after, and treat that, not the hostname or the plan name, as the fact that settles whether your address changed.