Technical analysis
Why ordinary internet service cannot get this data there in time.
The requirement under analysis: sustained bulk delivery of machine data from each site to two fixed destinations at average payload rates of roughly 44 to 131 Gbps per dense site depending on the delivery window, within a bounded data-age SLA, with protected telemetry and engineered backlog recovery. What follows is the transport-layer mechanics, not a judgment about carrier quality.
1. What an internet path is actually made of
Only the first hop is dedicated. The rest is shared with everyone.
A dedicated internet circuit is dedicated for exactly one segment: the access loop from the site to the carrier's first aggregation point. Everything after that is statistically shared. A typical path from a rural site to a cloud or GPU ingress crosses ten to twenty routed hops across three to five separately owned administrative domains. Every domain boundary is a queue, a policy point, and a potential congestion point, and every element past the first is outside the site contract.
| Path segment | Who controls it | Capacity committed to this flow | Observable to you |
|---|---|---|---|
| Access loop, site to carrier | Site carrier | Yes, the port rate | Yes |
| Carrier metro aggregation and core | Site carrier | No, statistically multiplexed | No |
| Carrier peering or transit handoff | Two parties, bilateral | No, sized to average demand | No |
| Transit backbones | Transit providers | No | No |
| Transit to destination peering port | Two parties, bilateral | No, historically the hottest point | No |
| Destination ingress edge and fabric | Cloud or GPU provider | No, policed and rate-managed | No |
On the private path, every segment from site demarcation to destination cross-connect is a contracted product with committed capacity, held by one operator, instrumented end to end.
2. Internet routing picks the cheapest path, not the fastest
Internet paths are selected by a policy protocol. Selection is driven by each network's commercial preference, typically its cheapest egress, and by path length. No step in that selection consults latency, loss, jitter, or link utilization, so traffic keeps being sent into a saturated interconnection port indefinitely, because saturation is invisible to the protocol. Each network also hands traffic off at its nearest exit to minimize its own carriage cost, which routinely produces asymmetric paths: the forward and return directions of one flow cross different infrastructure, with different behavior, defeating both performance reasoning and fault isolation.
The path is also not stable. Routes change without notice through maintenance, failures, and commercial renegotiations, so the path measured during a pilot is not guaranteed to be the path in production. Every network in the middle is optimizing its own cost of carriage. None is optimizing, or even aware of, your delivery objective. On the private path there is no path selection between site and destination at all: traffic follows engineered circuits whose route, capacity, latency, and failover behavior are fixed by design and stated in each Site Deployment Plan.
3. Delivery times have to be predictable
End-to-end latency has two components: propagation, fixed by distance, and queueing, variable and accruing at every congested hop. On a multi-domain path, queueing delay varies with everyone else's traffic: diurnal peaks, buffer bloat at access and interconnection points, and congestion events produce round-trip variance the site's dedicated loop does nothing to prevent. For interactive traffic jitter is an annoyance. Here it is contractual, because the SLA is expressed as maximum data age at the destination, and delivery-time predictability is exactly what queueing variance destroys. A path whose round-trip time breathes between 35 ms and 120 ms with the internet's load cannot support a bounded delivery commitment.
- 35 to 120 ms
- typical internet round-trip variance under load
- 18 to 47 ms
- engineered per-site route baselines, stated per site
- Sub-millisecond
- jitter on the private path, held at peak
4. A little packet loss wrecks transfer speed
Lose a fraction of a percent, and speed falls off a cliff.
Sustained bulk transfer is governed by the loss-throughput relationship: per-flow throughput is proportional to segment size divided by round-trip time times the square root of loss. Two structural consequences follow. Fractions of a percent of loss on a long path cut per-flow rates by an order of magnitude. And the internet path caps segment size at the standard 1500-byte frame, because jumbo frames do not survive multi-domain transit, while the private path runs jumbo frames end to end, raising the per-flow ceiling roughly sixfold at identical round-trip time and loss.
| Path loss rate | Per-flow ceiling, 40 ms round trip, 1500-byte frames | Parallel flows needed for 44 Gbps |
|---|---|---|
| 0.001%, well-run path, off-peak | ~113 Mbps | ~390 |
| 0.01%, ordinary internet weather | ~36 Mbps | ~1,200 |
| 0.1%, congested peering at peak | ~11 Mbps | ~3,900 |
| 1%, congestion event | ~3.6 Mbps | ~12,300 |
Parallel flows mitigate the per-flow ceiling but do not repair the underlying capacity: thousands of competing flows converging on the same congested port amplify queueing, raise the loss rate they are trying to outrun, and inflate transfer time through retransmission, which also duplicates carried volume. Loss at peak is precisely when the fleet is offloading. The private path is engineered to loss at or below 0.001% with fixed round-trip time and jumbo framing, so the same 44 Gbps objective is met with a handful of flows, and the loss and latency budget for each route is a stated, tested acceptance criterion.
5. Every site ends up squeezing through the same few points
Every shared segment above is oversubscribed by design: it is sized to average demand across all customers, not to any customer's committed rate, because that is what makes internet service economical. The binding constraints in practice are the bilateral interconnection ports, carrier to transit and transit to cloud, which are sized commercially, run hot at peak, and are augmented on negotiation timescales measured in quarters, by parties with no contract to your program.
The fleet then makes this worse with its own success: every added site sends bulk flows to the same two destinations, so the program's traffic fans in on identical choke points and congests itself, with degradation correlated across all sites, at peak, simultaneously. Every architecture has bottlenecks. The distinction is whether they are owned, measured, provisioned, observable, and expandable, or merely encountered downstream. The private design does not eliminate convergence, it relocates it to the A/B Aggregation Core, where aggregate demand is the arithmetic sum of contracted tiers, capacity is contracted non-blocking, utilization is reviewed quarterly, and upgrades follow a published tier ladder ahead of saturation.
6. You cannot see, or fix, most of the path
Operationally, the internet path ends at the carrier edge. There is no telemetry into a transit provider's queue depths, no ticket to file on someone else's peering port, no restoration target that attaches to the segment actually failing, and, given asymmetric routing, often no certainty about which segment that is. Fault isolation across three to five administrative domains is a negotiation, not a procedure. The private path is instrumented per segment, and delivery telemetry, bytes generated, queued, transmitted, received at aggregation, and accepted at destination, localizes any shortfall to source, storage, transport, core, or destination ingest, under one operator's SLA with stated restoration targets, credits, and chronic-outage rights.
7. What you need, and what each option actually does
| What the program needs | What internet access actually does | What the private path does |
|---|---|---|
| Sustained 44 to 131 Gbps payload per dense site | Per-flow ceilings set by loss and round-trip time; shared segments sized to average demand | Non-oversubscribed committed capacity, jumbo framing, engineered loss budget |
| Bounded data age at destination | Queueing variance and route instability make delivery time unpredictable | Fixed engineered round-trip time per route, sub-millisecond jitter, stated in the deployment plan |
| Protected telemetry class | No end-to-end quality of service: class markings are not honored across domains | Three service classes enforced end to end: protected, shaped, recovery |
| Backlog recovery after impairment | Recovery flows compete at the same congested choke points at peak | Deliberate spare capacity engineered per site for drain rate |
| Fault isolation and remedy | Three to five domains, asymmetric paths, no cross-domain SLA | One operator, per-segment telemetry, single SLA with restoration targets |
| Path and cost governance | Routing selects for each intermediary's cost; paths change without notice | Engineered circuits; route, capacity, and failover fixed by design |
Conclusion
None of these mechanisms reflects poor carrier engineering. Each is the internet working as designed. Routing economics, statistical multiplexing, nearest-exit handoff, and best-effort interconnection are what make universal reachability affordable, and they are exactly the properties that make bounded, sustained, high-volume delivery between fixed endpoints unachievable as a contractual commitment.
Internet access optimizes reachability at lowest cost. This program requires assured delivery within a data-age budget. Those are different engineering problems, and the private managed fabric exists because the second cannot be solved with the tools of the first. The mismatch is not paid for in network terms: it is paid in idle GPU capacity waiting on delayed data, and in training and program milestones that slip behind it.
Figures shown are illustrative planning and engineering values. Per-site values are set in each Site Deployment Plan.