Cloudflare Network Performance Issues • Hacker News Board

Re: Cloudflare Network Performance Issues

#221

Post by bovermyer » Tue, Jul 02, 2019, 2:26 PM UTC

luckylion wrote: post #212

bovermyer wrote: post #156

Earlier quoted context omitted.

Education and positive reinforcement. Teach people the right way to do things, and then make that behavior self-rewarding.

What if that behavior isn't self-rewarding and is actually expensive? Not using Cloudflare, Google Maps, Analytics et all means you need to use something else, need to spend attention points somewhere, need to pay for the services. Very few people will do that because "it's the right thing to do".

I didn't say it was easy or obvious. If it were, I would be out of a job.

Re: Cloudflare Network Performance Issues

#222

Post by eternalny1 » Tue, Jul 02, 2019, 2:27 PM UTC

They have mitigated it ...

https://twitter.com/eastdakota/status/1146057946494713858

Re: Cloudflare Network Performance Issues

#223

Post by sebastianconcpt » Tue, Jul 02, 2019, 2:27 PM UTC

Wonder how can we use CloudFlare and have a fallback plan in place for situations like this. What would be a good architecture for this? So far I've read that would be good to have the registrar out of CloudFlare and use them as CDN only. What else?

Re: Cloudflare Network Performance Issues

#224

Post by acdha » Tue, Jul 02, 2019, 2:27 PM UTC

Heliosmaster wrote: post #175

buildbuildbuild wrote: post #152

Cloudflare: Your status page showed "all systems operational" for over 20 minutes while your primary domain was returning a 502 error. Please change this to update automatically, many other engineering teams depend on you. https://i.imgur.com/qHBM2JW.png

Are you sure it wasn't cached? For us it was showing correctly the incident...

It might have been cached on the server but was not cached on my clients: I did a forced refresh and used a private browser window but it only showed the “almost everything is good” view throughout the duration of the incident.

The actual incident page was correct.

Re: Cloudflare Network Performance Issues

#225

Post by rc_kas » Tue, Jul 02, 2019, 2:28 PM UTC

bpicolo wrote: post #199

hu3 wrote: post #179

Earlier quoted context omitted.

https://www.digitalocean.com/ frontpage working for me: https://i.imgur.com/8yJRXVI.png

The outage appears to have ended between that post and your post.

Yeah, not a long outage, but a big one.

Re: Cloudflare Network Performance Issues

#226

Post by sauldcosta » Tue, Jul 02, 2019, 2:28 PM UTC

po1nter wrote: post #210

sauldcosta wrote: post #174

Some people on Twitter are reporting that it's due to a DDoS. http://www.digitalattackmap.com/#anim=1&color=0&country=ALL&... seems to indicate Iran is the source?

The date on your link is February 21st.

Right you are, heh. Not sure why it jumped back to that date. False alarm.

Re: Cloudflare Network Performance Issues

#227

Post by buildbuildbuild » Tue, Jul 02, 2019, 2:28 PM UTC

btown wrote: post #192

Heliosmaster wrote: post #175

Earlier quoted context omitted.

Are you sure it wasn't cached? For us it was showing correctly the incident...

If cloudflarestatus.com isn't serving text content as Cache-Control: no-cache, that's itself an egregious bug.

Their status page is hosted on Cloudfront, perhaps adding an unintended caching layer.

Re: Cloudflare Network Performance Issues

#228

Post by philipwhiuk » Tue, Jul 02, 2019, 2:29 PM UTC

pmlnr wrote: post #72

Good. I'm tired of people not learning that trusting a single gateway with 50% of the internet is bad. Yes, I know, free DDOS protection. There has to be another way of doing this, some mesh based DDOS protection or so.

It is slightly ironic that the best defence for a distributed problem is to build a single point of failure.

Re: Cloudflare Network Performance Issues

#229

Post by lkbm » Tue, Jul 02, 2019, 2:31 PM UTC

hoechst wrote: post #202

lkbm wrote: post #142

Earlier quoted context omitted.

This seems like a case for putting more of the internet through a single gateway. Having my downtime correlated with everyone else's means users will be more forgiving because they'll perceive it as "the Internet's down" rather than "lkbm's site is broken". (We saw this with CloudFlare. Some users were pissed, and others jumped in with "it's not their fault; AWS is down". That doesn't happen when our stuff specifical…

How cares whose fault it is? In the end, you're not able to provide service to your users and you potentially lose money.

The argument being made above only holds water if Cloudflare has worse uptime than smaller providers, and that it's because they're big.

This is often the case when monopolies realize they're in a position where they can get away with sucking, but I don't believe that to be the case with Cloudflare yet.

Re: Cloudflare Network Performance Issues

#230

Post by NikolaeVarius » Tue, Jul 02, 2019, 2:31 PM UTC

grey-area wrote: post #182

Throughout this outage, https://www.cloudflarestatus.com/ continued to show green - all services operational, with almost all services marked 'operational' and some vague cryptic message about users in this region being affected: Investigating - Cloudflare is observing network performance issues. Customers may be experiencing 502 errors while accessing sites on Cloudflare. We are working to mitigate impact to Interne…

This is not my experience, I have received many updates both through email and updates to the cloudflare status page throughout the incident, except for possibly the first 10 minutes