Network traffic between availability zones or sub-regions within a single cloud region, attracting lower charges than cross-region traffic but still material at scale. Intra-region transfer is the dominant cost component of multi-AZ high availability designs. The federation requires intra-region transfer volume to be reported per Tier-1 service quarterly, with optimisation opportunities identified through service mesh and zone-aware routing. Sustained intra-region transfer above the architecture intent baseline is reported as a routing inefficiency under UFMS-001:2.4.
A standard term of cloud networking literature; the multi-AZ pricing schedules of the major providers stabilised the vocabulary in the mid 2010s.
Federation members publish intra-region transfer volume quarterly. Multi-AZ traffic is reviewed at the annual architecture review for routing efficiency under MEV-Annex:3.2. Zone-aware routing decisions are documented in the architectural debt register.
@misc{ifo4_glossary_intra_region_transfer,
title = {{Intra-Region Transfer}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{intra-region-transfer}}},
year = {2026},
url = {https://ifo4.org/glossary/intra-region-transfer},
note = {Category: FinOps; key: IntraRegionTransfer}
}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.