Strava v. Garmin Lawsuit: Documented Timeline

Strava v. Garmin: A Documented Case Timeline

Strava sued Garmin in federal court on September 30, 2025, asserting patent infringement and breach of a cooperation agreement. Strava voluntarily dismissed the action without prejudice on October 21, and the court terminated it on October 22. The case produced no merits ruling, and the dismissal notice gave no reason.

This timeline separates filed allegations, public policy records, company statements, community reaction, and procedural events.

How to read the record

A complaint states the plaintiff's allegations and requested relief. It is not a finding that the allegations are true. A patent record establishes the document, claims, dates, and prosecution history. It does not decide infringement or validity in a later dispute.

A voluntary dismissal without prejudice ends the filed action at that point without a merits adjudication. The E086 public record reviewed here does not reveal a private resolution, concession, or reason for dismissal.

timeline
    title Strava v. Garmin public record
    2011 to 2017 : Patent filings and grants later asserted by Strava
    2015 : Cooperation agreement alleged in Strava complaint
    June 30, 2025 : Garmin API brand guidelines dated
    September 30, 2025 : Strava files federal complaint
    October 2025 : Strava publishes Reddit statement
    October 21, 2025 : Strava dismisses without prejudice
    October 22, 2025 : Court terminates case
    October 27, 2025 : Strava posts developer attribution update

Patent and partnership background

The complaint asserted U.S. Patent Nos. 9,116,922, 9,297,651, and 9,778,053. The patent records show their respective claims and histories.

The September 2025 complaint copy alleged that Strava and Garmin entered a Master Cooperation Agreement in 2015 involving Strava Live Segments on Garmin devices. The agreement itself was not in the reviewed public source set. Its disputed terms should not be described beyond attributed allegations from the complaint.

The complaint also recited a longer product history involving segments, heatmaps, and Garmin routing features. That history was part of Strava's pleading. The case ended before the court resolved competing factual or legal positions.

June 30, 2025: Garmin dates new API brand guidelines

Garmin's API Brand Guidelines are versioned June 30, 2025. They require attribution for Garmin device-sourced data across primary and secondary displays, exports, downstream APIs, derived uses, and social visuals. The guidelines state that noncompliance may lead to suspension or termination of API access under the applicable program agreement.

The document frames the requirement as source clarity and traceability. A dependent application may experience it as a broad product-design, engineering, and commercial obligation. Those two descriptions can both be true without deciding whether a particular contractual demand was enforceable.

September 30, 2025: Strava files suit

The public docket identifies Strava, Inc. v. Garmin Ltd. et al., No. 1:25-cv-03074, in the U.S. District Court for the District of Colorado.

Strava's complaint asserted that Garmin infringed the three patents and breached the alleged cooperation agreement. It requested damages and injunctive relief. The requested relief included restrictions affecting accused Garmin features and products.

The filing did not establish that Garmin infringed, breached an agreement, or lacked defenses. Garmin did not file an answer before Strava dismissed the action.

October 2025: Strava addresses users on Reddit

Strava Chief Product Officer Matt Salazar published "Setting the record straight about Garmin" through the Strava team account.

The post focused on Garmin's attribution policy and potential API cutoff. It said Strava considered the required branding intrusive and argued that users should be able to transfer activity data without required logos.

Replies challenged Strava's position by pointing to Strava's own API and branding restrictions and by emphasizing users' reliance on Garmin devices. The thread is direct evidence of a visible negative reaction in that community. It does not establish the opinion of all Strava users, a market-wide cancellation rate, or the legal merits.

October 21 and 22, 2025: dismissal and termination

Strava's filed notice of voluntary dismissal dismissed the action without prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(i). The notice did not explain why.

The docket records the court's termination of the case on October 22. There was no merits judgment, claim construction, validity decision, infringement finding, or published settlement in the reviewed record.

October 27, 2025: developer attribution update

Strava's developer update says Garmin updated its developer terms regarding data attribution and encourages affected developers to review implementation.

The update helps document operational continuity after the case ended. It does not explain the dismissal or establish what happened in private discussions.

What remains unresolved

The public record does not answer why Strava filed when it did, why it dismissed three weeks later, what either party concluded about the patents or agreement, or whether any confidential accommodation occurred.

The strongest public lesson is therefore about dependency and communication, not a legal winner. [[What Happens When an API Policy Changes Under Your Product]] addresses the operational response. [[How to Measure Platform Dependency Risk Before It Breaks Your Startup]] addresses the strategic exposure.

This page is educational reporting, not legal advice. It reflects public sources reviewed on July 27, 2026 and remains held for qualified legal review before publication. AI assistance was used for research organization, drafting, and validation. Publication remains unauthorized.