One has to wonder when the board realises Dane was a bad replacement for JGC. These outages are getting ridiculous
Cloudflare outage on February 20, 2026
71–80 of 135 posts
Re: Cloudflare outage on February 20, 2026
#72They should have rewritten this code in Rust using these brilliant language models. /jk
Re: Cloudflare outage on February 20, 2026
#73I'm honestly amazed that a company CF's size doesn't have a neat little cluster of Mac Minis running OpenClaw and quietly taking care of this for them.
Re: Cloudflare outage on February 20, 2026
#74Re: Cloudflare outage on February 20, 2026
#75Reliability was/is CF's label. It's alarming already. Too many outages in the past months. CF should fix it, or it becomes unacceptable and people will leave the platform. I really hope they will figure things out.
I have many things dependent on Cloudflare. That makes me root for Cloudflare and I think I'm not the only one. Instead of finding better options we're getting stuck on an already failing HA solution. I wonder what caused this.
There are no alternatives, and those alternatives that did exist back in the day, had to shut down due to either going out of business or not being able to keep a paygo model.
Not everybody needs cloudflare, but those that need it and aren't major enterprises, have no other option.
Re: Cloudflare outage on February 20, 2026
#76Earlier quoted context omitted.
I have many things dependent on Cloudflare. That makes me root for Cloudflare and I think I'm not the only one. Instead of finding better options we're getting stuck on an already failing HA solution. I wonder what caused this.
There are no alternatives, and those alternatives that did exist back in the day, had to shut down due to either going out of business or not being able to keep a paygo model. Not everybody needs cloudflare, but those that need it and aren't major enterprises, have no other option.
Lots of people who think they need Cloudflare don't. What are you using it for?
Re: Cloudflare outage on February 20, 2026
#77Earlier quoted context omitted.
I have many things dependent on Cloudflare. That makes me root for Cloudflare and I think I'm not the only one. Instead of finding better options we're getting stuck on an already failing HA solution. I wonder what caused this.
There are no alternatives, and those alternatives that did exist back in the day, had to shut down due to either going out of business or not being able to keep a paygo model. Not everybody needs cloudflare, but those that need it and aren't major enterprises, have no other option.
Bunny.net? Doesn't have near the same feature set as Cloudflare, but the essentials are there and you can easily pay as you go with a credit card.
Re: Cloudflare outage on February 20, 2026
#78It's something we debated in our team: if there's an API that returns data based on filters, what's the better behavior if no filters are provided - return everything or return nothing?
The consensus was that returning everything is rarely what's desired, for two reasons: first, if the system grows, allowing API users to return everything at once can be a problem both for our server (lots of data in RAM when fetching from the DB => OOM, and additional stress on the DB) and for the user (the same problem on their side). Second, it's easy to forget to specify filters, especially in cases like "let's delete something based on some filters."
So the standard practice now is to return nothing if no filters are provided, and we pay attention to it during code reviews. If the user does really want all the data, you can add pagination to your API. With pagination, it's very unlikely for the user to accidentally fetch everything because they must explicitly work with pagination tokens, etc.
Another option, if you don't want pagination, is to have a separate method named accordingly, like ListAllObjects, without any filters.
Re: Cloudflare outage on February 20, 2026
#79It's something we debated in our team: if there's an API that returns data based on filters, what's the better behavior if no filters are provided - return everything or return nothing? The consensus was that returning everything is rarely what's desired, for two reasons: first, if the system grows, allowing API users to return everything at once can be a problem both for our server (lots of data in RAM when fetching…
I like your thought process around the ‘empty’ case. While the opposite of a filter is no filter, to your point, that is probably not really the desire when it comes to data retrieval. We might have to revisit that ourselves.
Re: Cloudflare outage on February 20, 2026
#80Earlier quoted context omitted.
There are no alternatives, and those alternatives that did exist back in the day, had to shut down due to either going out of business or not being able to keep a paygo model. Not everybody needs cloudflare, but those that need it and aren't major enterprises, have no other option.
Lots of people who think they need Cloudflare don't. What are you using it for?
L7 DDoS protection and global routing + CDN, there is not a single paygo provider that can handle the capacity CF can, especially not at this price range (mitigated attacks distributed from approximately 50-90k ips, adding up to about 300-700k rps).
We tried Stackpath, Imperva (Incapsula back in the day), etc but they were either too expensive or went out of business.