4 ms·
> I see nothing wrong with Cloudflare just explaining what happened, even though they had nothing to do with it. You kinda inadvertently highlighted the issue:
by Ansil849 5y ago
> I see nothing wrong with Cloudflare just explaining what happened, even though they had nothing to do with it.
You kinda inadvertently highlighted the issue: because they had nothing to do with it, they do not know what actually happened. They can pontificate about likely causes, just like others in the industry can, but they have no idea what actually caused the issue.
- bikeshaving 5y agoAt no point in the blog post did they offer any conjecture about what was happening at Facebook. All of their information was general descriptions of DNS and BGP, or descriptions of how the Facebook outage was experienced on their end from running a DNS resolver. That in and of itself makes for an interesting and informative perspective.
- Godel_unicode 5y agoIf you read the blog post, you'll see that it's speculation-free facts about what happened. BGP announcements happened at time t, DNS started failing at t+n, DNS requests spiked, BGP updates happened at t', DNS returned to normal at t'+n.
- dfdz 5y agoI assume you did not read the blog post? It’s just a technical post describing the outage from Cloudflare’s perspective and mostly focuses on the increased traffic to 1.1.1.1 and the latency it caused You can pontificate about likely contents of Cloudfare’s blog post, just like others who did not read it, but clearly you have no idea what it actually contains
- Lazare 5y agoI think your criticism is unfair. > They can pontificate about likely causes They can, but they didn't.
- rattray 5y agoThey don't claim to; they had useful information to share and shared it in a way that was helpful and informative to the lay engineer.