4 ms·
As someone who hosts hundreds of PAID sites with CloudFlare this is pretty unacceptable. I'm giving them thousands of dollars so that this doesn't happen. Will
by overshard 14y ago
As someone who hosts hundreds of PAID sites with CloudFlare this is pretty unacceptable. I'm giving them thousands of dollars so that this doesn't happen. Will probably be moving off unless they have some very good reasoning behind a world-wide shutdown of a geo-redundant service...
- robotkad 14y agoHave you called the enterprise support number? What was their response? We are in the same boat, but guess where I have the phone number for enterprise support? Webmail on our domain. Lesson learned.
- overshard 14y agoThe response is "sorry we are looking into it, we'll call you back when we know what's wrong"... pretty generic.
- deleted 14y ago[deleted]
- rurounijones 14y agoWell to be fair, what do you expect them to say before they have diagnosed the root issue?
- alan_cx 14y agoFair enough. But then what is the point of paying for enterprise support if all you get is the same generic response a normal punter gets? If they cant offer better, then enterprise support seems poor value at best. Are we sure that if CloudFlare wasn't so popular here, the word scam wouldn't be used?
- mef 14y agoSo you're saying you want them to say the same thing but reword it since you're enterprise? If they don't know the root cause, they don't know the root cause.
- zhoutong 14y agoCloudFlare offers CNAME option for paid customers. So you can use an enterprise DNS service and only point to CloudFlare via a CNAME record. When disasters like this happen, a quick DNS change can be a life-saver.
- foobar2k 14y agoThere's no such thing as a quick DNS change.
- zhoutong 14y agoMy startup NameTerrific can support instantaneous DNS updates in a geo-redundant Anycast infrastructure. As long as your TTL is sufficiently low (<300), the impact is quite limited as propagation time is negligible at NameTerrific. EDIT: Sorry guys. We got some issues with a gem after installing the recently updated ruby2.0.0p0. The unicorn workers were timing out. TerrificDNS is completely unaffected and the site is already running again.
- avargas 14y agohttps://www.nameterrific.com/pricing https://www.nameterrific.com/pricing "We're sorry, but something went wrong."
- rdl 14y agoIf and only if the site's end users and their software fully respects TTL. A lot don't, especially shitty mobile networks and web browsers.
- Uchikoma 14y agoFrom my experience with DNS for a large site over the last years, a lot of ISPs do not respect your TTL and have their own TTL (often 24h).
- Uchikoma 14y agoNot the best advertising http://www.nameterrific.com http://www.nameterrific.com "502 Bad Gateway nginx/1.2.7"