41–50 of 69 posts
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?
They did all three of those in the space of a few minutes (if you were checking their status page - which you can subscribe to by the way).
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.".
Should be cleared up now. Sorry about that.
Thanks for the post. Yesterday you strongly rebutted me for saying that the widespread outages also were impacting Cloudflare [0], even tho it wasn't obvious to me at that time who was being impacted by who. Knowing the intricate connections of all the app and infrastructure and cloud providers is tricky! When stuff goes down, the blame gets spread around. [0] https://news.ycombinator.com/item?id=29568319 edit: chang…
Earlier quoted context omitted.
Thanks for the post. Yesterday you strongly rebutted me for saying that the widespread outages also were impacting Cloudflare [0], even tho it wasn't obvious to me at that time who was being impacted by who. Knowing the intricate connections of all the app and infrastructure and cloud providers is tricky! When stuff goes down, the blame gets spread around. [0] https://news.ycombinator.com/item?id=29568319 edit: chang…
Sorry if that came across harshly. ASCII is a tough medium.
To be direct - yesterday I spotted what seemed like an Internet-wide issue that was also impacting Cloudflare. You told me yesterday that no in fact, there was no impact on Cloudflare. Today there is a post about a separate issue where there is an impact on Cloudflare. In my mind I make the connection between these two events, and on the one hand the quick and direct denial of the issue being that of Cloudflare on the first day, but today an acknowldgement of issues, even if they were a different set of problems.
It would be helpful on outages where Cloudflare is showing an outage when the problem doesn't originate with Cloudflare to put on your own error page an indication of where the error might be. I know this might be touchy to do so, but you should feel free to point fingers when you know that an outage to your client is caused by another party.
For example:
"Error. Cloudflare reports this site is down. Issues point to an outage with [AWS, Google, Azure, Oracle That would help make it clear that yes, there is an outage, and no, Cloudlfare is not the proximal cause.
All this chatter about your use of words and my use of words kinda misses the main point of what I was trying to communicate.
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…
Now you're just showing off :)
Truly loving the service but we had to "unproxy" our website. When it works, it brings so much value. I'm guessing our issue isn't trivial to solve though.
Earlier quoted context omitted.
Sorry if that came across harshly. ASCII is a tough medium.
Yes text is indeed devoid of context and sentiment. But to the main point, I fear that the comments on tone are a bit beside the point anyways. So let's move past that to talk about what I really wanted to comment on. To be direct - yesterday I spotted what seemed like an Internet-wide issue that was also impacting Cloudflare. You told me yesterday that no in fact, there was no impact on Cloudflare. Today there is a…
I would love if their customer service was so fast. They keep ghosting us for 7 days. Poking the on a live chat results in "hey we'll look at this". Truly loving the service but we had to "unproxy" our website. When it works, it brings so much value. I'm guessing our issue isn't trivial to solve though.