AWS is also starting to charge for public IPv4 addresses this year. Did something happen with IPv4 markets? I used to think at least cloud providers were hoarding a ton of addresses.
We are going to start charging for dedicated IPv4 in January 1st
11–20 of 28 posts
Re: We are going to start charging for dedicated IPv4 in January 1st
#12That was posted 10 weeks ago. It also mentions that they list the charge for ipv4, but never actually billed for it.
The subject seems editorialized.
Re: We are going to start charging for dedicated IPv4 in January 1st
#13That was posted 10 weeks ago. It also mentions that they list the charge for ipv4, but never actually billed for it. The subject seems editorialized.
It seems they listing the pricing on their pricing page some time around April? The earliest snapshot I found with the pricing / shared IPv4 address stuff is this one: https://web.archive.org/web/20230404222621/https://fly.io/do...
Re: We are going to start charging for dedicated IPv4 in January 1st
#14I just came to HN to see if there was something about this here. I just got my first charge out of nowhere. I’ve had an account there for a couple years and tried it out a long time back but wasn’t actively using it. I like fly as a service, and I have no problem with them charging, but coming out of nowhere with no prior notice is definitely frustrating and unexpected.
The notice was posted by Fly on October 18th.
Posting a notice isn’t exactly the same as communicating with accounts that will be affected by the change. I hadn’t seen anything about it so it was a surprise to me. Would have appreciated a simple heads up - “hey, we’re going to start billing for this”
Re: We are going to start charging for dedicated IPv4 in January 1st
#15Out of the blue I received a bill from fly.io for ipv4 addresses. No warning about this, no email communication or anything. Forgot I even had anything on fly.io, was just some test stuff I created years ago. So if you ever tried them out but don't use them, go delete your account just in case they start billing you without warning. Oh and, don't put your credit card into a hosting service then forget about the "free…
same here. no email notification.
Re: We are going to start charging for dedicated IPv4 in January 1st
#16AWS is also starting to charge for public IPv4 addresses this year. Did something happen with IPv4 markets? I used to think at least cloud providers were hoarding a ton of addresses.
Two main reasons:
* The cost of an IPv4 address in the market is constantly increasing
* We have recessions, so giants are looking for savings and profits by using their market position.
In addition, some providers are making IPv6 available more and more (there is no reason to consider IPv4 granted then), and others built on someone else's infrastructure are starting to be charged, so they pass this cost on to consumers.
Re: We are going to start charging for dedicated IPv4 in January 1st
#17Same here, have a throw-away app for learning on fly-io. Got charge $75 for this month WITHOUT any email notification. Can't even contact support because you can't have email support for 'Hobby' tier
Re: We are going to start charging for dedicated IPv4 in January 1st
#18[dead]
Re: We are going to start charging for dedicated IPv4 in January 1st
#19No email sent out and charged on first of January for a mere 2$.
If there's a way to upset your customer base, that's one.
I had already switched off them my paid apps because of poor reliability and just had one internal app.
Shame because I love the workflow and the fact it's using firecracker.
This is the last fly.io sees of me.
Re: We are going to start charging for dedicated IPv4 in January 1st
#20If you're affected, you can replace dedicated IPv4 addresses with a shared one, or remove them:
fly ips release $ip
fly ips allocate-v4 --shared
fly ips allocate-v6