• Ask the Community

  • No IPv6 address for bunq API and website

Does bunq have any plans to make the app, the website and the api accessible over IPv6?

    May I ask why? As far as I understand it most advantages of IPv6 are for the provider, not the user.

      @Gregory#65663 I think in 2019, the argument against IPv6 should not be "IPv4 still works fine" anymore. Some home providers start to provision only an IPv6 address to their users, and multiple server hosting companies have models without IPv4 in their catalog. In my opinion, IPv6 support has been mandatory (or at least best practice) since at least 2018, probably even earlier. I can't think of any good reason (besides the initial work required) to skip IPv6 support any longer.

        @JanBrodda#65681 You're naming lots providers who use IPv6 and I understand the addresses are running out. But what advantage does it give the users of the API is what I'm asking. I think bunq can decide for themselves if they need it on their end

          @Gregory#65683 If my server does not have an IPv4 address, I am currently not able to use the API at all. And as I said earlier, there are hosting companies where IPv6-only machines are perfectly normal.

            Jan Brodda changed the title to No IPv6 address for bunq API and website.

              @Gregory#65663
              The IPv4 addresses space is almost exhausted. Therefore ISP's and other networking administers are forced to use technics like (carrier grade) NAT. If you are behind a carrier grade NAT, you share one public IPv4 address with multiple customers of the ISP. If your application (Or the bunq API) uses a black- and whitelist based on IPv4 addresses, multiple customers of an ISP are affected by one entry in the list. With IPv6 it possible to give every device a unique public address and make black- and whitelist for individual devices.

                The advantage of also being reachable through IPv6 should be obvious: You can also use bunq if you're on a IPv6-only network. Granted, maybe rare today for regular consumers, but it's becoming more and more important for some set-ups. And with carrier-grade NAT, I personally don't really want to use my IPv4 anymore. I don't want to be associated with the actions of any other users. So it is not something that bunq needs on their end, it's something that users need (and will need more and more in the future) to actually reach bunq.

                  @Gregory#65663 Also nice for privacy! You often have one IPv4 address, but a whole range of IPv6 addresses to segment your traffic in to. :)

                    I give up, discussing things in Internet community is a waste - but of my time ;-) Sorry that I tried, again. I deleted my comments.
                    It's useless, mankind is doomed. People don't understand.

                    bye :-)

                      8 months later

                      The original question is still valid - not having a dualstacked endpoint for all bunq APIs is a major bummer, especially in late 2019.

                      It would be nice to get an official statement from bunq - is this the right place to ask?

                        @Florian-Lime-Badger#129037 bunq replies sometimes but definitely not always. In case you want a guaranteed answer from a bunq employee your best shot is to try the Support chat 💬, although they might not be able to assist you with technical questions perse.

                          8 months later

                          @bunq I want to raise awareness for this.

                          IPv6 should be part of every modern company. Especially because you are so modern in terms of offering an API and sich, I would have expected there to be IPv6 compatibility. This is kind of a bummer :(

                            2 years later

                            Case in point: https://www.hetzner.com/sb Ordering a server with IPv4 address costs you 2 Euros / month more compared to going with IPv6-only (and you get a whole /64 subnet). For smaller projects leveraging the bunq API, being able to save some money is always nice.

                              3 months later

                              Here is a hoster without IPv4: https://ipv6onlyhosting.com They have DNS64 and NAT64, but incoming webhooks from the API wouldn't work. Also one of the biggest Japanese VPS providers gives you only IPv6 on the cheapest plan: https://web.arena.ne.jp/indigo/price/ Both as an API user but also as a regular banking user, I would appreciate not having to rely on IPv4 connectivity to communicate with my bank. The time to offer dual-stack connectivity is now!

                                2 months later

                                As far as I know, bunq runs on AWS and historically they've been pretty bad in terms of IPv6 support across all their products.
                                This has been changing recently (see: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/), but I believe there might still be some pains for migrating a whole service's workload to a fully functioning dual-stack setup - depending on bunq's service/cloud architecture.

                                  2 years later

                                  • GötzRookie

                                    • Post #23

                                    We have 2025 now and AWS has support for IPv6 nearly everywhere. At least for all the frontend stuff this should be feasible.
                                    As the internet even becomes more and more IPv6 centric. I can access bunq only via my mobile providers PLAT gateway, as mobile networks are IPv6-only now a days.

                                    When do we get #IPv6 support from #bunq?

                                    I once thought of bunq as a modern and forward looking bank.

                                      Write a Reply...