Clipper 2.0 Is Still Seeing Hourslong Outages, and a Full Fix Is Months Away

Why It Matters

Persistent failures erode rider confidence and threaten fare revenue, while escalating costs pressure transit agencies already facing budget constraints.

Key Takeaways

• Only 1.3M of 15M cards upgraded.
• Ten major incidents caused 33+ outage hours.
• Additional $3.4M budget for legacy system.
• Call center volume tripled to 35k calls monthly.
• Bulk migration testing slated for May 30.

Pulse Analysis

The Bay Area’s Clipper card has been the region’s unified fare medium for over a decade, linking BART, Caltrain, Muni and dozens of smaller operators. The promised Clipper 2.0 upgrade, billed as a next‑generation platform with instant top‑ups, discounted transfers and mobile‑wallet integration, was slated for an eight‑to‑12‑week rollout under a $461 million contract with Cubic Transportation Systems. Instead, the project entered a protracted “soft launch” after its December 10 debut, with only 1.3 million cards migrated and a cascade of technical failures that have kept the system in limbo.

The operational fallout is immediate and costly. Cubic has recorded ten major incidents, amounting to more than 33 hours of systemwide outages, including a three‑hour‑48‑minute shutdown that coincided with the San Francisco Giants’ opening game. Transit agencies report a threefold surge in call‑center volume to roughly 35,000 calls per month, prompting a $7.6 million budget request for additional staffing. Lost fare revenue is difficult to quantify, but a single July 1 outage cost BART an estimated $386,000, underscoring how software underperformance can directly dent agency finances.

With a bulk‑migration test not expected until May 30 and a full transition pushed into the next fiscal year, the MTC is preparing to fund the legacy Clipper system for another year, allocating an extra $3.4 million. The situation highlights the risks of large‑scale public‑private IT contracts lacking robust performance safeguards. Agencies considering similar upgrades should demand clearer milestones, penalty clauses, and contingency funding to avoid service disruptions that alienate riders and erode trust. Ultimately, a reliable fare‑collection backbone is essential for sustaining ridership growth and funding future transit investments.