Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Due to HN's flaky Cloudflare 503 Bad Gateway error, I noticed that Cloudflare is also being affected by S3 being down in a similar but subtle way. See their status page's broken logo on the upper left hand corner.[1] It was actually directly linking to a S3 URL: https://s3.amazonaws.com/statuspage-production/pages-transac...

[1]: https://www.cloudflarestatus.com/



https://www.cloudflarestatus.com/ http://www.trellostatus.com/

Looks like they are both using the same solution for their status pages. The icon for trellostatus did also fail to display.


Was HN affected by Cloudbleed?

I would rather access HN without Cloudflare as man-in-the-middle, especially over HTTPS.


All websites that use Cloudflare were potentially affected by Cloudbleed which is what makes it such a terrible thing.

You will never know the exact damage, the only thing you can do to play it 100% safe is to rotate all credentials on sites using Cloudflare.

And you can't access HN without going through Cloudflare (unfortunately, but HN is having a hard enough time to keep up with traffic as it is, without Cloudflare it would perform a lot worse than it does).


Hahaha too bad.

Google Analytics, Cloudflare, AWS, those are things you can never escape from.


Disagree on Google Analytics.


EDIT: Misread parent.


Because your status page shouldn't depend on your own infrastructure. Literally the problem Amazon is having right now.


I guess they don't want to host their status page on their own CDN in case it went down too.


But only the logo image hosted on S3 is broken though. It seems to be preventable if they host the logo image together with their status page.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: