Yeh the terminology is maybe a bit unclear, but the usage graphs are more about illuminating billing charges. So this is “usage” in the context of usage-based billing, i.e. Fly.io resources that you’re “using”.
With that context, this graph shows you the number of “IP assignment days” you’ve used. So if you had an ipv4 assignment for half a day (12 hours), that would contribute 0.5 to the value on this graph for that day.
This directly relates to how much you’ll be charged for IP assignments at the end of the month.
If you’re interested in tracking hits to an IP, that’d be a metrics thing. Let me know if you’d like more details on how to do this (off the top of my head I don’t know, but can investigate).
We’re actively working on improving our invoicing experience, which includes stuff like the usage reporting experience.
We bill for IPv4 in hourly increments, so it looks like the charge you’re seeing is because you had the dedicated address allocated for a little over half the month.
We will start charging for IPv4 on March 2024 invoices.
Hello,
On March 1st, 2024 we will begin charging for dedicated anycast IPv4 addresses.
What is this dedicated IPv4 charge about?
We have been giving out free dedicated IPv4 addresses to new apps. The IP address market unfortunately doesn’t allow for that. So we added shared IPv4 support, and assign those to newly created apps, free of charge. Since we have this new alternative, dedicated IPs will soon come with a cost of ~$2/month.
Until the end of this month anything IPv4 related showing up on our dashboard is a preview line, meaning its not gonna be charged by the February 1st.
When February 1st arrives then we will start collecting charges by the hour and the first invoice that will collect those charges is going to be the March 1st one.
I received the January unexpected dedicated IPv4 charge. So I tried: $ fly ips release 213.188.197.238 -a YOUR_APP_NAME
but got
Error: Could not find IPAssignment
I continued with $ fly ips allocate-v4 --shared -a YOUR_APP_NAME
and got
VERSION IP TYPE REGION
v4 66.241.125.30 shared global
Just to check, I have an A record currently using a dedicated IP on an app that has already been suspended. I’ve just destroyed the app using “flyctl apps destroy my-app-name”. Am I safe from being charged?
i have still not been refunded (the errant Jan 1 charge) and the billing team don’t respond to correspondence. I’ve had to alert my credit card company. Have others managed to obtain a proper refund?
I can see we credited your account for the amount you was charged back then along all others and we also replied on the email thread too.
Folks who had unpaid invoices back then and their only bill was IPv4 had their invoice voided (aka we made Stripe consider it paid).
Folks who had paid charges and only had IPv4 as $ values had their invoice fully refunded.
Folks who had a a charge that had other things + IPv4 had their accounts credited by the IPv4 amount so the next month will got a proportional discount.
Your organization falls under the 3rd case as you verify in your invoice. I hope that helps clarify things.
Hi I would prefer your billing team responded than discuss this publicly.
The problem with your approach is that it does not put me (and presumably many others) back in the position I would be in had the mistake not happened. It costs me $6 more. So is not a valid solution.
