Net emissions, after including Google's purchase of clean energy (market-based
methodology) are not yet available.
New carbon transfer configs create an off-schedule transfer run
When creating a new Carbon Footprint transfer config to
export carbon data to BigQuery, the
BigQuery Data Transfer Service will create an initial transfer run for the current date.
However, because carbon data is only published on the 15th of the month, this
initial transfer run may contain no data.
Transfer configs will automatically export carbon data for future months on the
15th of each month. Historical data can be requested via backfill as described
here.
[[["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-08-25 UTC."],[[["\u003cp\u003eCarbon Footprint's known issues are listed on this page and are planned to be addressed in future updates.\u003c/p\u003e\n"],["\u003cp\u003eNot all Google Cloud services are currently covered by Carbon Footprint, and a list of included services is available.\u003c/p\u003e\n"],["\u003cp\u003eCarbon Footprint currently reports location-based emissions only, with net emissions not yet supported.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new Carbon Footprint transfer configuration may trigger an initial, empty transfer run because data is released monthly on the 15th.\u003c/p\u003e\n"],["\u003cp\u003eFuture monthly carbon data transfers will occur automatically on the 15th, and backfilling is available for historical data.\u003c/p\u003e\n"]]],[],null,["# Known issues for Carbon Footprint\n=================================\n\nThis page lists known issues for Carbon Footprint.\nAddressing these issues is on the roadmap of Carbon Footprint.\n\nYou can also [check for existing issues](https://issuetracker.google.com/issues?q=componentid:1108255)\nor [open new issues](https://issuetracker.google.com/issues/new?component=1108255&template=0)\nusing the [public issue tracker](/support/docs/issue-trackers).\n\nLimited coverage of Google Cloud services\n-----------------------------------------\n\nCarbon Footprint does not cover all Google Cloud services, see the\n[list of covered services](/carbon-footprint/docs/covered-services).\n\nOnly location-based emissions are reported\n------------------------------------------\n\nNet emissions, after including Google's purchase of clean energy (market-based\nmethodology) are not yet available.\n\nNew carbon transfer configs create an off-schedule transfer run\n---------------------------------------------------------------\n\nWhen creating a new Carbon Footprint transfer config to\n[export carbon data to BigQuery](/carbon-footprint/docs/export), the\nBigQuery Data Transfer Service will create an initial transfer run for the current date.\nHowever, because carbon data is only published on the 15th of the month, this\ninitial transfer run may contain no data.\n\nTransfer configs will automatically export carbon data for future months on the\n15th of each month. Historical data can be requested via backfill as described\n[here](/carbon-footprint/docs/export#bigquery)."]]
