PostgreSQL Network Egress Continues to Increase Despite Services Using Internal URL
project id: fd3bc524-4fff-4055-af62-1fc7a75accfe
How can I investigate increased network egress charges in PostgreSQL? My single service project already utilizes private URL.
Attached are two screenshots for comparison, one from two days ago and the other from today. The postgres service usage increated from 71.8GB to 85.5GB
![No description](https://cdn.answeroverflow.com/1174578622829428776/image.png)
![No description](https://cdn.answeroverflow.com/1174578623177576498/CleanShot_2023-11-15_at_23.13.142x.png)
6 Replies
Project ID:
fd3bc524-4fff-4055-af62-1fc7a75accfe
first, i would go remove the tcp proxy
Do you mean
Public Networking
Connect to your service over TCP using a proxied domain and port
removing the tcp proxy would be a surefire way to make sure your services are communicating with the database privately, if something breaks then you know you weren't using the private network
![No description](https://cdn.answeroverflow.com/1174580608123535410/image.png)
Thanks. Just deleted, I will wait few days and see the results.
of course if it continues to increase i will help you get an investigation going, so for sure report back in a few days