Live data from Hacker News

Cloudflare Experiencing Latency Issues

cloudflarestatus.com

31–40 of 69 posts

Re: Cloudflare Experiencing Latency Issues

#31
post #8

Should be cleared up now. Sorry about that.

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 is slow but still working.

Of course, in parallel I'm in a conference call with about 40 other people who have actual access to monitoring and systems and other things who can see exactly where things are.

But I was damn close with four commands and gave me confidence in what people were saying. But, I have to say, Cloudflare's internal distributed tracing system is pretty cool because I got sent a trace and you could see right where the slowdown was.

Re: Cloudflare Experiencing Latency Issues

#32

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…

Now you're just showing off :)

Re: Cloudflare Experiencing Latency Issues

#33
post #23

Earlier quoted context omitted.

In my experience, a lot of Americans interpret direct, no-wasted-word statements as aggressive or confrontational. Euphemism and indirect implication is the norm in American communication, much to my dismay. It can wrap around to extremes sometimes, too. https://sneak.berlin/20191201/american-communication/

This reminds me of the younger generation sometimes perceiving messages ending in a period as rude. I'm also sometimes surprised by how effectively a simple statement like "I don't want to spend money on that" can shut down even a pushy salesman. Or even the simple "No." can work wonders.

>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.".

Re: Cloudflare Experiencing Latency Issues

#34
post #29

Earlier quoted context omitted.

This is a fair statement. Didn't use to be this way - I blame the participation trophy era of kids.

You're engaging in it yourself right now by using euphemism/implication to suggest a certain type of person instead of just saying "whiny, overly sensitive children" (which I assume is what you mean). You should remove the plank from your own eye, first. You don't get to blame others for your voluntarily chosen courses of action.

You're fast! Good job. I present you with a trophy.

Re: Cloudflare Experiencing Latency Issues

#35

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…

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

Re: Cloudflare Experiencing Latency Issues

#36

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.

We have whole teams of people to get status up and inform people and support them.

Re: Cloudflare Experiencing Latency Issues

#37

Earlier quoted context omitted.

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

We have whole teams of people to get status up and inform people and support them.

And yet I'm learning about this outage from HN. How did that happen?

Re: Cloudflare Experiencing Latency Issues

#38

Earlier quoted context omitted.

We have whole teams of people to get status up and inform people and support them.

And yet I'm learning about this outage from HN. How did that happen?

Suggest subscribing on https://www.cloudflarestatus.com/ as that was updated long before I came to HN to say anything (which was only after the incident was resolved).

Re: Cloudflare Experiencing Latency Issues

#39
post #33

Earlier quoted context omitted.

This reminds me of the younger generation sometimes perceiving messages ending in a period as rude. I'm also sometimes surprised by how effectively a simple statement like "I don't want to spend money on that" can shut down even a pushy salesman. Or even the simple "No." can work wonders.

> 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.

Re: Cloudflare Experiencing Latency Issues

#40
post #29

Earlier quoted context omitted.

You're engaging in it yourself right now by using euphemism/implication to suggest a certain type of person instead of just saying "whiny, overly sensitive children" (which I assume is what you mean). You should remove the plank from your own eye, first. You don't get to blame others for your voluntarily chosen courses of action.

You're fast! Good job. I present you with a trophy.

[deleted]
Post reply on HN