Network

IPv6 is now dual-stack everywhere

As of 30 March 2026, every Atlantika location, plan and service is dual-stack. New instances receive a /64 by default, every public service has an AAAA record, and our own management network has been IPv6-only for six months. There is no surcharge and no separate IPv6 plan.

What changed

  • IPv6 is enabled in all twelve locations, including edge PoPs.
  • New instances get a public IPv4 address and a routed /64.
  • Existing instances can enable IPv6 from the portal without a rebuild.
  • Private networks get an IPv6 prefix alongside their IPv4 space.
  • Our DNS, API, portal and monitoring endpoints all publish AAAA records.

The addressing plan is documented in the customer portal. If you need a larger prefix than a /64 for a single network, ask support; we can route a /56 or /48 where the architecture makes sense.

What to check

Most applications work without changes, but “most” is doing some heavy lifting. Worth checking:

  • Services listening on :: as well as 0.0.0.0.
  • Firewall rules that were written for IPv4 only.
  • Monitoring checks that resolve A records but not AAAA.
  • Log parsers and rate limits that assume dotted-quad addresses.
  • Anything that stores client IPs in a fixed-width column.

A quick test from outside the instance:

$ curl -6 -I https://cloud.atlantika-company.uk/
HTTP/2 200
$ dig +short AAAA cloud.atlantika-company.uk
2001:db8:4a2::10

The address above is from the documentation range; your instance will have its own.

The gotcha that hides broken IPv6

Happy Eyeballs is helpful for users and unhelpful for testing. A browser will quietly fall back to IPv4 when IPv6 is broken, so a site can appear healthy while every IPv6 connection fails. Test explicitly with curl -6, and make at least one monitoring check use IPv6 only.

We found two of our own checks doing exactly this during the rollout. Both had been green for months while the IPv6 path was unreachable from one probe location. The fix was small; the lesson was not.

How to opt out

You can disable IPv6 per instance in the portal. The private network prefix can stay enabled even if the public address is off. We do not recommend opting out long-term, but we are not going to pretend there is only one correct migration schedule.

If something breaks and you are not sure whether IPv6 is involved, email support@atlantika-company.uk with the instance ID and the output of curl -6. We have seen most of the failure modes by now.

← All notes Written by Tom Avery, Head of Infrastructure