Match the address plan to your service
A cloud platform may value one contiguous range for simpler address management. A service aimed at local users may value the right geolocation first. Tell LARUS which outcome matters most and build your allocation around it.
One contiguous block
Choose a continuous range when address aggregation and centralized management come first. You receive capacity within one larger block. If its current geolocation differs from your deployment, announce it from the intended location and follow the geolocation update guide.
Location-ready addresses
Prioritized geographic registration selects addresses around the requested location. The result can be several smaller blocks rather than one large range—for example, /18 or /20 blocks instead of a single /17. This suits services where local recognition is a key part of the customer experience.
Make the trade-off work for your network
Bring your capacity, target city and announcement plan to LARUS. We can work through which option best supports your rollout. Geolocation providers refresh their own records, so test the services your customers actually use as part of launch.