Google says its Ultra Low Latency Solution and U4 machine family are generally available, but documentation limits access to approved exchange operators and participants in select private Google Cloud regions. Exchange operators run on U4P bare metal, participants on U4C bare metal, and nearby auxiliary workloads on U4S virtual machines.
On U4C, two physical NICs carry separate A and B unicast and multicast market feeds at up to 1 Gbps each, while a third NIC carries ordinary cloud communication at up to 100 Gbps of internal egress. The feed path can use hardware multicast and user-space networking through OpenOnload and DPDK rather than a traditional hypervisor-level virtual switch.
Firefly integration is described as sub-10-nanosecond network-level or NIC-to-NIC synchronization. That is timestamp precision, not a claim that an order executes end to end in under 10 nanoseconds. U4C can attach 12 TiB of local Titanium SSD; persistent Hyperdisk is a separate archive option. A primary zone supports live production while a secondary zone supports maintenance and qualification.
Google cites collaboration with CME Group and customer testing, but publishes no raw latency distributions, sample sizes, prices, regions or reproducible benchmark code. The interesting result is the split architecture: bare metal for the direct feed path, virtual machines for adjacent risk and analytics. Google Cloud engineering post · U4 documentation.