Orgoo, Inc. v. Rackspace US, Inc.

341 S.W.3d 34, 2011 WL 15953
CourtCourt of Appeals of Texas
DecidedJanuary 5, 2011
Docket04-09-00729-CV, 04-10-00058-CV
StatusPublished
Cited by18 cases

This text of 341 S.W.3d 34 (Orgoo, Inc. v. Rackspace US, Inc.) is published on Counsel Stack Legal Research, covering Court of Appeals of Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Orgoo, Inc. v. Rackspace US, Inc., 341 S.W.3d 34, 2011 WL 15953 (Tex. Ct. App. 2011).

Opinion

OPINION

Opinion by:

SANDEE BRYAN MARION, Justice.

This is an appeal from a no-answer default judgment rendered in favor of appel-lee, Rackspace US, Inc. Because we conclude appellant was not properly served with notice, we reverse the default judgment and remand to the trial court, and we deny the petition for writ of mandamus.

FACTUAL BACKGROUND

Rackspace US, Inc., which is an internet hosting company located in San Antonio, is a subsidiary of Rackspace Hosting, Inc. Through its subsidiaries, Rackspace Hosting operates computer servers that maintain networks and websites for a variety of businesses. Under a contract dated February 25, 2008, Rackspace US provided web-hosting services to appellant Orgoo, Inc., an internet start-up company located in California. According to Rackspace US, *37 beginning in August 2008, Orgoo failed to pay for services rendered by Rackspace US. In September and October 2008, Rackspace US discovered that the Orgoo website was allegedly being used to transmit and display images in which children were sexually abused and raped and that Orgoo’s live video streaming feature was allegedly showing child pornography and child molestation. Rackspace US notified the FBI. The FBI ordered Rackspace US to preserve all electronic evidence of the images displayed on Orgoo’s website. Rackspace US decided to suspend services to Orgoo and to disable the servers that hosted Orgoo’s website.

Orgoo’s CEO, Michael Kantor, demanded that Rackspace US resume hosting Or-goo’s website, and Rackspace US refused. On March 3, 2009, Orgoo sued Rackspace Hosting in California state court (the “California suit”). According to Rackspace US, this lawsuit violated the parties’ forum selection agreement, which required Orgoo to file its lawsuit in Bexar County, Texas. On June 23, 2009, the California court enforced the forum selection agreement and dismissed the suit. Meanwhile, in April 2009, Rackspace US filed the underlying lawsuit against Orgoo in Bexar County. In October 2009, Orgoo sued Racks-pace Hosting in Bexar County, asserting the same claims it asserted in the California suit. Orgoo’s lawsuit against Racks-pace Hosting has been abated.

PROCEDURAL BACKGROUND

On August 6, 2009 in the underlying lawsuit, the trial court rendered a default judgment against Orgoo and in favor of Rackspace US following Orgoo’s failure to appear. Less than ninety days later, Or-goo filed a Texas Rule of Civil Procedure 306a motion to extend post-judgment deadlines (hereinafter “Rule 306a motion”), alleging it did not receive notice of the signing of the default judgment until October 19, 2009. On November 3, 2009, a hearing was conducted on Orgoo’s Rule 306a motion and, at the conclusion of the hearing, the trial court denied the motion. A week later, Orgoo filed a motion pursuant to Texas Rule of Appellate Procedure 4.2(c) (hereinafter “Rule 4.2(c) motion”) asking the court to find the date on which Orgoo received notice or acquired actual notice of the judgment. On November 20, 2009, a hearing was conducted on Orgoo’s Rule 4.2(c) motion and, at the conclusion of the hearing, the trial court denied the motion. Because the trial court denied both motions, it did not sign a written order finding the date when Orgoo or Orgoo’s attorney first either received notice or acquired actual knowledge that the judgment was signed. On January 21, 2010, Orgoo filed a petition for writ of mandamus complaining of the trial court’s denial of its Rule 306a and Rule 4.2(c) motions to establish the operative date of the judgment. 3

Orgoo filed a notice of restricted appeal from the default judgment on November 13, 2009. Four days later, Orgoo filed a motion for new trial with the trial court. The court denied the motion without a hearing on December 16, 2009. On January 19, 2010, Orgoo filed an amended notice of appeal, stating it did not intend to amend or modify its restricted notice of appeal, but instead it intended to perfect for appeal the arguments it made in its motion for new trial under Craddock v. Sunshine Bus Lines, Inc., 134 Tex. 388, 133 S.W.2d 124 (1939).

OPERATIVE DATE OF THE JUDGMENT

In both its petition for writ of mandamus and on appeal, Orgoo asserts the trial *38 court abused its discretion by denying its Rule 306a motion and its Rule 4.2(c) motion and by refusing to make a finding on the operative date of the default judgment. If the operative date is August 6, 2009, the date the default judgment was signed, then this is a restricted appeal, and we may only consider whether there is error apparent on the face of the record. Norman Commc’n v. Tex. Eastman Co., 955 S.W.2d 269, 270 (Tex.1997) (per curiam). If the operative date is October 19, 2009, the date Orgoo alleges it first received notice of the default judgment, then this is a traditional Craddock appeal and, if Orgoo was properly served with process, in order to be granted a new trial after a no-answer default judgment, Orgoo must prove the now familiar Craddock elements. However, we do not reach the issues of whether the trial court erred by not making a finding on the operative date of the judgment 4 or whether the operative date can be implied from the trial court’s denial of the two motions because under either the restricted appeal standard or the Crad-dock standard, we conclude the trial court did not acquire jurisdiction over Orgoo because service was defective.

A default judgment rendered on defective service “will not stand” and rules governing service will be “rigidly enforced” on appellate review of the judgment. Hubicki v. Festina, 226 S.W.3d 405, 408 (Tex.2007). Here, the trial court rendered a default judgment in favor of Rackspace US based upon Rackspace US’s amended petition. However, the Texas Secretary of State certified that a copy of Rackspace US’s original petition was forwarded to Orgoo, but “process was returned ... bearing the notation Attempted — Not Known.” Our determination of whether, under these facts, the trial court acquired jurisdiction over Orgoo involves an analysis under both the restricted appeal standard and the Craddock standard.

RESTRICTED APPEAL

A party may bring a restricted appeal if the party: (1) filed notice of the restricted appeal within six months after the judgment was signed; (2) was a party to the underlying lawsuit; (3) did not participate in the hearing that resulted in the judgment complained of and did not timely file any postjudgment motions or requests for findings of fact and conclusions of law; and (4) error is apparent on the face of the record. Tex.R.App. P. 26.1(c), 30; Alexander v. Lynda’s Boutique, 134 S.W.3d 845, 848 (Tex.2004). The face of the record consists of all papers on file in the appeal. Norman Commc’n, 955 S.W.2d at 270. The first three requirements for filing a restricted appeal are not disputed in this appeal.

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

Related

Ex Parte E.C.
Court of Appeals of Texas, 2021
Ex Parte J. E.
Court of Appeals of Texas, 2020
Ex Parte Marco Martinez
Court of Appeals of Texas, 2018
in the Interest of C.G.
Court of Appeals of Texas, 2014

Cite This Page — Counsel Stack

Bluebook (online)
341 S.W.3d 34, 2011 WL 15953, Counsel Stack Legal Research, https://law.counselstack.com/opinion/orgoo-inc-v-rackspace-us-inc-texapp-2011.