IssueTracker

it seems very short sighted that in this era a service such as Google Compute is launched with no IPv6 support at all and 18 months down the line still no word, very poor indeed.

agree...

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.

Best Regards,
Josh Moyer
Google Cloud Platform Support

I'd also like to see IPv6 support!

we use logmein-hamachi on our google compute engine instance and broken because of no ipv6 support, can google give us some info is ipv6 is going to be available? otherwise we will move to other providers

IPv6 would be greatly appreciated. Thanks!

Can we have a guesstimate?

At least a rough estimate like: 1 year, 6 months... after the last solar eclipse of 2015?

i second it!

A growing number of mobile platforms are now IPv6 only. I'm planning new projects elsewhere due to the lack of response/interest from Google in this baseline feature.

Is it possible to allow 6in4 packets to pass through to GCE VMs, so that tunnels can be used as a stop-gap until native IPv6 is available?

I tried this, but it doesn't seem to work...

   http://stackoverflow.com/questions/31066205/how-to-allow-protocol-41-6in4-through-the-gce-firewall

IPv6 would be extremely nice.  This is one of the issues which is fully stopping me from moving my entire infrastructure over.

Any updates yet ?

No, there are no updates. Google, like most large infrastructure providers, have highly optimised hardware routers which only support IPv4. This is not a simple software update, otherwise it likely would have already been done.

This whole situation is understandable. The only issue is the lack of transparency from providers like Google. That said, it is very hard, because individual engineers in big corporations are not necessarily empowered to make statements about this sort of thing that aren't signed off by management, and management isn't necessarily inclined to spill what they see as secret technical details.

Thanks for the quick answer !

Google Cloud was built new cloud.
Should be built with the support for IPv6.

http://www.worldipv6launch.org was in 2012.

indeed, an IPv6 support would be welcome for VM instances

[Comment deleted]

Reply to #13: I sure hope the comment was ironic!

On MySQL instances they bragged about the introduction of an IPv6 address for each instance. No words on the fact that the address is futile (as in VMs are not available) if you don't access the instance from the outside world!

Reply to #18: I'm not sure what is so ironic. Google has expensive custom routers that probably don't support IPv6. Google has been behind the IPv6 launch quite heavily and I don't think they would be withholding support if there wasn't a good reason, and with IPv6 that reason is normally lack of router support. That said a actual response from the GCE team would go a long way towards helping the brand.

Google, if you are reading this, we understand this is hard, we just want some transparency here. Please don't turn into another Namecheap (e.g. they have been saying that they are working on DNSSEC for years when their upstream provider is actually the one blocking the issue).

This issue was ACKed (pun intended) by Google in October 14. This. Is an unreasonable turnaround time for an update.

