We are going to start charging for dedicated IPv4 in January 1st

I 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.<p>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.

Out 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&#x27;t use them, go delete your account just in case they start billing you without warning. Oh and, don&#x27;t put your credit card into a hosting service then forget about the &quot;free&quot; app you had on there...

&quot;Please don&#x27;t do things to make titles stand out, like using uppercase or exclamation points, or saying how great an article is. It&#x27;s implicit in submitting something that you think it&#x27;s important... Otherwise please use the original title, unless it is misleading or linkbait; don&#x27;t editorialize.&quot;<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;newsguidelines.html</a>

No email sent out and charged on first of January for a mere 2$.<p>If there&#x27;s a way to upset your customer base, that&#x27;s one.<p>I had already switched off them my paid apps because of poor reliability and just had one internal app.<p>Shame because I love the workflow and the fact it&#x27;s using firecracker.<p>This is the last fly.io sees of me.

I also fell into this new trap:<p><pre><code> flyctl ips list flyctl ips release 168.220.XXX.XXX flyctl ips allocate-v4 --shared </code></pre> Error: Your account has overdue invoices. Please update your payment information: <a href="https:&#x2F;&#x2F;fly.io&#x2F;dashboard&#x2F;myname&#x2F;billing">https:&#x2F;&#x2F;fly.io&#x2F;dashboard&#x2F;myname&#x2F;billing</a><p>Ok, so now they got my credit card info, because I had to pay 2$.<p><pre><code> flyctl ips allocate-v4 --shared </code></pre> Error: cannot use a shared ipv4 with wildcard hostnames, please remove those before allocating a shared IP: <i>.XXX</i><p><pre><code> flyctl certs list flyctl certs remove *.XXX flyctl ips allocate-v4 --shared </code></pre> Now it works. Just have to fix my DNS records now. ipv6 or CNAME to the app.fly.dev domain preferred.<p>I don&#x27;t like fly too much, because this is the first free hoster, which I have to constantly check for downtimes and restart the app then. Need a 10m cronjob now.<p><pre><code> cd ~&#x2F;MyAppPath if timeout 5 flyctl logs -a myapp | grep -e &quot;Health check on port 8080 has failed|connection error:&quot; then flyctl apps restart myapp fi</code></pre>

All: this was a bug. We&#x27;re reversing the charges. Everyone affected got an email. The tl;dr:<p>* The advance notice of the billing change (we announced in October, but only on our community site) slipped, but the billing change didn&#x27;t. That&#x27;s not OK! We agree: you get notified before we bill new things to you.<p>* Ordinarily, we waive invoices less than $5. Our billing code had a bug that let these charges slip through. D&#x27;oh.

Same here, have a throw-away app for learning on fly-io. Got charge $75 for this month WITHOUT any email notification. Can&#x27;t even contact support because you can&#x27;t have email support for &#x27;Hobby&#x27; tier

If you&#x27;re affected, you can replace dedicated IPv4 addresses with a shared one, or remove them:<p><pre><code> fly ips release $ip fly ips allocate-v4 --shared fly ips allocate-v6</code></pre>

I had a similar experience last year with them. Went to check the billing&#x2F;invoices section on my account, there was nothing there about the charge. Usage section to see if I had passed a limit, the section wasn&#x27;t even working properly and mentioned it was in beta.<p>Found a few people complaining on their forums about an unexpected charge but with no official resolve.<p>Since I wasn&#x27;t hosting anything serious with them, I purged the account and have never thought about them till now.

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.

That was posted 10 weeks ago. It also mentions that they list the charge for ipv4, but never actually billed for it.<p>The subject seems editorialized.