Stay organized with collections
Save and categorize content based on your preferences.
This page covers frequently asked questions about the use of
Data Transfer Essentials.
Does Data Transfer Essentials cover traffic to external users?
No. Data Transfer Essentials doesn't extend to
inter-cloud service provider (CSP) traffic between an organization and its
external users, whether other organizations or individual customers. Such
traffic is charged at the data transfer rates that are applicable by default as
documented in Network Service Tiers pricing.
Which connectivity methods can I use in conjunction with Data Transfer Essentials?
Data Transfer Essentials is designed to work only with external
IP connectivity.
Is Data Transfer Essentials suitable for mission-critical services?
No. For mission-critical services, connectivity over the internet might not be
suitable. Other cross-CSP Google Cloud connectivity products, such as
Cross-Cloud Interconnect
or Cloud Interconnect,
aren't supported by Data Transfer Essentials.
Can other services be supported?
No. Data Transfer Essentials supports only essential services,
Network Service Tiers or regional endpoints
and regions. See Supported services and regions.
Other services are outside the scope of Data Transfer Essentials.
Can other CSPs be supported?
No. Data Transfer Essentials supports only specific CSPs and
ASNs.
Can a destination be defined using a domain name?
No. Data Transfer Essentials doesn't support defining a
cross-cloud destination by domain name. This helps you avoid the problem of
maintaining all possible IP address resolutions for the domain name in the
associated destinations of the configuration. You define destinations by IP
prefixes.
Can I retroactively enable Data Transfer Essentials for a service?
No. Data Transfer Essentials applies to future usage.
Configuration changes—including creation, updates, and
deletions—require up to 24 hours to take effect.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-10 UTC."],[],[],null,["This page covers frequently asked questions about the use of\nData Transfer Essentials.\n\nDoes Data Transfer Essentials cover traffic to external users?\n\nNo. Data Transfer Essentials doesn't extend to\ninter-cloud service provider (CSP) traffic between an organization and its\nexternal users, whether other organizations or individual customers. Such\ntraffic is charged at the data transfer rates that are applicable by default as\ndocumented in [Network Service Tiers pricing](/network-tiers/pricing).\n\nWhich connectivity methods can I use in conjunction with Data Transfer Essentials?\n\nData Transfer Essentials is designed to work only with external\nIP connectivity.\n\nIs Data Transfer Essentials suitable for mission-critical services?\n\nNo. For mission-critical services, connectivity over the internet might not be\nsuitable. Other cross-CSP Google Cloud connectivity products, such as\n[Cross-Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/cci-overview)\nor [Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/overview),\naren't supported by Data Transfer Essentials.\n\nCan other services be supported?\n\nNo. Data Transfer Essentials supports only essential services,\n[Network Service Tiers](/network-tiers/docs/overview) or regional endpoints\nand regions. See [Supported services and regions](/data-transfer-essentials/docs/services).\nOther services are outside the scope of Data Transfer Essentials.\n\nCan other CSPs be supported?\n\nNo. Data Transfer Essentials supports only specific CSPs and\n[ASNs](/data-transfer-essentials/docs/asn).\n\nCan a destination be defined using a domain name?\n\nNo. Data Transfer Essentials doesn't support defining a\ncross-cloud destination by domain name. This helps you avoid the problem of\nmaintaining all possible IP address resolutions for the domain name in the\nassociated destinations of the configuration. You define destinations by IP\nprefixes.\n\nCan I retroactively enable Data Transfer Essentials for a service?\n\nNo. Data Transfer Essentials applies to future usage.\nConfiguration changes---including creation, updates, and\ndeletions---require up to 24 hours to take effect."]]