As I said in MySQL instances you already have an IPv6 address (https://cloud.google.com/sql/docs/mysql-client#connect-ipv6)
 

How about adding a 6in4 protocol support at least (enable protocol number 41 in IPv4 to allow that, similar to TCP, UDP, and few other allowed protocols; why not all of them?). This would at least allow some workarounds, maybe not build proper website and services on top of GCE, but at least allow people to do some limited connections to the IPv6 world. Shouldn't be any less secure than any existing UDP based tunneling protocol.

Should I pay $0.01 each hour for Cloud SQL IPv4-Address in order to able to connect Compute Engine VM instance (has no internal IPv6) to Cloud SQL?

This is going to be a big issue for us in the near future.  We will have to migrate elsewhere if IPv6 doesn't arrive by then.

we need ipv6 support on the GCE.

Can we get ::1 (ipv6 localhost on lo) at least ? what prevents that ?

With the introduction of IPv6 on the Google Compute Cloud SQL instances it does seem that Google now has network infrastructure that can support IPv6. It would be excellent if Google could introduce support for IPv6 on their Google Compute Instances.

waiting for ipv6 for google coumpute engine for internal use with google cloud sql.

No update about this issue ?

No we dindnt get the error anymore! But in case happens again I let you
know. thanks!

Just discovered my ISP services switches between IPV4 and IPV6. So cannot configure Google compute engine firewall to work with my internet connection. Google, any update on rolling out compute engine and mysql for IPV6?

In MySQL instances there is already IPv6!

Is there a timeline for IPv6 implementation ??
Frankly speaking, I would not like to lose even a single customer connecting from IPv6 only devices. Eagerly Awaiting your response Google.

How embarrassing that Google released a cloud platform in 2016 and forgot to add IPv6 support... Deary me...

I agree with everyone, please make amends with immediacy

[Comment deleted]

http://www.wired.com/2016/06/barefoot-networks-new-chips-will-transform-tech-industry/

With Barefoot network in the picture, the implementation of the security mechanisms should be even more easier to achieve on IPv6.

Even from purely business perspective, No matter how much of cost is invested in "Custom Made IPv4 Routers", it just makes "No Sense" to ignore IPv6.

Your call.

My current project requires IPv4 and IPv6 for outbound connections. I would really like to settle on the Google Cloud, however I have to go where I have native IPv6 support provided by my cloud provider. I don't want to run this on Digital Ocean.

Common guys, it seems Google already has too much of business load and
customers to tackle to, lets not burden them further. Google, please feel
free to bring ipv6 as & when desired. We All will keep waiting patiently.
Now, I would like to resume my meditation trance please. Please wake me up
(before you go go) once Google has implemented ipv6.
:-p

I also need to use IPv6, and for GCE, I even cannot use tunnelbroker.net because of the firewall only allow tcp,udp and imcp and I cannot turn off the fire wall.

I don't think there can be any delay on this issue due to this:

https://developer.apple.com/news/?id=05042016a

As much as I would like to agree with #37, there's just too much movement on the issue.

cmon google even amazon supports this
https://aws.amazon.com/blogs/aws/now-available-ipv6-support-for-amazon-s3/
please bby girl can we please habe ipv6??

damm this thread was started at 2014 and its been 2 years Google is treating Google Cloud like how valve treats CS:GO - LIKE SHIT.

Saying your routers don't support this is bananas. You built your own os and hardware based on Broadcom and other custom silicon. You know it supports ipv6 you just haven't figured out the virtual firewall thing yet google. :(

IPv6 please

I’m Paul, a Product Manager for Google Compute Engine. First of all, I want to assure everyone here that we do hear your feedback, and Google does believe IPv6 is important.

As many people familiar with the history will know all too well, the timeline for IPv6 adoption industry-wide has stretched on for quite a long time. Despite years of efforts, worldwide adoption is still only about 14%, with US adoption the highest anywhere, at 29% (as reported by https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption&tab=ipv6-adoption). Given that, the broad majority of our customers tell us IPv6 is not yet a requirement for them. We’re aware that this is currently the most starred item on this tracker (!).

Customer priorities have a very significant influence on how we prioritize our work overall. Considering all this input, and because we at Google are trying to help increase the pace of transition, we are still prioritizing it highly, along with many other large feature requests that customers do ask for a lot.

Several people have made comments speculating about how easy or difficult it might be for us to add IPv6 support, but I don’t believe that any Google employees have actually made statements about implementation details here. Supporting IPv6 throughout our global infrastructure is much more work than simply “figuring out” a few small items of networking settings. If it were that easy, we would have done it already. :) If you’ve built your own v6 plan before, you’ll have some taste of this: it requires testing and potentially modifications at every level of the software and hardware stack.

Despite the continued lag in industry adoption, Google believes in the importance of major providers leading the way. IPv6 is definitely a priority that we’re working on, but we aren’t prepared to announce a timeline yet. Thanks for your feedback, and please hang in there. Note, you can also track the status of this item on our UserVoice forum, here: https://goo.gl/n0kg5j

Sorry, incorrect UserVoice link (it added an admin/ part for me). Correct link is:

https://googlecloudplatform.uservoice.com/forums/302595-compute-engine/suggestions/8518246-support-ipv6

We took effort accept Google Cloud platform for Mobile Backend. And 95% completed the entire platform and launched the Android App and it was working blazing with Google Compute VM.
When we submitted the iOS App to Apple App store they rejected it saying it is not compatible with ipV6 .
Now we are in very critical state like what needs to be done ? Move out of Compute Engine which is very tough after years of work.
Kindly let suggest as what has to be done ?

[Comment deleted]

I remember seeing something about IPv6 on Google Cloud Load Balancer. Maybe that will work for you? Can't find the link anymore.

For iOS apps, I am not 100% sure but I believe Apple allows usage of DNS64/NAT64 to access IPv4-only servers. Have you tried that ? Should be as easy as setting up a DNS and accessing the server via the hostname instead of a raw IPv4, the router should do the rest of the work to translate IPs.

You should also be able to try this setup from a mac by creating an IPv6 wifi network.

Google it has been a while and now the adoption rate is very high with with all of comcast US customers moving to IPv6 and likewise many other ISP globally, the adoption rate for IPv6 is greater than the 14% cited.  We have clients from US, Canada, UK, Germany, Italy, France, Australia cant access our services on GCE. Please we need a solution thanks

Microsoft Azure allready have IPv6 since 09/2016.
https://azure.microsoft.com/en-in/updates/ipv6-for-azure-vms/

Sorry but it is a shame..
That just Google IPv6 does not even have on the Timeline.
Google was once known for supporting IPv6. One of the first providers which one have an IPv6 Public DNS Service.

Why should the "small" ISP offer IPv6 if even the major vendors like Google do not fully support it.

Re: #49
Can you substantiate that IPv6 is available on Google Cloud Load Balancer? I can't find any indication of that, but would love to see it!

For anyone who didn't see the uservoice update, IPv6 for HTTP/S, TCP, and UDP loadbalancers now available in alpha: https://cloud.google.com/compute/docs/load-balancing/ipv6

Oops, that should say HTTP/S, SSL, and TCP*

For my application I require IPv6 for UDP and ICMP6 support.  Its the only way to properly detect the path mtu and avoid packet fragmentation.

Same here, I use a google cloud compute instance to host the back-end for a multiplayer game which means UDP is essential. Quite a few game app stores and publishers require that their users are able to utilize any server/networking over IPv6, so the result is we're getting rejected from certain app stores/publishers. We got on google play no problem though! (funnily enough)

I want it too!!!!!!!!

I decided to use digital ocean for my servers. It's funny to me one of the
largest internet companies in the world does not support ipv6. Just got
tired of waiting.

On Thu, 23 Nov 2017, 21:43 , <buganizer-system@google.com> wrote:

--


*Adam Sentner*
*Senior Product Architect*
Walk West

asentner@walkwest.com
o: 919.324.3925
c: 919.215.6068

Almost 5 years since first request made. Hopefully some works are in progress. Is there any updates other than ipv6 load balancer?

any updates? workarounds at least?

i'm not sure if this is related, but in my case all the services like http://ipv6-test.com/validate.php says everything is ok, after i've set up ipv6 load balancer and hosted domain on Google Domains. Though Apple review still b*tching about server unavailability from ipv6-only networks. Even their own recommended way of ipv6 testing (https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW21) works fine but they are rejecting app periodically, then accepting after few attempts.

it's been 5 years, this is frankly an embarassment. can't count the # of deployments I've *not* made in google cloud as a result of this. unsub'd from the issue as I don't expect an answer. Plenty of other providers who can offer native IPv6 in the interim.

This is very bad. After 5 years IPv6 is still not supported. No wonder people moving to AWS ..... ignorance of google engineers is likely major reason.

These comments are not helpful. IPv6 support is management decision. Ask your CEO to talk to whoever Google has in place to talk to CEOs (they are supposedly much more approachable by businesses than it used to be the case) and let them talk. Assuming the CEO can make a good case why your company needs IPv6 in the internal network... Thing is, the IPv6 load balancer covers a lot of ground, I would be genuinely interested what you truly need IPv6 in the internal network for.

In some countries ipv4 blocks of Compute Engine is blocked. Please enable ipv6 to make this product(GCE) available for such countries.

It's apparent Google is not taking any of this seriously. Between this and the lack of PTR control, I've moved all my infrastructure away. Damn shame.

@Google it is a disgrace that we are in 2018 and a google virtual compute instance cannot operate on an IPv6 network!

Your customers and your customers' customers are ashamed of their cloud choice.

I am just wondering if the ipv6overipv4 solution can be implemented on GCP instance [so far I managed to configure the instance but it wont let ipv6 requests getting out, as it seems to me]
reference: https://askubuntu.com/questions/990195/ipv6-tunnel-in-ubuntu-17-10

I have to just second, third, and fourth this. GCE is nice but it's quite asinine that they do not have IPv6 plumbed through yet. This is 2018 and literally everyone else has it, even budget VPSes.

The lack of IPv6 support is preventing me from considering GCP for certain workloads.  My use of IPv6 is not limited to web traffic, so the GCLB is not sufficient.

Need public IPv6 on instances, no need for internal instance to instance IPv6 (will do with IPv4 there).
Indeed, I need a wide range of UDP ports available from the outside wild world directly to some instances, without loadbalancer.
Ok for any alpha testing if necessary (I have a big bunch of production traffic - free users - that can afford a bad SLA).

Outbound ipv6 connectivity is required for some of my projects.

yapacagınız işe sokayım kaç gündür uğraşıyorum bunun için

any update please?

I'd love to pick gcp for my host servers in the USA but IPv6 is a must have

We offer all our customers one free IPv6 address and need direct support for it due to the configuration of our systems

this ticket can now go to the primary school, any status on this?

IPv6 is an advanced topic - they don't teach that in primary school.

On Mon, Jul 29, 2019 at 2:46 AM <buganizer-system@google.com> wrote:

With the introduction of additional charge per public IPv4 address, IPv6 support a must now.

https://news.ycombinator.com/item?id=20742965

At least provide a timeline or information regarding this or people will look elsewhere to host their projects.

Indeed, I'd be happy to go IPv6-only as I don't need IPv4 in my use case, now I'll have to pay for it because Google won't implement IPv6.

Technically, I think you can kind of use Google's load balancer (which
AFAIK is free for ipv6) to go externally ipv6-only (ie. you don't need
a global ipv4 address) provided you're ok with only being able to
handle incoming ipv6/tcp (or http/https/ssl) - among other things this
means you can get in via ssh over tcp over ipv6.  The setup is a bit
annoying though and non-trivial.  AFAIK, you need an instance group,
etc.  It's not as simple as saying point this ip:port to this port on
this vm.  Of course you still use private ipv4 within your project,
but it's only public ipv4 which is being charged for, so that's fine.
Unfortunately there's no *easy* way to figure out the remote user
endpoint - you can of course enable the proxy protocol extension, but
most apps (like sshd) don't handle it by default.  All that said
35$/year for an IP is super expensive - you can buy an IPv4 address
for life for less.

