---
cuppy_hub: gcp
cuppy_path: changelog/2026-10-21-networking-family.md
cuppy_section: docs
cuppy_doc: KYYB-CH3R
cuppy_doc_uuid: 18217da1-1b5a-4918-a03a-b379a63d1b47
cuppy_permalink: https://cuppy.io/gcp/d/KYYB-CH3R
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/gcp/docs/changelog/2026-10-21-networking-family
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 3790977c08a2866acafa06f29a831460126be6df45eebb9b186c7c442eddbead
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# Networking family — first release

## Added

| Document | What it carries |
|---|---|
| `reference/networking/vpc.md` | global network, regional subnets, the two subnet modes, the implied rules, non-transitive peering, Shared VPC |
| `reference/networking/cloud-load-balancing.md` | the current type names, which are global, proxy against passthrough, the Premium/Standard classic trap |
| `reference/networking/cloud-nat.md` | software-defined rather than an appliance, the two NAT types, and the inbound sentence |
| `reference/networking/cloud-armor.md` | the attachable balancer list, the rules language, the CRS versions |
| `reference/networking/private-service-connect.md` | the five objects and which side owns each |
| `reference/networking/errors.md` | indexed by symptom and topology, because networking failures have no error string |
| `guides/networking/reach-a-private-service.md` | six steps, ending in a revocation test |
| `guides/parity/networking.md` | the four rows that re-model a networking estimate |

## The headline fact

**A Google Cloud VPC network is global; only its subnets are regional.** An AWS VPC and an Azure VNet are
regional. So `N` regional networks usually become **one** network with `N` subnets, and the transit object —
Transit Gateway, Virtual WAN — disappears. This is a re-modelling, not a count conversion, and it is the
largest structural difference in the whole hub.

## Absences recorded rather than filled in

- The Cloud NAT overview **does not name specific port-allocation modes**; only "manual NAT IP address
  assignment" is named, so nothing else is stated.
- The Cloud Armor overview **does not name distinct policy classes** (backend, edge, network-edge) as separate
  categories. Those names exist elsewhere in the product's documentation and are not asserted here.
- The load-balancing overview was read for taxonomy, not for backend services, health checks, URL maps or
  certificates — none of which this release documents.

## Known missing

- Backend services, health checks, URL maps, forwarding rules, certificates.
- Cloud Interconnect, Cloud VPN, Network Connectivity Center and hybrid routing.
- Cloud DNS, including private zones and DNS peering.
- VPC Service Controls — named in the compute and IaC families as a cause of refusals, not documented.
- Network service tiers in their own right, beyond the classic-balancer note.
- VPC Flow Logs and Network Intelligence Center.


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 91 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/gcp/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->