Canonical source:
libs/oshun/analytics/src/v3-pixel-streaming-session-start-success.ts
Evidence artifact:
V3/ue/Build/PixelStreaming/session-start-success-validation.json
Manifest version: v3-pixel-streaming-session-start-success.v1
The GA Pixel Streaming session-start gate validates every launch POP at 5x expected concurrency for seven consecutive UTC days. Each POP must keep daily session-start success at or above 99.5%, with first-frame p99 at or below 8 s.
| POP | 5x sessions | 7-day attempts | 7-day success | Worst daily success | Worst first-frame p99 |
|---|---|---|---|---|---|
us-east-1 |
6,000 | 1,008,000 | 99.7966% | 99.7847% | 6.22 s |
us-west-2 |
4,000 | 672,000 | 99.7677% | 99.7573% | 6.50 s |
eu-west-1 |
4,000 | 672,000 | 99.7820% | 99.7688% | 6.43 s |
ap-northeast-1 |
1,500 | 252,000 | 99.7250% | 99.7000% | 7.03 s |
ap-south-1 |
1,250 | 210,000 | 99.5814% | 99.5567% | 7.42 s |
ap-southeast-2 |
1,250 | 210,000 | 99.6567% | 99.6367% | 6.88 s |
sa-east-1 |
1,250 | 210,000 | 99.6205% | 99.6033% | 7.16 s |
The release gate is anchored to the Rust Pixel Streaming relay
(apps/v3/lilith-pxstream-relay/src/lib.rs), the
session_start_success_stays_above_budget_under_5x_ga_load harness, the
short-lived session JWT, SDP exchange, and the UE Pixel Streaming worker image
contract. The verifier fails closed when a required POP is missing, load does
not equal 5x GA capacity, CI is not green, the window is not exactly seven
consecutive UTC days, any daily success rate drops below 99.5%, first-frame p99
exceeds 8 s, or the relay and worker smoke contracts are not wired.