Rivian 2026.15 Reached ~99% of the Fleet in a Staged Five-Day Rollout

Community trackers show the build distributed to nearly every linked R1 vehicle over roughly five business days, with Rivian shipping corrective hotfixes while the waves were still expanding.

The Rivian Roamer tracker for 2026.15 currently reports 6,081 of 6,129 linked vehicles flagged for the update and 6,066 with it installed, both at about 99%. Connect+ vehicles sit at the same percentage, while the small non-Connect+ slice trails slightly at 97%. Those figures come from owner-linked accounts rather than Rivian's internal telemetry, yet they tell a consistent story: the rollout progressed through its wave schedule and essentially completed.

How Rivian staged the waves

Rivian distributes major OTAs in progressively larger rings. The Rivian Roamer software-update guide describes a pattern that spans roughly five business days, with Connect+ subscribers and trial users prioritized in the first three days and the remaining eligible vehicles covered over the final two. Rollouts advance on business days only. Selection within each wave is random, and WiFi parking does not move a truck or SUV up the queue.

The process is notification-driven: once a vehicle is flagged, owners see prompts on the center display and in the mobile app. That server-side gating explains why some R1S and R1T owners saw an update appear and then vanish before download finished. They were likely watching the boundary between waves, when Rivian's backend had flagged one slice of the fleet and had not yet opened the next ring.

Hotfixes arrived while the rollout was still moving

2026.15 was also a lesson in mid-flight corrections. RivianTrackr reported that Rivian issued hotfix builds 2026.15.30 for Gen 2 R1 models and 2026.15.01 for Gen 1 models to address privacy settings that had been flipping on their own, including location permissions and autonomy-related toggles. Rivian described the bug as rare. Owner comments on that piece describe a wider impact, with drivers saying Universal Hands-Free and Gear Guard cameras stopped working until they manually re-enabled settings.

That cadence matters for anyone tracking Rivian's OTA maturity. The company shipped a feature-heavy release adding Rivian Assistant and profile PIN security while smoothing Gen 2 autonomy behavior, detected a regression in the field, and pushed targeted rebuilds while the fleet tracker continued climbing toward full coverage.

What confused some owners

Mid-week owner chatter suggested the rollout had frozen. The tracker data does not support that reading. A dip in fresh install reports often coincides with the quiet tail of a wave schedule: early Connect+ owners finish quickly, then a multi-day gap opens before the next ring expands. Owners who compare their timing only to the first wave can easily read normal pacing as a stop.

The remaining gap is communication. Rivian did not publish running commentary on 2026.15 wave timing, and the mobile app does not alert owners when a vehicle is merely flagged, a limitation the Rivian Roamer guide documents explicitly. Community trackers filled that vacuum, which is useful when read against the wave model and easy to misread when it is not.

AutonomyEV's opinion

The evidence points to a staged OTA program working largely as Rivian designed it. 2026.15 reached nearly the entire fleet, and the privacy-toggle hotfix shows the ring strategy catching a defect, patching it, and continuing distribution. The friction is perceptual. Random queue placement plus sparse official status updates will keep producing "is it stuck?" moments even when the backend is advancing on schedule. Rivian would earn more owner trust with lightweight wave progress notes than with silence that leaves room for false halt narratives.