Company: FSLY
Filing Date: 2025-05-07
Form Type: 10-Q
Source: 0001517413-25-000111
Chunk: 23

Company: Fastly, Inc.
Filing Date: 2025-05-07
Form: 10-Q
Item: Part I, Item 3
Chunk 23
---
 dismiss on March 17, 2025. Defendants filed a reply in support of the motion to dismiss on April 30, 2025. We anticipate that we may be a target for lawsuits in the future, as we have been in the past. Any litigation to which we are a party may result in an onerous or unfavorable judgment that may not be reversed on appeal, or we may decide to settle lawsuits on similarly unfavorable terms. Any such negative outcome could result in payments of substantial monetary damages and accordingly our business could be seriously harmed. The results of lawsuits and claims cannot be predicted with certainty. Regardless of the final outcome, defending these claims, and associated indemnification obligations, are costly and can impose a significant burden on management and employees, and we may receive unfavorable preliminary, interim, or final rulings in the course of litigation, which could seriously harm our business.

We may not be able to scale our business quickly enough to meet our customers’ growing needs. If we are not able to grow efficiently, our business could be harmed.

As usage of our edge cloud computing platform grows and as the breadth of use cases for our platform expands, we will need to devote additional resources to improving our platform architecture, integrating with third-party applications and maintaining infrastructure performance. In addition, we will need to appropriately scale our processes and procedures that support our growing customer base, including increasing our number of POPs around the world and investments in systems, training, and customer support.

58

Any failure of or delay in these efforts could cause impaired system performance and reduced customer satisfaction. These issues could reduce the attractiveness of our platform to customers, resulting in decreased sales to new customers, lower renewal rates by existing customers, the issuance of service credits, or requested refunds, which would hurt our revenue growth and our reputation. Even if we are able to upgrade our systems and expand our staff, any such expansion will be expensive and complex, and require the dedication of significant management time and attention. We could also face inefficiencies or operational failures as a result of our efforts to scale our cloud infrastructure, such as by over investing in systems and equipment to support anticipated growth in our platform. We cannot be sure that the expansion and improvements to our cloud infrastructure will be effectively implemented on a timely basis, if at all, and such failures would harm our business.

We may have insufficient transmission bandwidth and colocation space, which could result in disruptions to our platform and loss of revenue.

Our operations are dependent in part upon transmission bandwidth provided by third-party telecommunications network providers and access to