zlacker

Unless you saw a huge spike I feel like not letting you know before is totally unacceptable.

Also, while that's in the terms that's a generic get out clause I know they need but doesn't at all help you figure out what services are ok.

>>IanCal+(OP)
No huge spikes at all, so not sure what triggered it.

>>IanCal+(OP)
Unless you saw a huge spike I feel like not letting you know before is totally unacceptable

I agree... sort of? I mean, this is Cloudflare, right? It isn't as if a huge, legit traffic spike should tax their infra.

IMO, there should be zero shutdown for any long term client, for any reason, at all, ever, without an form of contact.

So weird to have stable uptimes, then support saying "we sorta think you were blocked because..."

So, even account info, with a valid "block" reason, isn't available to their own staff. EG, even their own staff aren't notified?!?

This is sales 101. Mega-simple stuff.

"Hi! You are doing bad thing X, and it needs to change, but we can fix that right now! Let me help you..."

>>tardis+A
Cloudflare seems to be claiming that you did have a huge spike.

> Traffic from this customer went suddenly from an average of 1,500 requests per second, and a 0.5MB payload per request, to 3,000 requests per second (2x) and more than 12MB payload per request (25x)

https://www.theregister.com/2023/02/09/cloudflare_traffic_th...

>>Firero+o2l
I don't have a reason to not believe them in that regard, there was a spike, but it was not visible in analytics I have access to it seems.