Still seeing Managed Postgres (MPG) charges after deleting clusters - why?

Hi all,

I recently deleted all of my Managed Postgres clusters and their associated apps, but I’m still seeing MPG Cluster + MPG Cluster Storage charges in my billing breakdown.

I’ve confirmed that:

  • fly pg list shows no active clusters

  • fly apps list doesn’t show any Postgres apps

  • I also ran fly volumes list but I may still see volumes in pending_destroy

Is this expected behavior (e.g., billing continues for volumes/snapshots until the deletion window is over), or should I open a support ticket because something is still being billed incorrectly?

Goal: I’m trying to keep costs as low as possible until launch, so I want to make sure I’m not paying for resources that should already be gone.

Thanks in advance!

This is the command to list unmanaged postgres clusters.

To list MPG clusters, you want fly mpg list.

If you have billing questions you should absolutely email billing@fly.io, where we can give you more specific help.

In general though, if you deleted a cluster in the middle of the month, you’re still seeing charges on your draft invoice because you had the resource provisioned until you deleted it, therefore you will be charged for the duration it was provisioned.

If you’re seeing charges continue to tick up, that sounds like something else is going on, and billing@fly.io is the place to write us. Unless you have paid support, then definitely use that as you’ll get a much faster response.

Appreciate the response. We ran fly mpg list also and it says that there are not any managed MPG clusters.

We didn’t use the MPG clusters. they were added automatically but not used (We have our own database).

Do you mean they were added when you fly launch’d?

Just FYI for the future, you have the option to make changes to the suggested launch settings, including to disable provisioning of a database. By default we provision a database for you if we detect that your app is using a database, and charges for MPG are accrued purely by virtue of the resources being provisioned (as is the same with basically all SKUs except data transfer).

If you write to billing@fly.io explaining this (I’d also suggest linking to this thread for context), we tend to be pretty understanding of genuine accidental provisioning.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.