This page describes how to use Storage Intelligence advisor to manage cross-region egress.

Cross-region egress occurs when applications transfer data from Cloud Storage buckets in one region to Google Cloud services in another region. Colocating your Google Cloud services and storage resources helps manage cross-region egress.

Storage Intelligence advisor displays the **Spike in cross-region egress** finding when cross-region egress increases above historical trends in your project, folder, or organization. A *finding* is an anomaly detected from your metrics that needs your attention. For an overview of Storage Intelligence advisor, see [About Storage Intelligence advisor](https://docs.cloud.google.com/storage/docs/storage-intelligence/advisor-overview.md.txt). For a full list of findings, see [Findings reference catalog](https://docs.cloud.google.com/storage/docs/storage-intelligence/findings/findings-reference-catalog.md.txt).

## Thresholds that trigger a finding

Storage Intelligence analyzes historical data to establish a baseline for
cross-region egress across your project, folder, or organization.
Storage Intelligence advisor generates a finding when cross-region
egress increases above this baseline over the last 24 hours.

Findings reflect the previous day's activity. For example, a spike occurring on
Tuesday appears in Storage Intelligence advisor on Wednesday.

## Respond to a finding

1. [View the finding details](https://docs.cloud.google.com/storage/docs/storage-intelligence/view-advisor.md.txt#view-finding-details).

2. Use the following table to select the recommended strategy for your
   scenario:

   <br />

   | Scenario | Recommended action | Details |
   | Data is frequently accessed from another region | Colocate resources using [bucket relocation](https://docs.cloud.google.com/storage/docs/bucket-relocation/overview.md.txt) | Colocate storage with Google Cloud services to optimize performance and reduce cross-region egress costs. Bucket relocation helps you move an existing Cloud Storage bucket from one geographic location to another. |
   | Need to understand which data or access patterns are driving egress | Investigate with Storage Insights datasets | If you need more granular information about what is driving cross-region egress, use Storage Insights to export metadata to BigQuery to identify specific prefixes, objects, and access patterns. > [!NOTE] > **Note:** Exporting data to BigQuery incurs costs. For details, see [BigQuery Pricing](https://docs.cloud.google.com/bigquery/pricing). |
   |---|---|---|

   <br />

## What's next

- **Key tasks** :
  - [View Storage Intelligence advisor](https://docs.cloud.google.com/storage/docs/storage-intelligence/view-advisor.md.txt#view-finding-details)
- **Explore other findings** :
  - [Improve performance by mitigating rate limited request errors](https://docs.cloud.google.com/storage/docs/storage-intelligence/findings/improve-performance-by-mitigating-429-errors.md.txt)
  - [Optimize usage for Coldline and Archive storage data](https://docs.cloud.google.com/storage/docs/storage-intelligence/findings/optimize-coldline-archive-class-costs.md.txt)
  - [Identify above trend storage consumption](https://docs.cloud.google.com/storage/docs/storage-intelligence/findings/identify-storage-consumption.md.txt)
  - [Review the findings reference catalog](https://docs.cloud.google.com/storage/docs/storage-intelligence/findings/findings-reference-catalog.md.txt)
- **Related concepts** :
  - [Storage Intelligence advisor overview](https://docs.cloud.google.com/storage/docs/storage-intelligence/advisor-overview.md.txt)
  - [Bucket relocation](https://docs.cloud.google.com/storage/docs/bucket-relocation/overview.md.txt)