On Tue, Aug 20, 2019 at 5:24 AM <buganizer-system@google.com> wrote:

No you can't. Global LB(the only LB that supports ipv6) requires external IPs behind it.

Also you still will not have external connectivity on VMs without external IPs(at least on NAT). So Ipv6 absence requires you to have unwanted charges for Ipv4, just to have external connectivity.

I agree with comment #81. I've held off on adding my "Me Too" to this thread for a while now, however with the IPv4 charge appearing on our bills next April, we need Google to provide a clear roadmap for IPv6 for VM's. Cloud NAT works for some people, and the uservoice linked above mentions that IPv6 is available on their load balancers, however external IPv6 for VM's is a great alternative to external IPv4 addresses for many others, or it would be if it were available.

I've used the IPv6 offering in AWS and it's just as seamless as their IPv4 offering. With Google seemingly championing IPv6 adoption (why else would they host a tracker) it seems bizarre that this isn't available. Surely the GCP infrastructure is IPv6 capable‽ Somebody at GCP need to acknowledge this thread and provide some solid information, otherwise people will turn to their competitors (if they haven't already)!

Hello, I was try load balancer with ipv6 and it not work good with only 1 instance ,google tell me i need at least 3 instance for the load balancer working good. so i very dissapointed and no i thinking leave GCP and use AWS that have fully ipv6 support and not force people use load balancer for get ipv6 supoort and cdn support. It is a big shame that this big company not take this issue seriously in so many years now. IT is year 2020 and they servers support ony old IP adresses from year 1990. what a joke....here we come AWS! no more google cloud servers for me.

