• News/
  • https://www.theregister.com/2025/09/18/cloudflare_ddosed_itself/

Cloudflare DDoSed itself with React useEffect hook blunder

The Register
·
Tim Anderson
·
Published Sep 18, 2025
·
Updated

Cloudflare has confessed to a coding error using a React useEffect hook, notorious for being problematic if not handled carefully, that caused an outage for the platform's dashboard and many of its APIs. The outage was on September 12, lasted for over an hour, and was triggered by a bug in the dashboard, which caused "repeated, unnecessary calls to the Tenant Service API," according to VP of engineering Tom Lianza. This API is part of the API request authorization logic and therefore affected other APIs. The cause was hard to troubleshoot since the apparent issue was with the API availability, disguising the fact that it was the dashboard that was overloading it. Lianza said the core issue was a React useEffect hook with a "problematic object in its dependency array." The useEffect hook is a function with parameters including a setup function that returns a cleanup function, and an optional list of dependencies. The setup function runs every time a dependency changes. In this Cloudflare case, the function made calls to the Tenant Service API, and one of the dependencies was an object that was "recreated on every state or prop change." The consequence was that the hook ran repeatedly during a single render of the dashboard, when it was only intended to run once. The function ran so often that the API was overloaded, causing the outage. The useEffect hook is powerful but often overused. The documentation is full of warnings about misuse and common errors, and encouragement to u...

Read full article

Affected Software

2 affected components
Cloudflare dashboard
Cloudflare API
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What was the cause of the Cloudflare outage?

The outage was caused by a coding error involving a React useEffect hook.

2

When did the Cloudflare outage occur?

The outage took place on September 12, 2025.

3

What services were impacted by the Cloudflare outage?

The outage affected the Cloudflare dashboard and many of its APIs.

4

Why is the useEffect hook considered problematic?

The useEffect hook can lead to issues if not handled carefully, which contributed to the outage.

5

Which company experienced this self-inflicted DDoS?

The company that experienced the self-inflicted DDoS is Cloudflare.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203