React caused an outage for Cloudflare?
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
We all fell for it…
Theo - t3․gg
216.3k views
Vercel accuses Cloudflare of stealing
Theo - t3․gg
71.8k views
I can't take it anymore.
Theo - t3․gg
122.9k views
Cloudflare takes on Next.js
Theo - t3․gg
98.5k views
How React took down Cloudflare
ThePrimeTime
133.7k views
The Future of React
Theo - t3․gg
50.7k views
Amazon bets big on React Native
Theo - t3․gg
48.2k views
React is killing the web
Theo - t3․gg
59.9k views
Was I wrong about Cloudflare?
Theo - t3․gg
57.1k views
React 19.2 Dropped Early???
Theo - t3․gg
55.4k views
Top Comments (10)
TLDR; they didn't use react query
ddos prevention company ddos'ed themselves due to bad react code funniest shit i have heard in a while
I hate the fact that they tried pointing blame on the web dev team. Just shows they have bigger organizational / management problems they need to fix first.
They didn't blame useEffect, it's clear that it's their own admission of fault. they said "we mistakenly included a problematic object in the dependency array" not, "react forced us to put that object.
Both the frontend and backend code were problematic here. I figure they preferred to have the frontend take the fall because they didn't want to go into details of their backend code for security reasons. That said, there are many things wrong here. What the hell was this response? If they noticed a lot of failures right after they deployed the new backend, rolling back should have been the first instinct. This outage could have been 5 minutes long and they would have been spared a Theo rant.
Title of the video : Did Cloudflare lie? 30 seconds into the video : I love the fact they put out this public postmortem and are transparent about this.
Where do they blame React and useEffect exactly? They just explain what happened, right?
The Cloudflare dashboard is pretty shoddy right now and this explains why. The amount of layout shifts and loading spinners per page navigation is just ridiculous.
The react code is irrelevant. Their ddos protection failed. If it didn’t then the dashboard api calls would be harmless.
bro went nuts at the outro xD
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
TLDR; they didn't use react query
ddos prevention company ddos'ed themselves due to bad react code funniest shit i have heard in a while
I hate the fact that they tried pointing blame on the web dev team. Just shows they have bigger organizational / management problems they need to fix first.
They didn't blame useEffect, it's clear that it's their own admission of fault. they said "we mistakenly included a problematic object in the dependency array" not, "react forced us to put that object.
Both the frontend and backend code were problematic here. I figure they preferred to have the frontend take the fall because they didn't want to go into details of their backend code for security reasons. That said, there are many things wrong here. What the hell was this response? If they noticed a lot of failures right after they deployed the new backend, rolling back should have been the first instinct. This outage could have been 5 minutes long and they would have been spared a Theo rant.
Title of the video : Did Cloudflare lie? 30 seconds into the video : I love the fact they put out this public postmortem and are transparent about this.
Where do they blame React and useEffect exactly? They just explain what happened, right?
The Cloudflare dashboard is pretty shoddy right now and this explains why. The amount of layout shifts and loading spinners per page navigation is just ridiculous.
The react code is irrelevant. Their ddos protection failed. If it didn’t then the dashboard api calls would be harmless.
bro went nuts at the outro xD