4 ms·
(op here). To be fair to Cloudflare a business with millions on the line should be paying a lot more money to Cloudflare than I, a college student with signific
by iudqnolq 7y ago
(op here). To be fair to Cloudflare a business with millions on the line should be paying a lot more money to Cloudflare than I, a college student with significantly less on the line, would. If I had the option to pay $1,000 right now and get everything back up instantly I wouldn't take it because it isn't worth that much to me.
- tracker1 7y agoI realize that... the issue isn't necessarily tethered to your paying status, and it could just as easily happen to someone with a high value business account.
- JakeTheAndroid 7y agoThis is unlikely for a few reasons. 1. If you write into support as an Enterprise customer, you're basically getting an automatic response. 2. Enterprise customers can dial a direct line to support and have this under investigation within minutes. 3. Enterprise customer have a dedicated account manager, and in most cases a Solutions Engineer helped get everything setup. Usually Enterprise domains get locked, so they cannot get caught by linting type services. The likelihood of a domain being removed under those conditions is very low. 4. The most common cause of this type of thing is the Name Servers no longer pointing to Cloudflare, no one noticing for a while. Cloudflare periodically checks to see if a domain is still using CF name servers, and if they aren't they get moved as the assumption is they are no longer on Cloudflare. I don't know that this is what happened here, but it's easily the most common issue on lower tier plans. Enterprise companies often have people monitoring their infra, thus they catch this before Cloudflare conducts the removal of the domain. Source: used to work on the Cloudflare support team.