zlacker

>>tardis+(OP)
i'm about to move a significant amount of traffic to cloudflare. holding off until i see how this is handled. Can you please update this to reflect the total time of service outage and time to resolve. As a busy tech company, this is an unneeded problem. We pay cloudflare to be fast. Not make our sites slow and unresponsive.

>>sgarg2+a6
Outage started around 00:00UTC today.

I was able to contact via support chat to confirm it's indeed Cloudflare related issue as wasn't sure as it's not displayed in any form on Cloudflare dashboard that indeed account is restricted. That was around 8AM UTC.

Since then I also contacted with sales team (got the details already as they approached me in last few weeks as mentioned before) in order to upgrade to Enterprise plan as it seems like the only solution, but did not get the quote yet and account is still restricted.

>>tardis+P6
Your biggest mistake is building a service that depends on a single vendor. Where's your redundancy? Where's your failover?

Creating a HN post is not a proper failover strategy.

All vendors do crap like this. They often have automated systems that sometimes make mistakes. It's your responsibility to build a system that takes these failure points as a reality and build working redundancies and failovers to keep your service online while you sort them out.