Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Experiencing Latency Issues

cloudflarestatus.com

Post reply on HN
Print view View original

61–69 of 69 posts

Re: Cloudflare Experiencing Latency Issues

#61

Post by dang »

stillicidious wrote: post #35
jgrahamc wrote: post #31

Earlier quoted context omitted.

I would have posted faster but I was too busy doing my own little bit of debugging which consisted of 1. dig @1.1.1.1 jgc.org 2. nc -v 104.22.11.223 80 3. curl -v https://jgc.org/cdn-cgi/trace 4. curl -v https://jgc.org/ Hmm #1 was fast so network is routing OK. Hmm #2 was fast so TCP is OK. Hmm #3 was fast so I know (because I worked on that code) that this code path is good. Hmm #4 is slow so that means component X…

I'm glad commenting on HN takes priority over notifying your enterprise customers.

First, please don't be an asshole and/or be snarky on HN. We don't want that here. (See https://news.ycombinator.com/newsguidelines.html.)

Second, "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith." (also in https://news.ycombinator.com/newsguidelines.html)

Third, punishing users for discussing something work-related is one of the worst things you can do to damage this place. We want knowledgeable comments, and for most people, our work is what we know the most about. Disincentivizing that is a losing proposition (https://hn.algolia.com/?query=disincent%20by:dang&dateRange=...) so please don't.

Re: Cloudflare Experiencing Latency Issues

#62

Post by vinay_ys »

jgrahamc wrote: post #31
tentacleuno wrote: post #12

Earlier quoted context omitted.

I really like it when people in your position at such a big company post on here, even if it is a brief comment like this. Thank you!

I would have posted faster but I was too busy doing my own little bit of debugging which consisted of 1. dig @1.1.1.1 jgc.org 2. nc -v 104.22.11.223 80 3. curl -v https://jgc.org/cdn-cgi/trace 4. curl -v https://jgc.org/ Hmm #1 was fast so network is routing OK. Hmm #2 was fast so TCP is OK. Hmm #3 was fast so I know (because I worked on that code) that this code path is good. Hmm #4 is slow so that means component X…

What was component X? Was it a buggy rollout?

Re: Cloudflare Experiencing Latency Issues

#63

Post by ithkuil »

tailspin2019 wrote: post #57
ithkuil wrote: post #55

Earlier quoted context omitted.

That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible.

> That rule is great for one single person (a pilot). In corporate incident management we can do better, and not blocking communication because you're overwhelmed with keeping the system up; in fact proper incident management workflows designate different people with different roles and delegates communication duties to a dedicated person if possible. I agree with you, but Cloudflare seem to have done exactly what yo…

Yes, my comment was about the Aviate Navigate Communicate rule, not about cloudflare's response

Re: Cloudflare Experiencing Latency Issues

#64

Post by jgrahamc »

tuananh wrote: post #60
jgrahamc wrote: post #31

Earlier quoted context omitted.

I would have posted faster but I was too busy doing my own little bit of debugging which consisted of 1. dig @1.1.1.1 jgc.org 2. nc -v 104.22.11.223 80 3. curl -v https://jgc.org/cdn-cgi/trace 4. curl -v https://jgc.org/ Hmm #1 was fast so network is routing OK. Hmm #2 was fast so TCP is OK. Hmm #3 was fast so I know (because I worked on that code) that this code path is good. Hmm #4 is slow so that means component X…

you often do you code these days?

Hardly ever. If I start a project I don’t end up having time to finish or maintain it which isn’t fair to the team.

If I write something it’s for my own use. And I like to write things that test Cloudflare. Доверяй, но проверяй.

Re: Cloudflare Experiencing Latency Issues

#65

Post by jgrahamc »

vinay_ys wrote: post #62
jgrahamc wrote: post #31

Earlier quoted context omitted.

I would have posted faster but I was too busy doing my own little bit of debugging which consisted of 1. dig @1.1.1.1 jgc.org 2. nc -v 104.22.11.223 80 3. curl -v https://jgc.org/cdn-cgi/trace 4. curl -v https://jgc.org/ Hmm #1 was fast so network is routing OK. Hmm #2 was fast so TCP is OK. Hmm #3 was fast so I know (because I worked on that code) that this code path is good. Hmm #4 is slow so that means component X…

What was component X? Was it a buggy rollout?

A proxy that serves traffic. No, it was way more complicated than “buggy rollout”.

Re: Cloudflare Experiencing Latency Issues

#66

Post by stillicidious »

dang wrote: post #61
stillicidious wrote: post #35

Earlier quoted context omitted.

I'm glad commenting on HN takes priority over notifying your enterprise customers.

First, please don't be an asshole and/or be snarky on HN. We don't want that here. (See https://news.ycombinator.com/newsguidelines.html .) Second, " Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith. " (also in https://news.ycombinator.com/newsguidelines.html ) Third, punishing users for discussing something work-related is o…

I'd suggest you are doing far more damage to the reputation of the board by conflating commentary with free marketing. The comment I replied to was the latter. If advertising is permitted where critique from actual paying users is openly punished, what is that saying about the board?

As for the extremely disappointing asshole comment, coming from a moderator is quite frankly astounding. "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith".

Re: Cloudflare Experiencing Latency Issues

#67

Post by Buttons840 »

sneak wrote: post #39
ziddoap wrote: post #33

Earlier quoted context omitted.

> This reminds me of the younger generation sometimes perceiving messages ending in a period as rude. I've never seen any comments regarding a single period, but I've seen comments (and sometimes agree with them) regarding the perceived rudeness when ending messages in ellipses. "Good job..." seems almost sarcastic compared to "Good job.".

Good job. seems almost patronizing in comparison with good job Then again, I grew up on IRC.

Studies have shown the same.

Re: Cloudflare Experiencing Latency Issues

#68

Post by maxgashkov »

jgrahamc wrote: post #64
tuananh wrote: post #60

Earlier quoted context omitted.

you often do you code these days?

Hardly ever. If I start a project I don’t end up having time to finish or maintain it which isn’t fair to the team. If I write something it’s for my own use. And I like to write things that test Cloudflare. Доверяй, но проверяй.

I see comrades you have on your team have taught you well /jk

Re: Cloudflare Experiencing Latency Issues

#69

Post by maxgashkov »

jgrahamc wrote: post #46
tailspin2019 wrote: post #32

Earlier quoted context omitted.

Now you're just showing off :)

Allow an old man the fantasy that he still knows how the whole of the system works.

That's a huge problem for companies of almost any scale. Can you shed some light on tools used internally in Cloudflare for tracing?
Post reply on HN