Cloudflare: service incidents and stable hiring
From October 14 to October 26, Cloudflare reported seven separate technical incidents affecting data centers in the U.S. Despite these outages, the company continues active hiring, with 457 public job postings.
Key points
- During the second half of October, the company faced a series of incidents primarily affecting the Ashburn data center.
- Beyond the Ashburn issues, Cloudflare recorded outages in other locations, including increased errors in Portland, network congestion in Dallas and Seattle, and delays building Cloudflare Workers.
- Cloudflare maintains stable hiring: as of the latest report, the company has 457 published job postings, with 433 open positions.
Service incidents at data centers
During the second half of October, the company faced a series of incidents primarily affecting the Ashburn data center. Problems included HTTP 502 errors, network instability, and service interruptions for Durable Objects, R2, Workflows, and Cloudflare Workers. An October 15 incident affecting Ashburn and Newark was classified by the company as having major impact.
Other technical events
Beyond the Ashburn issues, Cloudflare recorded outages in other locations, including increased errors in Portland, network congestion in Dallas and Seattle, and delays building Cloudflare Workers. All mentioned incidents were resolved within one day or less; technical measures were implemented to correct them, and processing queues returned to normal levels.
Labor market activity
Cloudflare maintains stable hiring: as of the latest report, the company has 457 published job postings, with 433 open positions. The vast majority of roles offer a hybrid work format (348 postings). Most requests are concentrated in Solution Engineering (69 postings), Engineering (68 postings), and Field Sales (59 postings).
Risks and uncertainty
Recurring network problems in Ashburn may indicate infrastructure instability at that specific location. The company has not disclosed the reasons for these regular outages. Furthermore, the potential financial impact of these incidents, including possible compensation payments to clients for failure to meet service level agreements (SLAs), has not been disclosed.
What to monitor
Shareholders should monitor corporate service status reports and financial filings. Specifically, it is important to track whether Ashburn incidents lead to client compensation payments, which could impact profitability.
Original sources
- Elevated number of 5XX errors in PDX
- Possible Network Congestion in Dallas, TX, United States (DFW)
- Network Performance Issues in Eastern North America
- Elevated errors for some requests in Ashburn, Virginia
- Network congestion in Portland and Seattle, US
- Network Performance Issues in Ashburn
- Cloudflare Workers build delays
- Cloudflare, Inc. job board (greenhouse: cloudflare)
Cite this article
The fingerprint identifies the exact version of each original that the article was written from; the original stays at its source.
Follow Cloudflare
A notification in your browser or on your phone when we publish about Cloudflare. Free, no email, no account, no app.
Prepared by AI from official company documents; automatic checks and an AI editor review it before publication, and not every article is read by a person. This is not investment advice. Editorial standards
