This page discusses metrics used to monitor data usage rates from your
Cloud Storage buckets, as well as how to request additional egress
bandwidth for different quotas if you need more than the default quota.
For instructions on accessing monitoring data in Cloud Storage, see
Access monitoring data.
Introduction
Cloud Storage provides bandwidth monitoring for you to track bandwidth
usage from your project's buckets to other Trusted Cloud by S3NS services. Bandwidth
monitoring tracks usage for the last 6 weeks.
Before monitoring bandwidth usage, review the following terms:
Egress bandwidth refers to the rate at which data is retrieved from your
buckets in the course of completing requests made to Cloud Storage.
Google egress bandwidth refers to data retrieved from your buckets that
is destined for other Google services, such as Compute Engine.
Internet egress bandwidth refers to data retrieved from your buckets
that is served to the Internet, such as data downloaded directly to
your local computer.
Network egress refers to the rate at which data is sent over the network
from your buckets to requesters.
In normal operation, egress bandwidth and network egress are typically about the
same; however, in some cases egress bandwidth can be meaningfully greater than
network egress. Broken connections, cancelled requests, and partial requests are
cases where the data retrieved can be greater than the data that's ultimately
sent.
Bandwidth monitoring metrics
Google egress bandwidth per second per region: monitors Google egress
bandwidth usage for buckets in your project that are located in regions.
Internet egress bandwidth per second per region: monitors Internet
egress bandwidth usage for buckets in your project that
are located in regions.
Network monitoring
In addition to Cloud Storage bandwidth monitoring, you can use the
network/sent_bytes_count metric to measure Cloud Storage
network egress. This is useful for approximating bandwidth usage for specific
buckets, because bandwidth monitoring tracks bandwidth usage by location and
project.
When using this networking metric, keep in mind the following:
network/sent_bytes_count uses bytes in its measurements, whereas typical
networking metrics often use bits. For example, a 1 GiBps measurement for
network/sent_bytes_count is equivalent to 8 Gibps.
network/sent_bytes_count tracks all the traffic sent over the network, not
only egress to co-located Trusted Cloud by S3NS services. As such,
network/sent_bytes_count is typically greater than bandwidth usage.
In some cases, network/sent_bytes_count can be less than bandwidth
usage due to events such as broken connections, cancelled requests, and
partial requests.
network/sent_bytes_count metrics are sampled every 60 seconds. If the
traffic is spiky, it's possible that requests are throttled for a short period
of time even though the average egress over 60 seconds is below the limit.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["# Overview of bandwidth usage in Cloud Storage\n\nThis page discusses metrics used to monitor data usage rates from your\nCloud Storage buckets, as well as how to request additional egress\nbandwidth for different quotas if you need more than the [default quota](/storage/quotas#bandwidth).\n\nFor instructions on accessing monitoring data in Cloud Storage, see\n[Access monitoring data](/storage/docs/access-monitoring).\n\nIntroduction\n------------\n\nCloud Storage provides bandwidth monitoring for you to track bandwidth\nusage from your project's buckets to other Google Cloud services. Bandwidth\nmonitoring is aggregated by region and tracks usage for the last 6 weeks.\n\nBefore monitoring bandwidth usage, review the following terms:\n\n- *Egress bandwidth* refers to the rate at which data is retrieved from your\n buckets in the course of completing requests made to Cloud Storage.\n\n - *Google egress bandwidth* refers to data retrieved from your buckets that\n is destined for other Google services, such as Compute Engine.\n\n - *Internet egress bandwidth* refers to data retrieved from your buckets\n that is served to the Internet, such as data downloaded directly to\n your local computer or data retrieved by Cloud CDN for serving to the\n Internet.\n\n- *Network egress* refers to the rate at which data is sent over the network\n from your buckets to requesters.\n\nIn normal operation, egress bandwidth and network egress are typically about the\nsame; however, in some cases egress bandwidth can be meaningfully greater than\nnetwork egress. Broken connections, cancelled requests, and partial requests are\ncases where the data retrieved can be greater than the data that's ultimately\nsent.\n\nBandwidth monitoring metrics\n----------------------------\n\nThe following bandwidth usage data is available for monitoring:\n\n- Google egress bandwidth per second per region: monitors Google egress\n bandwidth usage for buckets in your project that are located in regions.\n\n- Dual-region Google egress bandwidth per second per region per\n dual-region location: monitors Google egress bandwidth usage for buckets in\n your project that are located in dual-regions.\n\n- Multi-region Google egress bandwidth per second per region: monitors\n Google egress bandwidth usage for buckets in your project that\n are located in multi-regions.\n\n- Internet egress bandwidth per second per region: monitors Internet\n egress bandwidth usage for buckets in your project that\n are located in regions.\n\n- Dual-region internet egress bandwidth per second per region per dual-region\n location: monitors Internet egress bandwidth usage for buckets in your project\n that are located in dual-regions.\n\n- Multi-region internet egress bandwidth per second per region: monitors\n Internet egress bandwidth usage for buckets in your project that\n are located in multi-regions.\n\n### Monitoring alerts\n\nYou can use Monitoring alerting policies to inform you when\nmetrics such as `storage.googleapis.com/google_egress_bandwidth`,\n`storage.googleapis.com/dualregion_google_egress_bandwidth`, and\n`storage.googleapis.com/multiregion_google_egress_bandwidth` approach a quota\nlimit.\n\n- For an overview of Monitoring alerts, see\n [Introduction to alerting](/monitoring/alerts).\n\n- To get started with Monitoring alerts using the\n Google Cloud console, see [Create metric-based alert policies](/monitoring/alerts/using-alerting-ui).\n\n- For examples of Monitoring alerts, see\n [Chart and monitor quota metrics](/monitoring/alerts/using-quota-metrics).\n\n### Network monitoring\n\nIn addition to Cloud Storage bandwidth monitoring, you can use the\n[`network/sent_bytes_count`](/monitoring/api/metrics_gcp_p_z#gcp-storage) metric to measure Cloud Storage\nnetwork egress. This is useful for approximating bandwidth usage for specific\nbuckets, because bandwidth monitoring tracks bandwidth usage by location and\nproject.\n\nWhen using this networking metric, keep in mind the following:\n\n- `network/sent_bytes_count` uses bytes in its measurements, whereas typical\n networking metrics often use bits. For example, a 1 GiBps measurement for\n `network/sent_bytes_count` is equivalent to 8 Gibps.\n\n- `network/sent_bytes_count` tracks all the traffic sent over the network, not\n only egress to co-located Google Cloud services. As such,\n `network/sent_bytes_count` is typically greater than bandwidth usage.\n\n - In some cases, `network/sent_bytes_count` can be less than bandwidth usage due to events such as broken connections, cancelled requests, and partial requests.\n- `network/sent_bytes_count` metrics are sampled every 60 seconds. If the\n traffic is spiky, it's possible that requests are throttled for a short period\n of time even though the average egress over 60 seconds is below the limit.\n\nRequest more bandwidth\n----------------------\n\nThe following instructions apply when requesting egress bandwidth of up to 1\nTbps for Cloud Storage buckets:\n\n1. Make sure you have enabled the\n [Cloud Storage service `storage.googleapis.com`](https://console.cloud.google.com/apis/library/storage.googleapis.com).\n\n2. In the Google Cloud console, go to the IAM **Quotas \\& System Limits** page.\n\n [Go\n to Browser](https://console.cloud.google.com/iam-admin/quotas)\n3. In the **Filter** search bar, select the **Metric** property, then search\n for the metric for which you are requesting an increase:\n\n - Use `storage.googleapis.com/google_egress_bandwidth` to increase Google\n egress for your buckets located in regions.\n\n - Use `storage.googleapis.com/dualregion_google_egress_bandwidth` to increase\n Google egress for your buckets located in dual-regions.\n\n - Use `storage.googleapis.com/multiregion_google_egress_bandwidth` to\n increase Google egress for your buckets located in multi-regions.\n\n - Use `storage.googleapis.com/internet_egress_bandwidth` to increase Internet\n egress for your buckets located in regions.\n\n - Use `storage.googleapis.com/dualregion_internet_egress_bandwidth` to\n increase Internet egress for your buckets located in dual-regions.\n\n - Use `storage.googleapis.com/multiregion_internet_egress_bandwidth` to\n increase Internet egress for your buckets located in multi-regions.\n\n4. In the list of results, toggle the checkbox for the locations where you want\n to increase egress bandwidth. For the\n `storage.googleapis.com/dualregion_google_egress_bandwidth` and\n `storage.googleapis.com/dualregion_internet_egress_bandwidth` metrics, there\n must be non-zero historical usage of the metric before you can request an\n increase.\n\n5. Click **Edit Quotas**.\n\n6. Enter your requested quota and business justification.\n\n7. Click **Submit Request**.\n\nFor bandwidth requirements greater than 1 Tbps for egress from buckets in\nregions and dual-regions, contact your [Technical Account Manager](/tam) or Google\nrepresentative. Increase requests greater than 1 Tbps for egress from buckets\nin multi-regions are not supported.\n| **Important:** Granting and continuation of bandwidth quota increases is dependent on your project's history. For example, a project might have an existing bandwidth quota increase reduced or rescinded if the project is not in good standing.\n\nFor more information, see [View and manage quotas](/docs/quotas/view-manage).\n\nWhat's next\n-----------\n\n- [Access bandwidth monitoring data](/storage/docs/access-monitoring).\n- [Monitor who accesses your Cloud Storage resources](/storage/docs/audit-logging).\n- [Create notifications](/storage/docs/reporting-changes) when an object is created, updated, or deleted."]]