Tyntec Inc. v. Syniverse Technologies, LLC

CourtDistrict Court, M.D. Florida
DecidedMay 29, 2020
Docket8:17-cv-00591
StatusUnknown

This text of Tyntec Inc. v. Syniverse Technologies, LLC (Tyntec Inc. v. Syniverse Technologies, LLC) is published on Counsel Stack Legal Research, covering District Court, M.D. Florida primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Tyntec Inc. v. Syniverse Technologies, LLC, (M.D. Fla. 2020).

Opinion

UNITED STATES DISTRICT COURT MIDDLE DISTRICT OF FLORIDA TAMPA DIVISION TYNTEC INC., et al.,

Plaintiffs,

v. CASE NO. 8:17-cv-591-T-23SPF

SYNIVERSE TECHNOLOGIES, LLC,

Defendant. __________________________________/

ORDER

A review of the papers, record, precedent, and scholarly literature reveals that the magistrate judge’s report and recommendation (Doc. 240) warrants adoption. However, the circumstance justifies a few comments on some points the plaintiff raises in objection and on the report in general. First, the argument that tyntec inherited a “preexisting voluntary and . . . profitable”1 course of dealing by virtue of Iris’s contract assignment is weak, at best.2 (Doc. 250 at 20–1) Because a course of dealing, considered in the antitrust context, sheds “light upon the motivation of [the] refusal to deal,” Verizon Commc’ns Inc. v. Law Offices of Curtis V. Trinko, LLP, 540 U.S. 398, 409 (2004), the course of dealing between Iris and Syniverse imputes no probative course of dealing to tyntec and

1 Novell, Inc. v. Microsoft Corp., 731 F.3d 1064, 1074 (10th Cir. 2013). 2 But see Steward Health Care Sys., LLC v. Blue Cross & Blue Shield of Rhode Island, 997 F. Supp. 2d 142, 154 (D.R.I. 2014) (declining to grant a motion to dismiss because “the Court is not aware of case law that would preclude consideration of [the assignor’s] direct prior course of dealing with [the defendant]”). Syniverse, who were strangers before the assignment. Although Iris and Syniverse’s prior course of dealing might retain some evidentiary value on some issue and, in that sense, might acquire some “relevance,” the Iris and Syniverse course of dealing establishes neither a voluntary and profitable course of dealing between Syniverse

and tyntec nor a perennial course of dealing in the inter-carrier vendor (ICV) market. Both logic and the protean economics of the ICV market caution strongly to the contrary. Second, a year into this action, tyntec offered Syniverse more than forty- thousand dollars if Syniverse would agree to a free peering relationship. tyntec

argues that Syniverse manifested “exclusionary practices” by rejecting this offer and forbearing short-term profits. (Doc. 116 at 10–11) The notion that Syniverse’s rejection of tyntec’s eleventh-hour offer exemplifies Syniverse’s “anti-competitive” motivation will not cohere. The antitrust laws obligate a court to “look back in time to the marketplace as it once was and . . . not as it now is.” Novell, Inc. v. Microsoft

Corp., 731 F.3d 1064, 1071 (10th Cir. 2013). Further, “the bringing of a lawsuit . . . may provide a sound business reason for . . . terminating [business] relations.” House of Materials, Inc. v. Simplicity Pattern Co., 298 F.2d 867, 871 (2d Cir. 1962)). And Syniverse provides several other reasons for the decision to discontinue a peering relationship. Thus, because tyntec initiated the peering offers a year after suing

Syniverse and because Syniverse states a reasonable basis for refusing to deal, Syniverse’s refusal to accept tyntec’s eleventh-hour peering offers displays no “willingness to sacrifice short-term profits” within the contemplation of Section 2. Therefore, Syniverse’s rejection of tyntec’s proposals constitutes no ongoing refusal to deal and serves no useful evidentiary function. * * *

