[sgarg26]

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.

[tardis_thad]

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.

[herodoturtle]

> Since then I also contacted with sales team … in order to upgrade to Enterprise plan as it seems like the only solution

Talk about coercion.

Considering that you weren’t, technically speaking, violating any terms of service, this response from them leaves a very bitter taste in my mouth.

Good luck, and thank you for sharing this with us all.

[tardis_thad]

Around 12:00UTC today ban has been lifted for my account thanks to @jgrahamc - thanks!

[BeefWellington]

So you got a 12 hour outage over... Some random automated system kicking you off their platform for serving non-HTML in requests, which they demonstrate doing in their documentation?

Truly amazing.

[password4321]

The correlation between between being contacted by Cloudflare sales and the throttling should serve as a warning for other customers.

[miroljub]

Seems like blackmail from the Cloudflare side. Waiting for a quote while having an outage doesn't give any negotiation possibility.

However, good luck. And hope your enterprise contract with Cloudflare will be limited only to amount of time you need to migrate from their platform.

[sparrish]

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.

[is_true]

By now most SLAs are already breached