Concerning that its not supported though both Azure and Aws support it now.

Roadmap? Any info at all?

Roadmap?

I guess Google support doesn't actually reply to this huh? It's just sad to see GCP so far behind on the IPv6 curve.

This is ridiculous, Google was one of the first to promote IPv6, but itself cannot add it to its service.

Ipv6 please

The fact that you cannot get any native ip6 connectivity in the compute engine VMs is indeed a big big limitation.
It's not the first time that I have to select another cloud service provider that offers ipv6 because of this.
If you want to gain more market share this is for sure something to implement.

Many years on, I have given up waiting.

Is GCP team work on the issue anyhow ?  

Google has been vocal about supporting IPv6 for years (for example: co-organizing world IPv6 launch day, etc), so I'm sure they're well aware of the need and working on it.

The presence of the IPv6 tcp/ssl/http/https load balancer also suggests this - though of course it's just a stopgap measure.

The fact they're now charging more for IPv4 GCE addresses also suggests that they're probably running out of public IPv4 addresses (either for their cloud users or even possibly for themselves).

That said, you have to realize that IPv6 is most likely an absolutely massive undertaking.
At least that's been my experience with an IPv4 to IPv6 migration I've worked on.
It probably gets more and more complex as the size and age of the network and infrastructure increases.

It is well known that Google uses SDN - software defined networking - and that it's all in house - so presumably all that always running code has to be updated to support IPv6 - and this has to be done live without maintenance windows or outages across their entire network (when's the last time Google had a planned network outage for maintenance?).  Similarly all backend databases storing ips, and firewall rules, and probably billing, security, monitoring and UI's would have to be updated.

