DO Ideas 2

ipv6 addresses

Hi. Do you have a plan on providing ipv6 addresses? They are quite useful and necessary in some circumstances.

  • Wang Guoqin
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    Today we are excited to announce the availability of IPv6 in our newest region, Singapore. Customers can now enable IPv6 on existing droplets without the need for a reboot or add IPv6 during droplet creation. We've also announced this via our blog: https://www.digitalocean.com/company/blog/announcing-ipv6-support-in-singapore/ The blog contains links to a few community articles to help customers get started in using IPv6 and also with a few FAQ items related to IPv6. The biggest questions that customers may have is when IPv6 will be available in other regions. This process has already begun. We launched in Singapore first because it runs on our new v1.5 backend code which was completely rewritten from the ground up. Now that it's been in production for several months we have begun the process of migrating our existing regions over to the new code. The first region to under go the migration is our SFO1 region. Also, all new datacenters that are opened will support IPv6 from day one. In regards to Europe we will be launching several new datacenters in the next 1-3 months which will provide IPv6 availability to the European region in that time frame. We don't have an ETA on the migrations yet because it is a large process that we have to undergo for an entire datacenter and as we make more progress we will be able to better estimate the work that is involved. All new creates in the SFO1 region are now running on the v1.5 code so the entire process is already well underway. Sorry for the many delays in product updates and announcements, it is one of the challenges that we faced as the company began to scale next year. I think that journey that we went through is not unique to us but something that many other startups have faced. We've discussed some of the challenges with other founders and they've related similar episodes so we will look to put together a blog regarding that so that hopefully it can shed some light for our customers on the process as well as perhaps provide some guidance to other companies and startups as they go through their own challenges and maybe they'll be able to avoid some of the pitfalls that we encountered. Thanks, Moisey Cofounder Digitalocean
  • Attach files
  • RobM commented
    September 11, 2018 20:02

    Far too few IPv6 addresses compared to Linode. No reason for it.

  • Andrew Burns commented
    September 11, 2018 20:02

    It would be more useful if you could manage the rdns of the ipv6 subnets - at the moment, you can just change the rdns of the hostname for both ipv4 and ipv6.

  • Scott Gruby commented
    September 11, 2018 20:02

    I'm on NYC1; will this data center get IPv6 or will I have to recreate my droplet in another data center? I'm grandfathered into unlimited traffic, so I don't want to lose that by setting up another droplet.

  • Craig McQueen commented
    September 11, 2018 20:02

    Once customers can request dedicated /64 or /56 subnets, it would also be good if customers can manage the reverse DNS for the subnet.

  • Craig McQueen commented
    September 11, 2018 20:02

    It's a great step. I wouldn't consider it "completed" until customers can request dedicated /64 or /56 blocks.

  • Anonymous commented
    September 11, 2018 20:02

    @Anonymous

    No, it is production quality, although yes it is only on one DC. Please give them a break.

  • Anonymous commented
    September 11, 2018 20:02

    Hahahaha!!! Closed?? You people are nuts. You consider thios closed when you put it in ONE datacenter and is still in testing phase.

    Come on! Get with the real world. This is total BS!!!!!

  • Andrew Starr-Bochicchio commented
    September 11, 2018 20:02

    IPv6 is now available in our SGP1 datacenter. Check out the announcement for more info and future plans:

    https://www.digitalocean.com/company/blog/announcing-ipv6-support-in-singapore/

  • Scott Mustard commented
    September 11, 2018 20:02

    We hope the beta went well over the last 2-3 weeks. Our company is looking to try out DigitalOcean but requires IPv6. Is it now available?

  • Jan Krupa commented
    September 11, 2018 20:02

    Honestly I don't believe digitalocean's ETAs. In 2012 they promised that custom kernels will be released "soon". I can see similarities here with the IPv6. I'm already testing other providers.

  • Louis Matthijssen commented
    September 11, 2018 20:02

    And yet another loose promise.

  • Anonymous commented
    September 11, 2018 20:02

    Tomorrow, it will be fully 3 weeks since the announcement above...

  • Florian Strankowski commented
    September 11, 2018 20:02

    You cant take part at the beta and you cant get grandfathered nowadays because thats a special award for the first users here.

  • Mick O'Rourke commented
    September 11, 2018 20:02

    Any updates on the beta?

  • Dmitry commented
    September 11, 2018 20:02

    I'm interested to join 'ipv6 beta test' - but I'm not 'grandfathered' yet.
    Can I?

  • md_5 commented
    September 11, 2018 20:02

    Prefix size is mostly irrelevant, a /112 still provides 65K addresses. The minimum registry allocation is a /32 which provides a whopping 4 billion /64 subnets, so there is no reason to only provide a /96 anyway. Linode etc can offer a routed /48 last I checked.

  • Anonymous commented
    September 11, 2018 20:02

    Thomas, it is not as trivial as you think it is. Obtaining IPv6 addresses from ARIN and other RIRs was in fact the easy part for them. They have to make sure that their BGP sessions are setup correctly for IPv6, and are sufficiently stable. This goes for all their other software too.

    Most VPS providers will provide at most 5 (or maybe more if you're lucky) IPv6 addresses; RamNode (for example) uses only a /96 for its customers. /64 is really what you would find with dedicated servers, not VPS.

  • Thomas Fjellstrom commented
    September 11, 2018 20:02

    wait, no update in ages, and I hear we only get one ipv6 address? that is totally against the ipv6 idea. getting an entire /64 shouldn't be a problem in the slightest. even if its per server. How can it possibly be taking this long? You set up an ipv6 auto config server and hand everyone a fixed range. Then linux auto gets an ipv6 address.

  • Jason Kurtz commented
    September 11, 2018 20:02

    How's the beta going?

  • Anonymous commented
    September 11, 2018 20:02

    Do we get a full /48 or a /64 or only a single IPv6 address?

  • Rémi Rampin commented
    September 11, 2018 20:02

    Wait, is this still going on? Discussions about IPv6 in 2012 were promising, but in 2014 this is a joke. I have obviously moved to another provider since...

  • Steve Sobol commented
    September 11, 2018 20:02

    Honestly Moisey, it's too late. Even after you roll it out, the problem you and your staff said it would solve for me, won't be solved.

    Tired of the lies and BS; already looking at other VPS providers.

    Thanks for nothing.

  • Steve Sobol commented
    September 11, 2018 20:02

    Oh, imagine that. No updates from DO in almost six weeks! Would love to be surprised, but I totally expected this.

  • Steve Sobol commented
    September 11, 2018 20:02

    I personally am tired of being lied to. I'm waiting for IPv6 because I was told I could not have more than one v4 IP per droplet, and I have SSL websites I need to set up. Now I'm told that EVENTUALLY, when IPv6 is rolled out, I still get only one IP, and there is still no ETA for v6 anyhow, after two years.

    Moisey, if I treated my customers the way you treat yours, I'd be out of business. You should be ashamed of yourself.

  • Mick O'Rourke commented
    September 11, 2018 20:02

    Hi Moisey,

    I've been holding of on using Digital Ocean in a more permanent way - as have others I know - pending IPv6 support.

    Glad to hear it's the beta is close to starting and that we'll hopefully see a production release soon.

    Cheers

  • Moisey Uretsky commented
    September 11, 2018 20:02

    We're doing a bit more testing this week but hope to start the beta test within the next 2 weeks in Singapore with our original grandfathered users.

    Thanks!

  • ivan matimatik commented
    September 11, 2018 20:02

    What about this beta thing? Was it started, are there any results or ETA so far?

  • Jason Kurtz commented
    September 11, 2018 20:02

    I'd like to be part of the beta.

  • Yong Jie Wong commented
    September 11, 2018 20:02

    I have knowledge of IPv6 technologies and have a dual-stack connection at home, and I would like to participate in the beta. May I know how can I be part of the beta?

  • Aritra Dalal commented
    September 11, 2018 20:02

    Hi,

    Thanks for the update. But it's already been a little late!

    I understand that undertaking such a feat is difficult, but your promises have had negative effects. Recently SixXS blocked my IPv6 tunnel to DO's IP addresses, stating that you guys already provide IPv6, or so you told them that you did, and they refused to reallow my tunnel to back live. I know, it's easy enough to switch providers, but tell DNS that. Yes, this has caused problems and complaints already.

    All I'm saying is that stop apologising if you honestly don't mean it. One of my main reasons of sticking with you guys is for your promises for IPv6, which would've made you pioneers of sorts. Now, you're one of the last ones in the field to even start thinking about IPv6.

    Sigh.

  • Anonymous commented
    September 11, 2018 20:02

    Well, lets see, it has now been almost 2 years since we heard, "next quarter". So coming soon should be sometime next year at the earliest. But that is just for Singapore Region.

    I figure at your pace and ability to lie to your customers, us here in the NY data centers might be lucky and see it sometime in the next decade.

    Please quit feeding us bullshit!!!

  • Vitaliy Vasilenko commented
    September 11, 2018 20:02

    Please, add to AMS region support

  • Shouyang Li commented
    September 11, 2018 20:02

    How to apply for the limited public beta?Have native IPv6 in China.

  • Anonymous commented
    September 11, 2018 20:02

    http://status.digitalocean.com is giving some hints....

  • Angela Kristine Branaes commented
    September 11, 2018 20:02

    I must admit that the lack of IPv6 support is making me seriously consider switching hosting company.

  • Ronny Lam commented
    September 11, 2018 20:02

    Nope, IPv6 is not on the job requirements.

  • Anonymous commented
    September 11, 2018 20:02

    Hey look, Digital Ocean is hiring a Senior Network Engineer! Maybe they might now get IPv6 implemented!! https://www.digitalocean.com/company/careers/senior-network-engineer/

  • Ariel commented
    September 11, 2018 20:02

    The only complaint about the excellent digital ocean service is the lack of ipv6 support for the droplets.

  • Florian Strankowski commented
    September 11, 2018 20:02

    Its pretty sad. I'm one of those early adopters, was within DigitalOcean once it came onto the market and this forum was pretty neat to get in touch with the developers and support. Suggestions have been implemented fast once they reached the critical mass of votes, support answered and gave timelines.

    Nowadays, once DO gets bigger and bigger, the community who actually build DO up and made it popular, is missing the respect from the officials and wont even receive answers here.

    A sad time for DO.

    /fs

  • Joni Kähärä commented
    September 11, 2018 20:02

    Nah, too busy setting up new data centers.

    Seriously, I don't think they pay much attention to this board any more. Perhaps the backlog of things that they had promised would be implemented got too dense and they just stopped giving a fsck.

  • Carl Rosengren commented
    September 11, 2018 20:02

    "But we will definitely have IPv6 fully rolled out in 2013" Well Mr Uretsky, it's 2014 now and I can't see that ipv6 is available yet. So any updates on an ETA?

  • Florian Strankowski commented
    September 11, 2018 20:02

    PING

  • Yasen Simeonov commented
    September 11, 2018 20:02

    Hello,
    I am planning to move some of my servers here. The lack of IPv6 is something stopping me to do so. I am looking forward to see it's implementation soon.

  • Gnatyuk Roman commented
    September 11, 2018 20:02

    Some sort of necroposting, sorry.
    Any updates on this?

  • Anonymous commented
    September 11, 2018 20:02

    Please RT, they didn't even respond so far!

    https://twitter.com/badipscom/status/431520578344726528

  • Anonymous commented
    September 11, 2018 20:02

    Was really surprised - first VPS provider I bought something from that doesn't do v6 ...
    Guess I need to go elsewhere when there isn't even an ETA.

  • Anonymous commented
    September 11, 2018 20:02

    Funny that people have been asking for this since at least 2012 and all they can say is they have thought about it. You would think that after almost 2 years they could at least give a better time line. But I guess taking time and money to actually deploy it would make too much sense and take away from the profits even though it is what customers are wanting.

  • Florian Strankowski commented
    September 11, 2018 20:02

    No there is no official update available yet. You may try to ask them via Twitter @DigitalOcean.

  • Simon commented
    September 11, 2018 20:02

    Is there any official update?

  • Florian Strankowski commented
    September 11, 2018 20:02

    IPv6 wont be implemented before 2020.

  • Anonymous commented
    September 11, 2018 20:02

    So when will be avalaible?

  • Dan Victor commented
    September 11, 2018 20:02

    Bump for unlikely response...

  • Florian Strankowski commented
    September 11, 2018 20:02

    @Anonymous: Enjoy waiting several days, i wait 2 years now and nothing has changed.

  • Joni Kähärä commented
    September 11, 2018 20:02

    I think it's strange that DigitalOcean representatives can't give _any_ feedback here – and it's not just this one issue, they're very quiet on some others that I've been watching, too. Either they a) don't care, or b) are too busy to keep us updated (which is just another form of not caring, IMO).

    The site is called Uservoice which is only fitting as it's only the users who are talking.

  • Maykel Moya commented
    September 11, 2018 20:02

    I got an answer via Twitter (https://twitter.com/mmoyaro/status/422361375101304832):

    "the current update with IPv6 is that it's in development - we'll provide a more accurate delivery date soon. Thanks for addressing"

  • Anonymous commented
    September 11, 2018 20:02

    I HAVE BEEING CONSIDER CHANGE THE VPS PROVIDER B/C IPV6 NOT SUPPORTED HERE..
    THE NOTIFICATION SHOWS THAT THIS UPDATE WILL IMPLOY IPV6, IT IS EXCITED!
    I LIKE DO,I WILL WAIT SEVERAL DAYS...

  • Anonymous commented
    September 11, 2018 20:02

    Filip: you can't use cloudflare if with your own dns infrastructure and you can't ssh to your vps via cloudflare.

  • Filip Oščádal commented
    September 11, 2018 20:02

    you can use CloudFlare IPv6 proxy meanwhile

  • Anonymous commented
    September 11, 2018 20:02

    Digitalocean guys - come on. Unlike many of the other posters, IPv6 isn't at all critical for me, but your lack of response is starting to upset your customers.

    If IPv6 isn't ready, that's ok! A simple update of the status would go far in easing your customers' minds!

  • Peter commented
    September 11, 2018 20:02

    I understood the service is good, but no IPv6 is a no-go for me.

  • Stephen Bryant commented
    September 11, 2018 20:02

    *Please* implement IPv6! I love DigitalOcean, but I can't wait much longer. The lack of IPv6 is already causing me major issues.

  • Drake Wilson commented
    September 11, 2018 20:02

    Quite. If I can't put services up on IPv6 addresses it's really hard to integrate them with my network architecture.

  • Adam Peacock commented
    September 11, 2018 20:02

    This is one of the big things preventing me from moving to DigitalOcean - I try to deploy all my services on both IPv4 and IPv6, but without any IPv6 support from DigitalOcean I cannot do that.

  • Florian Strankowski commented
    September 11, 2018 20:02

    Please update this!

  • Daniel Olewine commented
    September 11, 2018 20:02

    Any IPv6 update?

  • Alexander commented
    September 11, 2018 20:02

    Any news?
    DO this is bad, really bad. We need IPv6.

  • Florian Strankowski commented
    September 11, 2018 20:02

    Nearly end of the year. News please.

  • Anonymous commented
    September 11, 2018 20:02

    Also a vote for IPv6 here.

  • Florian Strankowski commented
    September 11, 2018 20:02

    Seriously, can we please get an update on this topic?

  • Anonymous commented
    September 11, 2018 20:02

    It's almost 2014. Updates?

  • Florian Strankowski commented
    September 11, 2018 20:02

    Any updates?

  • Jason Kurtz commented
    September 11, 2018 20:02

    Is the delay of IPv6 due to peering issues (outside of DO's control)? Another provider I know of has cited peering issues as the reason for their delay and I wondered if it was the case here as well.

  • Marek B. commented
    September 11, 2018 20:02

    What is really real state when we can expect a native IPv6 in AMS? There is a possibility at least get an account beta testers for IPv6?

  • Jonathan H commented
    September 11, 2018 20:02

    I was hoping the arrival of AMS2 might have brought IPV6 with it. After all, we're way after the October beta time which hasn't happened yet. Any news?

  • Henrik Nordstrom commented
    September 11, 2018 20:02

    With all your talk about IPv4 shortage and IPv6 being the solution I kind of assumed IPv6 would be in place before signing up, and now find that it's not... but at least you are working on it.

  • Erik Gävert commented
    September 11, 2018 20:02

    This is a must have for me to migrate.

  • Alexander Zaremba commented
    September 11, 2018 20:02

    I would like to be ipv6-beta-tester too.
    Is it possible?

  • Georg Sluyterman commented
    September 11, 2018 20:02

    I have server at Digital Ocean and I am currently using a HE.net tunnel.

    I too am interested in an ETA for native IPv6 and I am looking very much forward for you to make it available (the lack of the feature makes you cloud quite old fashioned in comparison with e.g. Rackspace).

    Remember to have reverse-DNS working for IPv6! :-)

  • Anonymous commented
    September 11, 2018 20:02

    any updates? would really like to migrate off linode but their ipv6 deployment is really well done.

  • Markus Wiegand commented
    September 11, 2018 20:02

    Any news? You can invite me for the beta. My vps are in amsterdam.

  • Benjamin Reed commented
    September 11, 2018 20:02

    Is there any updated ETA on this? This is really incredibly important for me.

  • Anonymous commented
    September 11, 2018 20:02

    Pleaseee i need ipv6 just for ssh !

  • Ryan Olson commented
    September 11, 2018 20:02

    Personally, take your time with IPv6 - I would rather you test it inside and out before you even consider beta testing it from specific pods. Thanks for letting us know you are still listening to us!!!

  • Säl commented
    September 11, 2018 20:02

    Any updates? October is running away!

  • Orthocenter commented
    September 11, 2018 20:02

    I would like to be ipv6-beta-tester too :)

  • Skovoroda Nikita commented
    September 11, 2018 20:02

    Can you please enable IPv6 on speedtest-nyc2.digitalocean.com, if IPv6 is already enabled for NY2 region?

  • Ben commented
    September 11, 2018 20:02

    Vitaliy: there's always Hurricane Electric tunnels. I believe HE has a IPv6 tunnel POP in Amsterdam, so using the tunnel might not hurt that much. Probably not as good as NY2 (where HE's NY IPv6 POP is < .5 ms away), but it should still be usable.

  • Vitaliy Vasilenko commented
    September 11, 2018 20:02

    I need v6 address in AMS DC

  • James Cloos commented
    September 11, 2018 20:02

    +1 on beta testing.

  • Tobias Gruetzmacher commented
    September 11, 2018 20:03

    So, any chance to get notified when IPv6 is available?

  • Jason Kurtz commented
    September 11, 2018 20:03

    I'd enjoy being a beta-tester for IPv6 as well.

  • Stephane commented
    September 11, 2018 20:03

    I would like to be ipv6-beta-tester too :)

  • Bruno Delbono commented
    September 11, 2018 20:03

    I tried creating a droplet on nyc2. Private networking is enabled but not IPv6. Can I also put my name down for beta testers?

  • Vincent commented
    September 11, 2018 20:03

    ipv6 is already enabled for me on NYC2, try creating a droplet there.

  • Ivan Strokanev commented
    September 11, 2018 20:03

    I would like to be ipv6-beta-tester too :)

  • Bosse Klykken commented
    September 11, 2018 20:03

    I'm set up with IPv6 through a tunnel broker at the moment, but it is not ideal for my operations, and I would really like an IPv6 option soon. Charge for it if you must.

  • Raj Amal commented
    September 11, 2018 20:03

    I would like to be on beta list

  • Rémi Rampin commented
    September 11, 2018 20:03

    "Private networking" have been released. I'm still waiting on this.

  • Anonymous commented
    September 11, 2018 20:03

    Any update on this? We're already in September 2013.

  • Kolbjørn Barmen commented
    September 11, 2018 20:03

    Great, looking forward to this.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We will be releasing private networking very shortly in our NY2 region and then working on releasing it to all of our regions.

    Once the initial rollout of the first region is finished we'll be moving to get IPv6 enabled in our NY2 region first and are targeting an October ETA for the first public beta!

    Thanks!

  • Skovoroda Nikita commented
    September 11, 2018 20:03

    IPv6 support is the only thing that stops me from migrating to Digital Ocean.

  • Ben Uretsky commented
    September 11, 2018 20:03

    We have to delay IPv6 for at least 1 month, the new updated beta access is set for October 2013. The good news is that we are releasing private networking access in our NY2 datacenter in September. This will bring us 1 step closer to having IPv6 connectivity. We have already subscribed for v6 access with our network providers and continue to build out the features to release it publicly.

    Due to heavy demand and other issues we have to push the timetable for IPv6, and we are updating to October 2013.

    Thanks for being patient, and we're working on this as an important improvement to our overall service.

  • einarjh commented
    September 11, 2018 20:03

    It is September 1, 2013. Any news on IPv6?

  • Ben commented
    September 11, 2018 20:03

    We're getting pretty close to Sep 1. Any progress?

    Meanwhile, I'm using a Hurricane Electric tunnel on my droplets in NY1. HE's NY Tunnel server seems to be pretty close to NY1. Yesterday, I noticed that my IPv6 ping time to a DO droplet is less than my IPv4 ping time, despite using tunnels on both ends (Freenet6 from home, HE at DO). Those of you with a small number of droplets might want to look at an HE tunnel if DO misses yet another predicted deadline.

  • Paul commented
    September 11, 2018 20:03

    any news regards IPv6 addresses?

  • Anonymous commented
    September 11, 2018 20:03

    also want ipv6.... i will sign up as soon as you have it.

  • Helge Olav commented
    September 11, 2018 20:03

    Want IPv6

  • Kye Alan Russell commented
    September 11, 2018 20:03

    Well? Any news? I want to pull all my services from Linode, but v6 is a definite deal-breaker.

  • Anonymous commented
    September 11, 2018 20:03

    I would also like to be on the beta list. Please!

  • Benry Yip commented
    September 11, 2018 20:03

    Will beta access information be posted here or on the main site?

  • Andrew van der Stock commented
    September 11, 2018 20:03

    I will migrate my servers once IPv6 is enabled. Any news on when it will be available?

  • René Moser commented
    September 11, 2018 20:03

    Can not migrate my servers because lack of native IPv6 connectivity. Bye.

  • Jonathan H commented
    September 11, 2018 20:03

    I'm also keen to try the beta. I was just wondering why you don't hook up with someone like Cloudflare to take advantage of their auto-IPV6 system?

  • Michael commented
    September 11, 2018 20:03

    Is there anything one can do to join the beta? :)

  • Ben Uretsky commented
    September 11, 2018 20:03

    We're glad to say that IPv6 will be available by September 1, 2013 - expect beta access earlier. Will keep you guys posted and would love to get your feedback on network reachability.

    Cheers.

  • Sven commented
    September 11, 2018 20:03

    I would really appreciate IPv6 for droplets...

  • Vikarti Anatra commented
    September 11, 2018 20:03

    so, WHEN?

  • Alex commented
    September 11, 2018 20:03

    any updates about ipv6 ?

  • Kolbjørn Barmen commented
    September 11, 2018 20:03

    Lack of native IPv6 connectivity is another reason I cannot really make use of DO today.

  • Adam Harrison commented
    September 11, 2018 20:03

    Lack of support for IPv6 is preventing us from adopting your service too. It would be helpful for those of us involved in supplier selection and deployment planning if you could give us a rough estimate - is it Q3? Or are we looking at 2014? Thanks!

  • JC commented
    September 11, 2018 20:03

    Please implement IPv6 connectivity soon!

  • Jason Kurtz commented
    September 11, 2018 20:03

    Any comments on how you plan to delegate v6? It sounds like a bunch of us are more concerned with that than with private networking.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We're working on private networking first so as that starts getting rolled out into production then we'll switch over to IPv6 =]

  • Vitaliy Vasilenko commented
    September 11, 2018 20:03

    Hello!
    I need a IPv6 address in NY Datacenter

  • Jason Kurtz commented
    September 11, 2018 20:03

    Any updates on this? I guess this is the thread I need to follow obsessively now that the other one (about AMS 512MB/1GB droplets) has been closed.

  • Giorgos Mavrikas commented
    September 11, 2018 20:03

    It's the middle of 13Q2. Do you have any updates on IPv6?

  • Florian Strankowski commented
    September 11, 2018 20:03

    Any Update?

  • Zeeshan Ahmad commented
    September 11, 2018 20:03

    any updates about ipv6 ?

  • Moisey Uretsky commented
    September 11, 2018 20:03

    Thanks for the feedback and we are working on this we also have another request for IPv6 that was submitted earlier and is more up-voted so we are closing this one in favor of the original to return your votes to you.

    Thanks

  • Daniel commented
    September 11, 2018 20:03

    Hello, hurry up with european datacenter IPv6 allocation please, i would really like to be your customer and use IPv6 !

  • Moisey Uretsky commented
    September 11, 2018 20:03

    The growing number of DCs doesn't impact our move to IPv6 as its a necessity and ARIN will be out of IPv4 early next year if not even possibly sooner followed by Latin America shortly there after.

    Thanks

  • James Cloos commented
    September 11, 2018 20:03

    Will you get a /32 for SFO or advertize smaller chunks from each datacenter in ARIN territory?

    Will you get a RIPE /32 or advertize chunks of the DIGITALOCEAN-V6-1 ARIN block in RIPE territory?

    Put another way: will the (welcome) growing number of datacenters have a negative impact on getting native v6 up and running?

  • James Cloos commented
    September 11, 2018 20:03

    arin announced 2604:A880::/32 (DIGITALOCEAN-V6-1) today:

    http://whois.arin.net/rest/net/NET6-2604-A880-1.html

    That looks good for /64s for each droplet. (They can always get another once they hit four billion concurrent droplets. ☺)

  • Trevor Bergeron commented
    September 11, 2018 20:03

    To +1 Anon's comment, it would be great if we could get /64 blocks instead of just single addresses! There should be plenty of address space, and even if it's only by request it would be super helpful in many ways.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We've received our first IPv6 allocation and given the issue with IPv4 in EU we are moving forward with progress on this as we have more updates we'll make them available.

  • Anonymous commented
    September 11, 2018 20:03

    Do you know if you'll provide a /64 or just one single IPv6-address?

  • NEC Administration commented
    September 11, 2018 20:03

    Our target and users will primarily be academic users on campus networks with IPv6/Internet2, so having this would be very useful!

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We have an already open request for IPv6 which has more votes so closing this one in favor of the original.

    Thanks

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We will be rolling out IPv6 as soon as possible and it's certainly true that native IPv6 support leaps and bounds better than any kind of other config that is setup.

  • Anonymous commented
    September 11, 2018 20:03

    That might work on clients as a temporary solution but you want native ipv6 on your servers. Also 6to4 is mostly crap. There is no point in moving to DO if what you got right now is better.

  • Anonymous commented
    September 11, 2018 20:03

    since you have a public IPv4 you could use this (on rhel6)
    # Remove if exist the value then add the wanted value to avoid bugs
    sed -i 's/NETWORKING_IPV6=.*$//g' /etc/sysconfig/network
    echo 'NETWORKING_IPV6=yes' >> /etc/sysconfig/network
    echo 'IPV6_DEFAULTDEV="tun6to4"' >> /etc/sysconfig/network

    export INTERFACE=`route -n | awk '/^0.0.0.0/ { print $8 }'`
    IPV4=`cat /etc/sysconfig/network-scripts/ifcfg-$INTERFACE | grep IPADDR | cut -d '=' -f 2`
    cat <<EOF>> /etc/sysconfig/network-scripts/ifcfg-$INTERFACE
    IPV6INIT=yes
    IPV6FORWARDING=no
    IPV6TO4INIT=yes
    IPV6TO4_IPV4ADDR=$IPV4
    EOF

  • Anonymous commented
    September 11, 2018 20:03

    I'm sad to hear that this doesn't have the high priority that it should have. :(
    This is stopping our migration from our current hosting.

  • Peter Murfitt commented
    September 11, 2018 20:03

    Would love to see this, I have to use a tunnel broker right now, which does work very well but native support would obviously be better.

  • Ryan Findley commented
    September 11, 2018 20:03

    Any update on an ETA for ipv6 support?

  • James Cloos commented
    September 11, 2018 20:03

    As an AS holder, you can get a /32, but even a non-PI /48 or two for each datacentre would provide enough space to give each droplet a /64.

    Adding native v6 to your current peering/transit/transport shouldn’t be a burden

  • Moisey Uretsky commented
    September 11, 2018 20:03

    Hi Daniele,

    We are definitely looking into rolling out IPv6 sooner rather than later but we have a few more physical updates to the service that we will be rolling out first.

    But we will definitely have IPv6 fully rolled out in 2013 as we feel its going to be a necessity for everyone as we get closer and closer to running out of IPv4 global allocations.

    Thanks

  • Daniele Albrizio commented
    September 11, 2018 20:03

    Native IPv6 connectivity lack is stopping me from migrating from a german VPS provider.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We will be rolling out a new core network in both our NY and AMS region which is the first step in getting IPv6 rolled out, when we have a better ETA we will be announcing it.

    Thanks

  • Bart Trojanowski commented
    September 11, 2018 20:03

    Is there any news on IPv6? If you run a beta, please contact me. I'd love to participate.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    Taking some time to work out all of the logistics with upstream providers, we'll be launching private IP networking first and then looking into IPv6.

  • Micheal Cottingham commented
    September 11, 2018 20:03

    We are in Q4, do you have an update?

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We will be introducing this eventually however we will need to do a lot of configurations throughout the entire network stack this will be rolled out later, most likely Q3.

  • Micheal Cottingham commented
    September 11, 2018 20:03

    I've already up-voted, but just would like to comment as well. As it becomes harder and harder to get IPv4 addresses, and hosting multiple sites on a single server, having IPv6 would make SSL deployment much easier.

  • Moisey Uretsky commented
    September 11, 2018 20:03

    We're looking into it but we dont have an ETA on that currently.