IFO4
Loading...The data movement between two distinct provider regions, attracting per-gigabyte charges that are typically higher than intra-region traffic and lower than public internet egress. Cross-region transfer is a planning input for global service architectures, multi-region high availability, and disaster recovery topologies. The federation requires cross-region traffic volume to be reported quarterly per Tier-1 service with material flows reconciled to architectural intent under UFMS-001:2.4. Sustained spurious cross-region traffic is reported as egress waste.
A standard term of cloud networking literature; the AWS pricing schedule popularised the explicit cross-region transfer category in the early 2010s.
Federation members publish cross-region transfer volume per Tier-1 service quarterly. Material flows are reconciled to architectural intent. Spurious flows are reported as waste under MEV-Annex:3.2 and remediated through routing or topology change.
@misc{ifo4_glossary_cross_region_transfer,
title = {{Cross-Region Transfer}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{cross-region-transfer}}},
year = {2026},
url = {https://ifo4.org/glossary/cross-region-transfer},
note = {Category: FinOps; key: CrossRegionTransfer}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.