Display project or branch transfer totals
Usage dashboards
Neon · Const
Data transfer
Data transfer is Neon’s measure of traffic sent through the Neon proxy. It distinguishes public internet egress from bidirectional private-network transfer.
How it works
Neon measures data transfer as outbound traffic from databases through the Neon proxy. Public transfer covers internet egress, while private transfer through AWS PrivateLink is bidirectional; project and branch API responses expose their combined value as data_transfer_bytes.
Syntax
data_transfer_bytesKey points
- Traffic sent from Neon to clients is metered as network transfer, or egress.
- The public category covers database traffic leaving Neon through the public internet.
- Private transfer applies when traffic uses AWS PrivateLink.
- Consumption metrics expose separate byte counters for public and private transfer.
- Project and branch detail responses expose one combined data-transfer byte field.
Common mistakes
- Logical replication egress is included in public network transfer, even when the destination is another Neon database.
- Private transfer is not egress-only: bytes sent to and received from private-network clients are counted.
- Both pooled and direct connections, including read replicas, pass through the proxy and contribute outbound traffic.
Example: Read project data transfer
curl -sS -H "Authorization: Bearer $NEON_API_KEY" "https://console.neon.tech/api/v2/projects/$PROJECT_ID" | jq '.project.data_transfer_bytes'Reads the combined data-transfer byte count from a project response.
When to use it
Track public and private transfer against plan allowances
Cost monitoring
Measure AWS PrivateLink traffic in both directions
Private connectivity
Interview questions
QWhat does Neon mean by data transfer?
Data transfer is outbound traffic sent from a Neon database through the Neon proxy. Public transfer is internet egress, whereas private transfer uses AWS PrivateLink and counts both directions.
Follow-up: How would an API distinguish the two categories? Use public_network_transfer_bytes and private_network_transfer_bytes in consumption metrics; project and branch detail responses provide the combined data_transfer_bytes field.
QHow do public and private network transfer differ?
Public network transfer is traffic sent over the public internet. Private network transfer is available through AWS PrivateLink and is billed bidirectionally.
Follow-up: Why can private transfer be larger than public transfer? It includes inbound traffic from clients as well as outbound database responses, unlike public transfer.
QWhich API fields expose transfer usage?
The project and branch detail API responses expose data_transfer_bytes as the combined transfer amount. Consumption metrics separate public_network_transfer_bytes from private_network_transfer_bytes.
Follow-up: Which endpoint provides invoice-aligned usage metrics? The Consumption API endpoint is /consumption_history/v2/projects, with availability determined by the account plan.
Related
public network transferprivate network transferdata_transfer_bytespublic_network_transfer_bytesprivate_network_transfer_bytesConsumption APINeon proxyAWS PrivateLink