331–340 of 448 posts
Earlier quoted context omitted.
Wouldn't this expose the origin IPs to attack?
The origin IP's are already open to attack for most users. It's trivial to scan the whole IPv4 internet to find out which IP you are hosting your site on.
Wishing Cloudflare ops teams the best to recover fast from this outage. Meanwhile, we urge customers to check out www.cdnreserve.com , and implement a sound CDN backup strategy (auto-failover) when the primary CDN suffers an outage.
Never market during another companies outage, offer help instead. Tomorrow it will be you.
Earlier quoted context omitted.
The origin IP's are already open to attack for most users. It's trivial to scan the whole IPv4 internet to find out which IP you are hosting your site on.
You need to block 443 for any other IP than Cloudflare. The IP list can be found at https://www.cloudflare.com/ips/ .
Yes, not worldwide but a lot of places. Problem with our backbone. We know what. Rollbacks etc. happening. Bring it back up in chunks. Should be back up everywhere.
Thanks for being here with timely updates! I knew to come to Hacker News once the alert triggered and a few users started complaining.
Earlier quoted context omitted.
Ditto - I'm sitting here, wtf I'm not running Nginx on my blog, but I'm getting an Nginx response, hit IP directly....oooh.... right that doesn't make sense it's working fine. Cloudflare can't be down, that's next to, wait, status page (to their credit it's got a status note). HN here we go...
Sorry about that.
Yes, not worldwide but a lot of places. Problem with our backbone. We know what. Rollbacks etc. happening. Bring it back up in chunks. Should be back up everywhere.
Earlier quoted context omitted.
To be fair this is not relying on a single SaaS for everything but many people relying on a single SaaS. I mean if you want to use a reverse proxy/CDN, you must rely on someone .
My company uses 3 CDNs, although not cloudflare. If one (say Aakami) goes down it gets removed from the pool and life continues.
It's time to start discussing a fail-open option for us CF users. Most of my sites are using CF for global performance rather than DDoS protection and security. I'd be fine with them changing DNS to point to the origin (or any other user defined IPs) in case of issues (even if it would take hours to return to normal). This is also important for countries with limited connectivity to the Internet, if the PoP in that c…
This would be best implemented by you. If the point is to avoid CF as a PoF, why would you rely on their infra to fail safe when something breaks?
Earlier quoted context omitted.
You can implement your own DNS server that CNAMEs to Cloudflare and falls back to origin IP when there is a problem with Cloudflare. I think a downstream Cloudflare provider could provide such services if they desire.
Last time I checked that was limited to the enterprise plan.