Viewing profile — eastdakota
eastdakota
HN member- Joined
- Mon, Dec 06, 2010, 11:55 PM UTC
- HN karma
- 11,160
- Public activity
- 696 items
- HN profile
- View on Hacker News ↗
About eastdakota
Recent public activity
-
comment
Comment #48895079
You’re confusing us with Google. We don’t have a visual CAPTCHA.
-
comment
Comment #45979057
That’s not accurate. As with any incident response there were a number of theories of the cause we were working in parallel. The feature file failure was one identified as potentia…
-
comment
Comment #45978859
There’s lots of things we did while we were trying to track down and debug the root cause that didn’t make it into the post. Sorry the WARP takedown impacted you. As I said in a co…
-
comment
Comment #45978825
Team has a good sense, typically. In this case, the names of the columns in the Bot Management feature table seemed sensitive. The person who included that in the master document w…
-
comment
Comment #45978769
* published less than 12 hours from when the incident began. Proud of the team for pulling together everything so quickly and clearly.
-
comment
Comment #45978730
Next time open your dev console in your window and look at how much is going on in the background.
-
comment
Comment #45978719
We incorrectly thought at the time it was attack traffic coming in via WARP into LHR. In reality it was just that the failures started showing up there first because of how the bad…
-
comment
Comment #45974882
Chicken burrito from Coyo Taco in Lisbon. I am not proud of this. It’s worse than ordering from Chipotle. But there are no Chipotle’s in Lisbon… yet.
-
comment
Comment #45974320
Well… we have a culture of transparency we take seriously. I spent 3 years in law school that many times over my career have seemed like wastes but days like today prove useful. I …
-
comment
Comment #45974213
Can attest: not a single LLM used. Couldn’t if I tried. Old school. And not entirely proud of that.
-
comment
Comment #45974038
That’s correct.
-
comment
Comment #45974030
Because we initially thought it was an attack. And then when we figured it out we didn’t have a way to insert a good file into the queue. And then we needed to reboot processes on …
-
comment
Comment #45974009
We don’t know. Suspect it may just have been a big uptick in load and a failure of its underlying infrastructure to scale up.
-
story
Cloudflare outage on November 18, 2025 post mortem
Related: Cloudflare Global Network experiencing issues - https://news.ycombinator.com/item?id=45963780 - Nov 2025 (1580 comments)
-
comment
Comment #45588309
That definitely is one not-wrong conclusion.
-
comment
Comment #45588305
Blog run by the engineering team. I wouldn’t even know how to veto a post if I wanted to. Not in our DNA.
-
comment
Comment #45376254
I’m not going anywhere anytime soon.
- story
- story
-
comment
Comment #45046507
Free customers are served from the nearest location where we have capacity. If we’re capacity constrained then free customers will be the first to be rerouted to another facility w…
-
comment
Comment #44218810
I agree with Kenton’s aside.
-
comment
Comment #43396033
We’re in Munich, pretty close, and Lisbon, which is lovely. Unlikely Austria any time soon.
-
comment
Comment #43396009
Had no idea there was a patent. Even if we had, think we’d have risked it.
-
comment
Comment #43393152
If it were merely marketing spend for customer acquisition, I bet the ROI on the lava lamp wall in SF has been 100,000x. This isn’t hard to figure out.
-
comment
Comment #43392458
Actually, it’s because we believe innovation is easier the further you are from HQ. And Portugal is wonderful. I’m spending about 4 months of the year there with the team who hail …