Review Google Cloud inter-region transfer costs
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Start with the exported service, SKU, project, location, usage, cost, and credit data. Prioritize material transfer-related rows, then verify the exact SKU and the service's pricing rules before changing an architecture.
Why this is worth a look
The standard Cloud Billing export contains services, SKUs, projects, locations, cost, usage, credits, adjustments, and currency. Google Cloud networking pricing distinguishes inter-zone, inter-region, internet transfer, CDN, and load-balancing charges, so review the service and SKU together instead of treating every transfer-related row as one path or rate.
Run this check
CHECKLISTUse this read-only BigQuery review checklist with the standard or detailed Cloud Billing export. It avoids assuming that a billing row identifies every network endpoint.
READ-ONLY REVIEW
Scope: one Cloud Billing account, one complete usage period, and the matching BigQuery export.
Permissions: permission to view the exported billing table and the Google Cloud SKU catalog. No resource changes are required.
Units: record the usage unit and amount exactly as exported; record cost and credits in the export currency.
[ ] Confirm the standard table name is gcp_billing_export_v1_<BILLING_ACCOUNT_ID>, or the detailed table name is gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID>.
[ ] Filter or search the export's SKU descriptions for candidate transfer-related rows. Treat the result as a starting search, not a complete classification.
[ ] Review candidate rows by service, exact SKU, project, location, usage, cost, credits, and adjustments. Calculate cost after credits using the export's documented credit fields.
[ ] Check each candidate SKU in the Google Cloud SKU catalog by product, SKU name or ID, and service region. Confirm the unit and pricing rule.
[ ] Use architecture and network records to confirm the source and destination services and their regions or zones before estimating a change.
[ ] Record whether each candidate is material or immaterial for this period. Do not treat an empty search result as proof that all transfer costs are absent.How to confirm it
- 01
Confirm the export and period
Use the BigQuery export for the billing account under review. Choose either the standard table, gcp_billing_export_v1_<BILLING_ACCOUNT_ID>, or the documented detailed table, gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID>. Confirm the usage period is complete and account for export delays or missing periods.
- 02
Create a candidate SKU list
Search SKU descriptions for transfer-related candidates, then inspect the matching rows. This text search is only a starting point because the SKU catalog and pricing rules determine how a row should be classified.
- 03
Prioritize exported cost dimensions
Review each candidate by service, exact SKU, project, location, usage, cost, credits, and adjustments. Include credits when calculating cost after credits, and keep the exported currency and usage unit with the result.
- 04
Verify the service and SKU rules
Look up each material SKU in the Google Cloud SKU catalog by product, SKU name or ID, and service region. Compare the rule with architecture and network records that confirm the source and destination services, regions, or zones.
Before making changes
This review depends on the fields and rows available in the selected export. A SKU-description search can include unrelated rows or miss relevant SKUs, so validate candidates against the SKU catalog. Billing modifications appear as separate line items, and export data can be delayed or unavailable for periods when export was disabled.