Section 2 of the Sherman Act provides, “Every person who shall monopolize, or attempt to monopolize, or combine or conspire with any other person or persons, to monopolize any part of the trade or commerce among the several States, . . . shall be deemed guilty of a felony.” Although monopolistic behavior typically comprises collusive or conspiratorial conduct, antitrust law recognizes in a limited circumstance

the potential for monopolistic behavior to manifest in unilateral conduct. An anti- competitive refusal to deal is one of these limited circumstances. But “refusal to deal” jurisprudence comes shrouded in “weak” and precarious doctrinal justification. ROBERT H. BORK, THE ANTITRUST PARADOX: A POLICY AT WAR WITH ITSELF 346 (1993) (“[T]he doctrinal justifications for the differences in [refusal to deal]

outcome[s] appear weak.”). Accordingly, a posture of restraint should guide the analysis of antitrust liability for a refusal to deal. This is not to suggest that “refusal to deal” jurisprudence lacks any proper place in antitrust jurisprudence or serves no benefit in averting monopolistic conduct; rather, this is to suggest that “refusal to deal” jurisprudence needs no further muddling –– an inevitable result if unwarranted

liability is imposed in a case such as tyntec’s. Aspen Skiing Co. v. Aspen Highlands Skiing Corp., 472 U.S. 585 (1985), a seminal precedent for “refusal to deal” doctrine (and a case on which tyntec heavily relies), falls “at or near the outer boundary of § 2 liability,” as characterized in Verizon Commc’ns Inc. v. Law Offices of Curtis V. Trinko, LLP, 540 U.S. 398, 409 (2004), which

circumscribes Aspen within its idiosyncratic facts and which consequently constricts “refusal to deal” liability. Eleventh Circuit precedent further constricts the boundary of “refusal to deal” liability and narrows the conduct that falls within the boundary. See, e.g., Morris Communications Corp. v. PGA Tour, Inc., 364 F.3d 1288 (11th Cir. 2004); Covad

Communications Co. v. BellSouth Corp., 374 F.3d 1044 (11th Cir. 2004). At whatever undescribed boundary “refusal to deal” liability might lie following Aspen, Trinko, Morris, Covad, Novell, and similar precedent, Syniverse’s business conduct –– pervaded by deliberative, understandable, reasonable, and lucid efficiency

justifications –– falls somewhere outside the boundary of Section 2 liability. tyntec’s action stands consequentially distinct from Aspen, some of which distinctions warrant remark.3 The parties in Aspen shared a longstanding business relationship that created a “joint venture”; Syniverse and tyntec were essentially strangers until the assignment of Iris’s contract. The parties in Aspen shared a

3 Although aptly summarizing the facts in, and ably applying the law of, Aspen, the report perhaps awkwardly analogizes Syniverse’s free peering to free skiing on a competitor’s mountain. However, no awkwardness in any of the report’s analogies undermines the balance of the report’s well-reasoned and thorough analysis. voluntary and mutually profitable relationship; Syniverse and tyntec shared no relationship but for a contractually imposed duty induced by a third party. The Aspen defendant’s conduct introduced a sudden and unexpected reversal into the parties’ course of dealing; assuming (generously) a course of dealing between

Syniverse and tyntec, Syniverse’s conduct was foreseeable and anticipatorily announced.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Morris Communications Corp. v. PGA Tour, Inc.
364 F.3d 1288 (Eleventh Circuit, 2004)
Covad Communications Co. v. BellSouth Corp.
374 F.3d 1044 (Eleventh Circuit, 2004)
Aspen Skiing Co. v. Aspen Highlands Skiing Corp.
472 U.S. 585 (Supreme Court, 1985)
Novell v. Microsoft Corporation
731 F.3d 1064 (Tenth Circuit, 2013)
Steward Health Care System, LLC v. Blue Cross & Blue Shield
997 F. Supp. 2d 142 (D. Rhode Island, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Tyntec Inc. v. Syniverse Technologies, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/tyntec-inc-v-syniverse-technologies-llc-flmd-2020.