340 MB of outbound bandwidth on unused postgres instance

1

I just created a postgres instance in an organization. Aside not being able to get my app connected to it, it is now reporting ~340 MB of outbound data transfer. Anyone have any idea idea what’s up with that? It has to be a miscalculation or bug, because I haven’t even been able to connect.

2

There is data transfer due to replication, as well as for the app. May be that:

The good news is Fly are great with bandwidth and assuming your database app has no public IP, (and so if you only connect to it privately from other apps) currently Fly won’t bill you for the internal bandwidth used. Might need @kurt to confirm.

1 Like
3

I don’t have replication set up, and am having trouble getting my app to connect. As long as I’m not being billed, I guess I don’t care too much.

For reference if someone internal can look it up (or confirm this is normal):

App
  Name     = swaydm-db          
  Owner    = swaydm             
  Version  = 0                  
  Status   = running            
  Hostname = swaydm-db.fly.dev  

Instances
ID      	PROCESS	VERSION	REGION	DESIRED	STATUS          	HEALTH CHECKS     	RESTARTS	CREATED    
24dca5db	app    	0      	ord   	run    	running (leader)	3 total, 3 passing	0       	18h15m ago
4

340MB transfer is not that much, we do very frequent health checks on those and they add up in a hurry.

What issues are you having with your app connections?