--

I've found this interesting cloud beta sdk documentation link:
  https://cloud.google.com/sdk/gcloud/reference/beta/compute/networks/subnets/create#--private-ipv6-google-access-type
mentioned at:
  https://github.com/googleapis/google-cloud-cpp/issues/3331

To quote:
  --enable-private-ip-google-access
Enable/disable access to Google Cloud APIs from this subnet for instances without a public ip address.

  --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE
The private IPv6 google access type for the VMs in this subnet. PRIVATE_IPV6_GOOGLE_ACCESS_TYPE must be one of: disable, enable-bidirectional-access, enable-outbound-vm-access

Which suggests something is happening, though I'm not exactly sure what...
It sounds like it's cloud api access over ipv6 from public ipv4 address-less VMs.

--

So I took the plunge and I enabled it on a subnet with my GCE VM:
  gcloud beta compute networks subnets update --private-ipv6-google-access-type=enable-outbound-vm-access --region=... ...

(not sure if you also need --enable-private-ip-google-access - I already had it on)

And I'm at least seeing RA's (tcpdump on my GCE VM):

42:01:0a:01:00:01 (oui Unknown) > 42:01:0a:01:00:02 (oui Unknown), ethertype IPv6 (0x86dd), length 110: (hlim 255, next-header ICMPv6 (58) payload length: 56) fe80::4001:aff:fe01:1 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 56
        hop limit 0, Flags [managed], pref medium, router lifetime 0s, reachable time 0ms, retrans timer 0ms
          source link-address option (1), length 8 (1): 42:01:0a:01:00:01
            0x0000:  4201 0a01 0001
          mtu option (5), length 8 (1):  1460
            0x0000:  0000 0000 05b4
          route info option (24), length 24 (3):  2001:4860:8040::/42, pref=medium, lifetime=90s
            0x0000:  2a00 0000 005a 2001 4860 8040 0000 0000
            0x0010:  0000 0000 0000

(note it claims to provide reachability to only a single /42 and not the full internet)
and then I ran 'dhclient -6 eth0' and I received a public ipv6 address:

# ip -6 addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1460 qdisc fq_codel state UP group default qlen 1000
    inet6 2600:2d0x:xxxx:xxx:a01:2::/128 scope global dynamic
       valid_lft 86436sec preferred_lft 86376sec
    inet6 fe80::4001:aff:fe01:2/64 scope link
       valid_lft forever preferred_lft forever

https://whois.arin.net/rest/net/NET6-2600-2D00-1.html
2600:2D00::/28
GOOGLE-CLOUD
*** The IP addresses under this Org-ID are in use by Google Cloud customers ***

