TL;DRA dedicated static IP earns its cost when something depends on the address itself — inbound services, partner allowlists, outbound sending reputation, or a setup that is expensive to rebuild. If your work is short-lived and purely outbound, a shared or dynamic address is cheaper and perfectly adequate. Match the address type to the dependency, not to the marketing.
The question that decides it
Ask one thing: if this address changed tomorrow without warning, what would break? The size of that answer is the value of a dedicated static IP, and everything else is detail.
If the answer is 'nothing, I would reconnect and carry on', you do not need one. If the answer involves reconfiguring firewalls, emailing a partner, or rebuilding an environment, you do.
Workloads mapped to what they actually need
| Workload | Needs a dedicated static IP? | What matters most |
|---|---|---|
| Hosting a reachable service (web, API, database, game server) | Yes | Inbound reachability at a stable address; clean reputation |
| Partner or API allowlisting | Yes | The address never changing under you |
| Outbound email or notifications | Yes | Sending reputation you own, not inherited from neighbours |
| A long-lived development or staging box | Usually | Stable SSH access; not rebuilding tooling around a new address |
| An egress address a business needs to be fixed and auditable | Yes | Provenance you can document; exclusivity in writing |
| Short-lived batch jobs, purely outbound | No | Price. Buy the cheapest thing that runs |
| Anything where you would just reconnect if the address changed | No | Price, again |
Where the address comes from matters separately
'Dedicated' and 'static' describe your relationship to the address. Provenance — which network it was allocated from — is a third, independent property, and it is the one that decides how third-party services treat your traffic.
An address on a real consumer ISP access line, a datacenter block, and a shared pool can all be dedicated and static. They are not interchangeable. If provenance matters to your workload, verify it rather than assuming it.
Five questions to answer before you order
- What breaks if the address changes? This sets your budget for a dedicated static IP.
- How much upstream do you actually need? Consumer access lines are asymmetric — the number that limits you is upload, not download, and it is shared with others on the same line.
- Is the address exclusive, in writing? Lookups cannot tell you this; only the contract can.
- What happens when an address gets flagged by some third-party service — does the provider swap it, and at what cost? Addresses are consumables, and this question is much cheaper to ask before you order.
- How is the machine recovered when the site loses power or connectivity? Ask specifically whether out-of-band management runs on a separate line from the service traffic.
Being honest about the ceiling
A consumer access line is asymmetric by design. On our own lines we measure roughly 400 Mbps down and around 20 Mbps up, and the upstream figure is what a customer experiences, shared with the other customers on that line.
That is comfortable for control panels, APIs, remote development, and most business tooling. It is not the right product for high-bitrate video, large file synchronisation, or bulk transfer, and we would rather say so before you order than after.
Frequently Asked Questions
Do I need a dedicated IP for a small side project?
Only if something depends on the address itself — an inbound service, an allowlist, or sending reputation. A purely outbound side project runs fine on a shared address, and buying on price is the right call there.
Why is upload speed the number that matters?
Because data has to leave the server over the same line to reach you. On an asymmetric consumer line the download figure describes what the server can pull in; the upload figure describes what you actually receive, and it is shared with others on that line.
Is a dedicated static IP worth paying extra for?
It is worth it when an address change would cost you real work — reconfiguring firewalls, contacting partners, rebuilding an environment. It is not worth it for throwaway or purely outbound tasks.
What should I ask a provider before ordering?
The specific IP you will get, whether it is exclusive in writing, what happens when an address is flagged, the measured upstream on that line, and whether out-of-band management runs on a separate line.
Does it matter which state the IP is in?
Usually less than people expect. For most workloads, allocation source, exclusivity and stability decide the outcome; the state matters mainly for region-restricted services or latency to a specific place. Check whether yours is one of those before paying a premium for a location.
Updated 2026-08-25 · Back to Guides · View plans →