[SudoAlex]

Is this a single IPv6 address sharing the same /64 with stateless auto-configuration, or static?

The implementation is important, over the years I've had annoying experiences with certain providers trying to do IPv6 - but not getting things quite right:

Hetzner - Gave customers a /64, but using additional IPv6 addresses required setting up proxy NDP - which at the time was annoying as only more recent Linux kernels supported it. I believe they've improved on this since though.

OVH - Requires setting up a default route outside of your normal netmask - this isn't fun. We don't do this with IPv4 - so why do some providers do it with IPv6?

Linode - Enables IPv6 auto-configuration, so many servers share the same /64 by default, and they give accounts "pools" of /116 allocations. Sites like Google considers all of them to be part of the same /64 network - so your server will probably have trouble accessing certain resources if another server is doing excessive queries.

[akerl_]

Only tangentially related, but Linode gives each server a /128 by default, and gives out /56, /64, and /116 for free on request. I use a /56 to do my own subnetting and other fanciness.

[SudoAlex]

Sorry, forgot to mention that Linode does give more options now.

[zAy0LfpBZLC8mAC]

That Linode setup sounds dangerous - do they protect against NDP spoofing somehow?

[justincormack]

Hetzner is just a normal /64 now.