I think the next step is 'ip -6 route add 2001:4860:8040::/42 via fe80::4001:aff:fe01:1 dev eth0' since my Linux kernel doesn't appear to be picking up the route from the RA by itself (not sure why).

I don't really know where to go from there, since I don't know of any ip addresses in that /42 subnet and I don't know what should or should not work...

AWS Fully support IPv6 and AWS cloud is lot older.
IPv6 is not a priority for Google this is what Google already write in this thread.

In AWS they still provide one(or more) /128 per host. You cannot properly use it to have ipv6 connectivity on containers on that host.
Hope to see prefix delegation here in GCP, so we will be able to get at least /60 or /56 and assign /64s to docker/podman networks.

I actually don't see any recent updates from Google in this bug.
Last one seems to be #46 / #47 from Nov 2016, and seems to talk about prioritizing it highly.

Following the link from #47 to https://googlecloudplatform.uservoice.com/forums/302595-compute-engine/suggestions/8518246-support-ipv6 shows a Sept 2017 update:

UPDATE: IPv6 load balancer endpoints are now GA. However, we continue to work on instance-level v6 addressing. Since I believe that at least some votes on this issue are for v6 all the way to the instance, I am leaving this issue open.

---

2600:2d0x:xxxx:xxx:a01:2::/128 seems to embed the ipv4 address of the VM (10.1.0.2 ie. :a01:2:) in such a way that it looks like /96 per VM might possibly maybe be a thing.

I'd love to see /60 as well, but there might simply not be enough bits for that?  They get a /28 from the registry... There's only 4 billion /60s in that, and that's probably nowhere near enough considering how many VMs they're likely to already be running (guessing millions?) and planning to be running (probably 10s or 100s of millions) -- and that they probably want some hierarchy for performance (you probably need at least a datacenter identifier in there) and/or operational sanity reasons.

Hi Google Team,

as many other users before me, I can't really understand why GCloud (being a IPv6 advocate and much older than AWS who has fully deployed that feature) is still at the queue of IPv6
It think it's on your roadmap, I just hope it doesn't get to us very late.


Kind regards

I would like to know what the roadmap for IPV6 is. There are bound to be cases in the near future where we can only interface to a customer system using IPV6 and in that case it becomes blocking. At minimum, a workaround could be provided by google for linux that provides a modification to the network stack on a VM instance to allow transparent use of IPV6 on the VM for connecting to external systems. That would be a minimum viable solution. For internal networking, I guess we don't really need IPV6 but it is mostly for connecting to external systems over IPV6. The other way around with application connecting to google cloud over IPV6 is already supported it seems so that is not an issue.

Does this update effectively complete this FR? https://cloud.google.com/compute/docs/ip-addresses/configure-ipv6-address

The linked documentation represents major progress on IPv6 support, but it's still highly limited. For example, because IPv6 is only supported for public IPs, you still have to carefully perform network planning and cannot e.g. decide after the fact that you want to pair two VPCs.

I would argue that what's been implemented is going to meet a lot of people's needs but it still doesn't represent pervasive IPv6 support.

Why would you want anything besides public ipv6 ips?  All it takes is a firewall to take care of anything external being actually able to reach your VMs.  And it's easy enough to set that up to be default deny.

Private IP addresses are somewhat privileged within GCP so they aren't exactly the same as a public IP with some firewall rules.

Is there a public roadmap about when IPV6 will be available in other regions? Do we know if they will get it at all?

In some GCE regions (see https://cloud.google.com/compute/docs/ip-addresses/configure-ipv6-address & specifically https://cloud.google.com/vpc/docs/subnets#ipv6-regions ) if you enable IPv6 for your network and VM, then you will be able to ping globally IPv6 reachable hosts.

However, you might not be able to reach (incl. ping) Google itself over IPv6 (this includes among others Google's IPv6 public DNS servers)...
Last I checked Google itself wasn't (yet??) reachable from GCE ipv6 capable VMs...

On Tue, Apr 26, 2022 at 10:03 AM <buganizer-system@google.com> wrote:

That seems like an unexpected state...
I don't expect this to be the correct behavior, I'll try some testing
today to verify.

External IPv6 subnet ranges now supported on almost all regions. You can't create external IPv6 subnet ranges in asia-southeast2 or asia-northeast3 at this moment.